Planning is one of main activities of software testing. Depending on formality of our test process, we have to create detailed test plans with strict template or simple check list on a paper. In any case, we must remember that planning is an endless activity. At least we have to plan for the whole project life cycle. We can’t create a test plan at the begin of the project, print it and have a successful test process. Test plan must be corrected and updated at every turn.
Archive for the ‘Reports’ Category
In this article I’ll discuss the first step for ensuring of transparency between testing department and customer.
It is best to build the relationship in such a way that the customer sees what is happening and what he pays money for. Over time, if our relationship is transparent and we continue working with this person, this relationship is improving. This person begins trusting more and more.
Rule: Quality work + Full transparency of what is happening in the sum gives us confidence of the customer.
The template of the bug report depends on the bug tracking system you use. Usually the bug report should contain the following fields:
- unique identifier
- build version
- step to reproduction
- reproduction (always, sometimes)
As soon as a bug has been found, it must be reported because you can forget about the bug. Do not prepare the report on a paper (you can lose it) and log the report to the bug tracking system. These are simple rules but many testers neglect them and many bugs have been left unfixed.