Ethics of Rapid Software Testing

What is Rapid Software Testing?

Rapid Software Testing is a unique approach of doing testing, by making testers, independent of endless documentations & paper-works, and directs them to accentuate on their intellectual traits, to carry out the process of testing. It’s a quick, inexpensive and expedient way of testing any software, at any time and under any condition.

This testing, unlike traditional testing, approaches mind-set and thinking ability of the tester, as a resource for testing. To distinguish, rapid from traditional, a little knowledge of traditional testing needs to be perceived.

Traditional Testing is an orthodox way of testing. It relies on paper-works and proper documentation during each phase of testing process. It’s a good strategy, to follow proper documentation, when your brand or value is at stake, but it is, not always possible to carry out traditional testing, keeping in account, time and budget constraints linked with the projects.

What’s new in Rapid Testing

• Motivates testers to think as experts, by making usage of their tacit knowledge.
• Actual testing is performed, without any paper-works such as requirement gathering and building testing strategies and plans.
• Quick and inexpensive testing under stringent conditions, environment and pressure, yet credible.
• Dual purpose- testing and teaching i.e. along with the task of testing, it teaches testers, how to work and response quickly, under pressure.
• Explorative testing is at the core of rapid testing.
• Effective for meeting, continuously growing needs of the testing, quickly, so as to fulfil the expectations of providing quick feedbacks, as desired from every tester.
• Experienced testers can expect to broaden their horizons of intellectuality, to carry out testing, quickly, under any circumstances. Fresh testers can see rapid testing as a door to explore new and innovative ways through testing drills & exercises, solving puzzles, etc.
• Heuristic approach, to persistently re-maximize testing, to meet the requirements of the client.
• Self-improvement process for the testers and develops their scientific mind.
• Exposure to realities.
• Designed for testing, in the availability of insufficient amount of information & resource and limited time.
• Transforms testing into excellent testing.

It’s principles

Testers must be aware of underlying principles of testing, on which best possible testing process could be structured. Here, we are providing you,with some of the principles, that may be considered, in order to achieve maximum success in Rapid Testing.

• Every Project is infected with unexpected circumstances and time-constraints.
• Every software project is bound to some time-limits. The volatile nature and growing complexities of these projects makes it more difficult. Despite of these, developers and testers are inclined towards more working on the project, than what is required, due to their inquisitive nature. But, they should also be aware of the fact, that the projects are to completed within stipulated deadlines
• Testing is an act, not an artifact
• Test cases are artifact, as they are build up by testers. These are converted into act, after their implementation and execution. Therefore, a tester should not be confuse between test cases and actual testing, as former portrays procedures for performing testing, while latter is the execution of these procedures.
• Perfection can’t be achieved
• Even after, being full-focussed, dedicated & attentive, we are left out with some errors, resulted from human nature of committing mistakes. To commit mistakes, is not a big issue, but repeating same mistakes is not acceptable. Therefore, it is necessary to learn from the mistake done in past, so as to improve in present and future.
• Testers cannot controls quality, but are responsible for it
• Controlling the quality is in the hands of developers, but testers should not neglect the fact that they are also responsible for quality keeping in account, their task of tracing bugs, so as to achieve and maintain the quality of the product.
• Relationship between software and its end-users.
• Each and every user have a different taste. It depends upon them that, what they prefer as quality in the software. It might be possible, that only one quality of the software is important for one user, whereas other user prefers another quality. Thus, the fact cannot be ignored, that human taste or perception, influences the software development process.