Closed miroslavpojer closed 3 months ago
@miroslavpojer Please help me understand why there is testIT and testDB. Wouldn't testIT be enough?
testDB
looks ok.testDB
is used on request of @benedeki - see comments above.Both commands represent a generic group of Integration tests so testIT
is a generic name, sure. I will use it everywhere, where I do not have any reason to change - see reasons for testDB
above.
@miroslavpojer Please help me understand why there is testIT and testDB. Wouldn't testIT be enough?
* Both commands are solved in different ways. So a different name. * Tests in database 'module' are testing db functions - so `testDB` looks ok. * `testDB` is used on request of @benedeki - see comments above.
Both commands represent a generic group of Integration tests so
testIT
is a generic name, sure. I will use it everywhere, where I do not have any reason to change - see reasons fortestDB
above.
Thanks for explanation. I guess If we intend to follow a convention of having a "database" module in our projects for sql functions and their tests it's reasonable to have a dedicated command.
Overall Project | 70.78% | :x: |
---|
There is no coverage information present for the Files changed
This item depends on:
Depends on #196