Integration Testing is a testing on the interaction of major subsystems in the project between each other. This means that the contract set upon the subsystem must be honoured during the testing.
It can be quite similar to what of 202206201320 as the latter also emphasises the importance of testing subcomponents before testing the main module.
202206201335# could be done on Integration Testing to validate the tests.
Run all the tests that doesn’t require specialised equipment or environment# (Unit Testing# and Integration Testing#) before checking the code. We should do it often and automatically, which could be done by incorporating the testing facility# into the project build system such as CMake and Makefile. If a full build is necessary, make sure all available tests are running during the process.
Unit Testing# is the foundation of this whole practice. That being said, other testing such as Integration Testing#, Validation and Verification of System Requirements#, Environmental Testing#, Performance Testing#, Usability Testing# and Runtime Diagnostics# should not be underestimated. All test cases should honour its contract where we can check whether the code meet the contract of the contract means what we think it means.
Regression Testing is a kind of testing that compares the output of the current tests (usually #202206201320, #202206201330 and #202206201415) with the previous values (from previous ran tests). It is used to find out the disparity or difference, if there is any, of performance, contract, validity etc. between them.