How to integrate system testing into a flexible process?

Classic agile descriptions have released code at the end of the iteration. If there are additional checks and checks that must occur to create a product, how do you integrate this into the process?

+5
source share
5 answers

What is stopping you from making your own process? If you find that something might be better ... just do it. If this works, continue with it, if not try something else. If you want agility, there is no installation process in stone.
A term that is more commonly used is shippable ' code at the end of each iteration. This means that you can provide it to the end user (like a bunch of DLLs to copy a part or personally deliver a CD / DVD), and he will receive a value from its use. Such code passed all the unit tests (developers) and acceptance tests (customers / QA / Analysts) , which were considered necessary for "DONE!". Acceptance tests are end-to-end modeling of client scenarios.

, " ". " ".

  • , " " .
  • - , .
  • //, , .

( , , .. . Yay!) , , β„– 14 , . " n " Iteration # 14.. . , , /, , .

, . .. , Iteration # 13. , 2- .. , , , . , 2 Iteration # 14 / , .

+3

, / , , , / . - . - , .

: . , , /. , , . - , , , , .

. , - . , , , , . .

, , , . , , . . .

, / , , , , , .., , , . , .

, , , , .

+3

.

+1

backlog ( Scrum) .

.

0

, . ( , , , .)

- , . (unit test + ), , . , x / , . , .

0

All Articles