subject: Definition And Meaning Of Testing Cycles [print this page] Test has its lifecycle that goes through outside of the milestones. When the new feature appears in the code, it becomes prone to be broken. There is a probability of 30 percent that fix of one software bug will cause another or not fix the bug.
Most often, the entire new component will be accompanied by bugs, if not broken altogether. Due to the fact that one of these bugs can block subsequent testing, firstly found bugs although in small quantities but have high severity. During the process of development of new feature, the number of bugs of different severity increases.
If the function goes to testing, the bugs gradually begin to shrink, and hopefully their severity tapers off as well.
More fit-and-finish issues are identified, and fewer crashing bugs appear. Software tester is present during all parts of testing cycle, thats why some days he can catch 15 or more bugs, and others days may find no new bug.
Remember some facts
First of all, you have to focus on verification. Further you will become more involved with falsification and detection.
Over the period of cycle, Test works with the entire testing team in order to avoid errors. Your job is to analyze the risk and minimize it by introducing and comparing information on the state of the software for management.
Some organizations require all the important features be developed in isolation with the refuse of the changes before the Development would add them into the main code. Others think that a review of code is enough. These actions are due to guarantee checks and balances.
These actions aren't performed in order to force anybody especially the Test do more work.
Be susceptible throughout the life of your test cycle as to verify that the processes are performing. They may need amendment or rejection due to its inoperability. A process whereby everything goes through a test cycle before checking in to the main build tree ensures that build breaks will be scarcely seen.
It was clearly a very effective process. However, it did not eliminate the appearance of some deflections. One developer has admitted that he was not strict enough, because he depended on Test to find where he might not have handled a situation. This process failed because software testing and testing team were not close to developers, architects, or managers, when they have created something. It is obvious that the development is in a condition to avoid the adding of errors in the product at the first stage. Then the Test verifies the product for software bugs, passed through the first step and tries to catch them. Bugs are always present, but a good testing team always strives to cement the cracks with the improvement of engineering and softwate testing.
