What is the difference between regression and integration testing

Testing a stub or functionality is Unit testing Integration testing: you developed Admin side of shopping cart website and your colleague developed front end cart functionality of the website. When you integrate these two functionalities and do a flow testing to make sure if integrating these two facilities breaks nothing and complete flow is working fine Regression testing: During integration testing, some bugs found and you and your colleague fix it.

Again tests are done on those changes. Also, if team implementing constant changes on modules and functionalities, regression testing is required to make sure any changes has not broken any existing functionality. User posted Regression testing and Integration testing is the responsibility of developer or tester? Monday, January 23, PM.

User posted thanks a lot for your answer would you please explain regression test with bit of example for better clarity. Regression testing and Integration testing is the responsibility of developer or tester? And what should you be testing? A unit test is a test written by a programmer to verify that a relatively small piece of code is doing what it is intended to do.

They are narrow in scope, they should be easy to write and execute, and their effectiveness depends on what the programmer considers to be useful. The tests are intended for the use of the programmer, they are not directly useful to anybody else, though, if they do their job, testers and users downstream should benefit from seeing fewer bugs. They test internal consistency as opposed to proving that they play nicely with some outside system.

I typically test each method in each class to ensure functionality at a very low level. You decide what the unit is by looking for the smallest testable part. An integration test is done to demonstrate that different pieces of the system work together. Integration tests cover whole applications, and they require much more effort to put together. When an error is discovered and fixed, the test must be re-performed to ensure that the corrections made have had no negative influence on components that previously had no errors the regression test already mentioned above.

After having performed the various system tests, it is necessary to make sure that the program developed provides the desired results even if it is run in environments other than the native one: it is therefore necessary to carry out integration tests, in which the product is tested together with other ones interfaces and applications.

Unlike system tests, in integration tests it is not necessary to re-test if a defect is discovered after it has been fixed. The integration tests are divided into different groups and can be carried out or not depending on the application to be tested:. The regression test is usually carried out in parallel with other tests and can be seen as a quality control to ensure that the code just modified continues to correctly perform the functions that have not been modified and that meets the same requirements verified previously.

In conclusion, it can be stated that the regression test ensures that the rest of the application not subject to modification is not affected by errors arising from the correction of others.