QA Engineer

The spiral model is a risk-driven process model. This SDLC model helps the group to adopt elements of one or more process models like a waterfall, incremental, waterfall, etc. The spiral technique is a combination of rapid prototyping and concurrency in design and development activities.
Each cycle in the spiral begins with the identification of objectives for that cycle, the different alternatives that are possible for achieving the goals, and the constraints that exist. This is the first quadrant of the cycle (upper-left quadrant). The next step in the cycle is to evaluate these different alternatives based on the objectives and constraints. The focus of evaluation in this step is based on the risk perception for the project. The next step is to develop strategies that solve uncertainties and risks. This step may involve activities such as benchmarking, simulation, and prototyping.

Requirement Analysis:
Requirement Analysis is the first step of Software Testing Life Cycle (STLC). In this phase quality assurance team understands the requirements like what is to be tested. If anything is missing or not understandable then quality assurance team meets with the stakeholders to better understand the detail knowledge of requirement.
Test Planning:
Test Planning is most efficient phase of software testing life cycle where all testing plans are defined. In this phase manager of the testing team calculates estimated effort and cost for the testing work. This phase gets started once the requirement gathering phase is completed.
Test Case Development:
The test case development phase gets started once the test planning phase is completed. In this phase testing team note down the detailed test cases. Testing team also prepare the required test data for the testing. When the test cases are prepared then they are reviewed by quality assurance team.
Test Environment Setup:
Test environment setup is the vital part of the STLC. Basically test environment decides the conditions on which software is tested. This is independent activity and can be started along with test case development. In this process the testing team is not involved. either the developer or the customer creates the testing environment.
Test Execution:
After the test case development and test environment setup test execution phase gets started. In this phase testing team start executing test cases based on prepared test cases in the earlier step.
Test Closure:
This is the last stage of STLC in which the process of testing is analyzed.

1. New: When a new defect is logged and posted for the first time. It is assigned a status as NEW.
2. Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team
3. Open: The developer starts analyzing and works on the defect fix
4. Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as “Fixed.”
5. Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is “pending retest.”
6. Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to “Re-test.”

1. Business Requirements must be available.
2. Application Code should be fully developed
3. Unit Testing, Integration Testing & System Testing should be completed
4. No Showstoppers, High, Medium defects in System Integration Test Phase. 
5. Only Cosmetic error is acceptable before UAT
6. Regression Testing should be completed with no major defects
7. All the reported defects should be fixed and tested before UAT

1. As we all know negative testing is very important to ensure the quality of a product. A good quality product is a zero vulnerability product, to ensure that negative testing is very important.
2. Doing negative testing makes sure that all possible cases are covered. Intentionally or unintentionally there is a chance of negative test cases to occur. So to make sure all cases are covered we have to do negative testing along with positive testing.
3. Negative testing will make more confidence to the client before going live.