Software Testing Processes: An approach for Software Quality |
Written by crestech software
Friday, 09 May 2008
|
Software testing is one of the inevitable processes in software development life cycle. For software testing process there are few sets of test are defined: making test plan, test cases design, defect documentation or bug logging and status report file.
All these steps are taken together by software testing teams to make a complete software testing cycle. This software testing cycle helps organization to achieve high quality software products and applications. To process high quality software testing the software development requirement documents and design document play major role in planning and designing the software testing deliverables.
There are various open source testing tools present and available freely to make the testing easy and simplified for beginners as well. Expert software testing professionals has right mix of following: - logical and reasoning aptitude, - software testing experience and - good knowledge of frameworks and practice on testing tools.
Let's discuss few processes of software testing:
Making Test Plan: Test plan describes the following - - the objective of software testing, - scope of the software testing, - approach and assumptions in testing, - dependencies and risks measurement and - schedule and steps for the test phases Many testing organizations and companies defines test plan as to describe software testing phases, testing procedures, technical analysis and other general standard testing practice. Objective of Test Plan defines "why testing is required", whereas scope of Test Plan defines "what are the requirements in testing".
Test Cases Design: Test cases designs are prepared to give the complete direction and flow in the testing procedure. Test cases are designed by keeping the operational flow of the software in mind. To design high quality test cases, the proper documentation of current test cycle is required to make it extendible in future test cycle. Test cases in common define the author, description, steps, and expected result of the testing.
Defect Documentation/Bug Logging: Software Testing is done to find the malfunctioning and defects in the software. Defect finding is the most critical role in the software testing cycle. Making proper documentation of defects stating how to reproduce the bug is required and expected from the software tester. Defect documentation commonly states the tester name, reproduction steps, severity and status of the defects.
Status report file: Status of the software testing is prepared in weekly, bi-monthly, monthly basis. Status report helps in meeting timelines and forecasting the staging of the software for production. Quality status reports always focus the goal of testing and software testing deliverables. http://www.crestechsoftware.com Article Source: http://www.ArticleBlast.com |
About The Author:
Crestech Software Systems is an independent software testing training company providing outsourced software testing services like functional testing, performance testing, test automation and Software QA across various stages in the software development lifecycle. Crestech also provides software trainings including corporate training and public training to leading and growing companies.
|
Software Testing Processes: An approach Written by crestech on 2008-05-09 06:39:08 , |
Only registered users can write comments.
Please login or register.
You are welcome to publish this article free of charge on your website, newsletter, or e-zine, provided:
- You don't change the article in any way
- You include the entire article, including the "about the author" box
- All hyperlinks must remain intact, including email addresses, and the link to ArticleBlast.com at the bottom
- In doing so you agree to indemnify the article's author, and ArticleBlast.com and its directors, officers, employees and agents from and against all losses, claims, damages and liabilities which arise out of its use
- It is also recommended that you provide a courtesy copy of your publication to the author of the article