Quality Assurance Process

2,091 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,091
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
134
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Quality Assurance Process

  1. 1. Software Quality Assurance Process<br />How the entire Quality Assurance Process is being carried out in a company (i.e.) in practical environment?.<br />Prepared By <br />Bala K<br />QA Analyst<br />
  2. 2. How the entire Quality Assurance Process is being carried out in TWC (i.e) in practical environment?<br />
  3. 3. How the entire Quality Assurance Process is being carried out in TWC(i.e) in practical environment? <br />Here I focus on software Testing actual working process. We have got a good experience of software Quality Assurance related activities.  So I will try to share more practically rather than theoretically.<br />Whenever we get any new project there is initial project familiarity meeting. In this meeting we basically discuss on who is client? what is project duration and when is delivery? Who is involved in project i.e. manager, Tech leads, QA leads, developers, testers etc..?<br />
  4. 4. How the entire Quality Assurance Process is being carried out in a company (i.e) in practical environment? <br />From the SRS (software requirement specification) project plan is developed. The responsibility of testers is to create Software Test Plan from this SRS and project plan. Developers start coding from the design. The project work is divided into different modules and these project modules are distributed among the developers. In meantime testers responsibility is to create Traceability Matrix test scenario and write Test Cases according to assigned modules. We try to cover almost all the functional test cases from SRS.  The data can be maintained manually in some excel test case templates or bug tracking tools.<br />
  5. 5. When developers finish individual modules, those modules are assigned to testers.  Smoke testing is performed on these modules and if they fail this test, modules are reassigned to respective developers for fix. For passed modules manual testing is carried out from the written test cases. If any Bug is found that get assigned to module developer and  get logged in Defect Tracking Template. On bug fix tester do bug verification and regression testing of all related modules. If bug passes the verification it is marked as verified and marked as closed. Otherwise above mentioned bug cycle gets repeated.(I will cover bug life cycle in other post)<br />How the entire Quality Assurance Process is being carried out in a company (i.e) in practical environment?<br />
  6. 6. Different tests are performed on individual modules and integration testing on module integration. These tests includes Compatibility testing i.e. testing application on different hardware, OS versions,  software platform, different browsers etc. Load and stress testing is also carried out according to SRS. Finally system testing is performed by creating virtual client environment. On passing all the test cases Test Report is prepared and decision is taken to release the product!<br />How the entire Quality Assurance Process is being carried out in a company (i.e) in practical environment?<br />
  7. 7. Let’s take a look how testing is carried out in the already existing System (Vendor Product).<br />
  8. 8. Methodology of Product Quality Assurance developed by a Vendor.<br />PPQA audits With the help of SRS:<br />Peer Reviews with the help of SRS : <br />Validation testing: <br />Data Driven Testing:<br />Load/Stress testing:<br />Compatibility testing:<br />Usability testing:<br />Let’s take a look how testing is carried out in the already existing System (Vendor Product).<br />
  9. 9. Let’s take a look how testing is carried out in the New Systems (Developing from Scratch)<br />
  10. 10. Requirements <br />This section of the test plan lists all requirements to be tested. <br />Functional Test Requirements – Enlist the functions to be tested. <br />Design Requirements - Testing the user interfaces.<br />Integration Requirements - the requirements for testing the flow of data from one component to the other may be included if it will be part of the test plan. <br />Test Strategy<br />This Section will describe how the test objectives will be met for each type of testing <br />Objective<br />Technique<br />Traceability Matrix<br />Test Cases<br />Risks/Assumptions<br />Tools<br />Resources<br />Identify the resource roles and responsibilities that will be required for test plan execution. <br /> Project Plan - develop a project plan showing the phases, tasks, and resources. <br />Let’s take a look how testing is carried out in the New Systems (Developing from Scratch) A good test plan is the cornerstone of a successful testing implementation. While every testing effort may be unique, most test plans include a common content framework. This article presents the components that make up this framework, and serves as a guide to writing your own test plan. <br />
  11. 11. Schedule <br />Document the schedule in which the application under test is to be made available for testing, and the estimated time for executing test cases.<br />Deliverables <br />List all the deliverables that are associated with the testing effort, and where copies of these deliverables or documents may be located.<br />Defect Tracking and Reporting - Describe any ratings, categories or classifications used to identify or prioritize defects. <br />Critical<br />Severe<br />High<br />Cosmetic<br />Approval - The test plan should be reviewed by all parties responsible for its execution, and approved by the test team, product and development managers.<br />Results - When the test effort is complete, document the results. <br />Let’s take a look how testing is carried out in the New Systems (Developing from Scratch)<br />
  12. 12. QA Process life Cycle Diagram <br />Lets take a look, How the Testing is Carried out Practically.<br />Preparation with the Help of Software Requirement Specification (SRS) or Functional Specification Document (FDS)<br />Inputs : Project Plan<br />Inputs : SRS & FDS<br />CLOSED<br />Pass<br />Fail<br />Retest (Regression Testing)<br />Track it to the Developer for Fix<br />Is Fixed<br />
  13. 13. System Integration with Automated Functional Testing Tool.<br />Once the Application/Modules/Screens are being Freeze by Manual Testing, then Integrate the Application Automated.<br />Regression Testing <br />Do the Above Steps Regressively, in order to Check the Application more and more for both Tested as well as untested Modules<br />
  14. 14. Quality Guarantee Certification<br />

×