The Role of Programming Testing

This is my first post in the Lifecycle error of the series. I have to talk about this because when it comes to the role of evidence is not clear. The role of software testing is often misunderstood by the participation of officials from various growths and implementation of this list also includes testers.

The test is considered part of quality assurance activity since the early days of software growth and the same trend is happening from now. Even the most titles as a QA Engineer / QA Lead testers are associated with even though they are not playing the role of quality control.

It's good for catching Test mission and aligns their test equipment in that direction. Everyone in the team must have clarity about their role and see how it is to contribute to the team's mission.

It is good to note that-

* Testing is not quality assurance systems the Tester it is not a quality police.

* Testing is not the orientation of fault-free products. It is simply impossible, since no human brain can construct systems (human beings make mistakes of course).

* Testing is not fighting with the development teams. Do not act like the enemy of developers.

* Testing is not just looking at the documents (so called BRS, SRS, and FRS) and writing test cases.

* Do not fight with the developers about the issues that must be corrected for release in time to write good report that reduced playing time and debugging.

The test is a process used to make things better. This helps them make informed decisions by allowing relevant information on the basis of context. Testers need to identify critical issues with the system as soon as possible and ensure that the data provided is sufficient to reproduce the problem. We have to provide information about the presence of errors in the system to interested parties. The information should help stakeholders to make informed conclusion.

The following list helps-

* Identify the different end users of the system and its interaction with it.

* Capture the important scenarios for each end user. It's good to say that we capture the story of the whole scene and not just steps.

* Talk with stakeholders, including customers (Case if you have access) on how the property could be used and the capture of the scenarios.

* Plan for the discovery of critical system problems as soon as possible.