Skip to main content
Software Engineering

Return to Answer

highlighting key words
Source Link
Sago78
Sago78
  • 1
  • 2

This will end in an opinion, but to comply with the proposed TestCoverage goal, it seems to be better to rely on UnitestsUnitests, rather than integration testsIntegration tests.

UnitestsUnitests should not rely on external factors or dependencies; if they break, it's due to the development of the application itself, and you have more control over the results.

Integration testsIntegration tests are important to determine any problem with the other products or services, and you may not want to run those often during your daily development but at certain stable checkpoints, as they usually take more time due the external factors and complexity.

Trying to comply with the test coverage sometimes might be hard, but it's a good exercise that helps to question yourself if you are following a clean approach.

This will end in an opinion, but to comply with the proposed TestCoverage goal, it seems to be better to rely on Unitests, rather than integration tests.

Unitests should not rely on external factors or dependencies; if they break, it's due to the development of the application itself, and you have more control over the results.

Integration tests are important to determine any problem with the other products or services, and you may not want to run those often during your daily development but at certain stable checkpoints.

Trying to comply with the test coverage sometimes might be hard, but it's a good exercise that helps to question yourself if you are following a clean approach.

This will end in an opinion, but to comply with the proposed TestCoverage goal, it seems to be better to rely on Unitests, rather than Integration tests.

Unitests should not rely on external factors or dependencies; if they break, it's due to the development of the application itself, and you have more control over the results.

Integration tests are important to determine any problem with the other products or services, and you may not want to run those often during your daily development but at certain stable checkpoints, as they usually take more time due the external factors and complexity.

Trying to comply with the test coverage sometimes might be hard, but it's a good exercise that helps to question yourself if you are following a clean approach.

Source Link
Sago78
Sago78
  • 1
  • 2

This will end in an opinion, but to comply with the proposed TestCoverage goal, it seems to be better to rely on Unitests, rather than integration tests.

Unitests should not rely on external factors or dependencies; if they break, it's due to the development of the application itself, and you have more control over the results.

Integration tests are important to determine any problem with the other products or services, and you may not want to run those often during your daily development but at certain stable checkpoints.

Trying to comply with the test coverage sometimes might be hard, but it's a good exercise that helps to question yourself if you are following a clean approach.