![]() What we do in a healthy agile environment is to release a new version with every check-in. The product increment that includes all these items then becomes version 1.0. Because people are not used to version numbers like 55461254.0, we use product increments in the agile context and at some point, the product owner defines which items of the backlog make a version 1.0. We just don’t call it Version 1.0, we call it product increment instead. ![]() If you ask yourself how this works for agile environments: Exactly the same way. Version 1.0 can be released to our customers. We do this for all specifications and if all test cases are passed the software provides all the specified functionality. There are different design techniques for test cases etc. If the software is written 100% according to specification the test case passes, and the testing of this specification is finished. Regressions start after version 1.0 is released… You will have multiple test steps with stimuli, expected, and actual results. That means a SME/Tester/Test Engineer reads through a specification (or a set of specifications) and designs a test case based on it. For now, we assume that testing, in general, is a technique used to prove that functionality works as specified. There is nothing special about a regression test besides its timing. Let me give you my definition for a regression test:Įvery test automatically becomes a regression test after its first execution. We can’t close this gap but knowing that it exists is the first rule in understanding how it works and how people write about it. ![]() is testing to find bugs or is testing a technique to prove that functionality works as expected. Most of them are the same just reflecting a different view, i.e. In the software testing world, there is a myriad of different definitions for the same “technique”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |