Timeline for Difference between two phases of STLC, Integration testing and System testing
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2014 at 16:44 | comment | added | Kate Paulk | If you can't automate, you need to prioritize - pick which of those tests cover the most ground (you'll probably find you can use sets of them - say tests 1, 15, 73, 995, and 1201 in a single scenario test). | |
| May 14, 2014 at 12:29 | comment | added | paul | So we ending up at the base question here now. If we need to give 2 big sprints (5-8 modules in each sprint) in a month, and each would require system testing (means end to end testing = execution of tests from 001 to 2000) then how we going to signoff sprint. This way each sprint would take at least a month (Dont say that we should automate :) ) | |
| May 14, 2014 at 12:14 | comment | added | Kate Paulk | Not necessarily @paul. System testing should happen as soon as the pieces are there. End to end test cases won't be the same as integration test cases, although they might use some of the same steps. | |
| May 14, 2014 at 11:40 | comment | added | paul | 1. So we dont do system testing very often and we dont do it before/after sprint release. 2. We dont need to write special test cases for system testing, we simply execute same test cases that have already executed, but this time we execute them again with newly deployed modules. AM I RIGHT? | |
| May 14, 2014 at 11:34 | history | answered | Kate Paulk | CC BY-SA 3.0 |