You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #419, it would be better for the QGB to define an IntegrationTestSuite as it will allow removing a good number of repetitive lines of code, and it is more elegant.
The text was updated successfully, but these errors were encountered:
With integration test suite:
Pros: remove 6 duplicate lines from each test and put them during integration test initialization.
Cons: not able to run the tests separately (they only run all of them).
Without integration test suite:
Pros: being able to run the tests separately and debug them separately
Cons: 6 additional initialization lines per test.
Does the ability to run tests separately (same as unit tests) worth an additional 6 lines per test ?
Current decision, stick with the current implementation without adding an integration test suite as the ability to run tests individually is really helpful at the moment
Similar to #419, it would be better for the QGB to define an
IntegrationTestSuite
as it will allow removing a good number of repetitive lines of code, and it is more elegant.The text was updated successfully, but these errors were encountered: