Get advice while stuck on a project

Dan — Mon, 12 Sep 2022 12:21:53 +0000

Hi,

Not sure if this is the correct place to ask or not, but said I would try!
I am creating a web app using a quarkus server, I am at a part of the app where I want my users to have an option of uploading files. There is a million+ tutorials on that and I am not stuck on that part.

What I am having trouble is I don't want to just upload a file, I want to upload a file with with extra information too, such as the name, description, expiry date, if it's required etc. Now this is something I can't seem to find anywhere and I am not sure where to go with this.

I dunno if the file is uploaded in it's own call and then the object is uploaded. Seems like a lot to me tbh.

Also with file management, is it better to save the file to the db or is it better to save it in a location on the server and then attach the path to the object saved in the db?

Really need help on this as I am stuck and haven't a clue.

TL;DR
Want to upload file over REST endpoint but also include other properties external to the file, like expiry date, required etc.

DB Testing with TestContainers

Dan — Tue, 06 Jul 2021 19:50:48 +0000

Testing, as we all know is a very important part of development, but it is not always easy to do!

Trying to find a way to test querying databases was very tough, at least I thought so anyway. From doing some research online there was one of two ways to test this;

Use mocks
Use an embedded db - including testcontainers in this

Personally I don't like mocks, so that was option 1 ruled out.

Using testcontainers in code was great and worked very well but I had a slight problem. For the life of me I could not get the database to reset between tests. If I were to run the tests individually, all would be good. But when I run a suite of tests at once they fail because the db isn't reset.

With a Quarkus setup I was able to find out that if you annotate the class with @TestTransaction, then after each test the db is rolled back.

@QuarkusTest
@TestTransaction
public class TestClass {

    @ClassRule
    private static PostgreSQLContainer dbContainer = new PostgreSQLContainer("postgres-image")
            .withDatabaseName("dbname")
            .withUsername("username")
            .withPassword("password");

    @Test
    public void myTest() {}


    @Test
    public void myTest_2() {}

Now with the two tests, you can run them as a suite and the db will be reset after each test is finished.

Happy testing

DEV Community: Dan

Get advice while stuck on a project

DB Testing with TestContainers