Recommended
More Related Content
What's hot
What's hot (20)
More from Dikshyanta Dhungana
Recently uploaded
Recently uploaded (20)
Stlc and v model
- 2. Content • STLC(Software Testing Life Cycle) • V-Model
- 3. Introduction of STLC • Testing process which executed in a systematic and planned manner • Activities are carried out to improve the quality of the product.
- 4. Phases of STLC • Requirement Analysis • Test Planning • Test Case Development • Environment Setup • Test Execution • Test Cycle Closure
- 5. Introduction of V-Model • It is the development form of water fall model • It is widely used software development process • It is also called as verification and validation model.
- 6. Phases of V-Model Left Side • Requirement Analysis • High Level Design • Architectural Design • Module Design • Coding Right Side • Unit Testing • Integration Testing • System Testing • UAT
Editor's Notes
- Requirement Analysis: 1st step where QA team understands all the requirements in terms of what we will testing and figure out the testable requirement. If the requirement are not understandable then in this phase QA team follow up with the various stakeholders to understand the detail knowledge of requirement. Test planning: Also called Test Strategy phase. In this test manager will involved to determine the effort and cost estimates for entire project. This phase will take off when Requirement phase is complete and based on this the requirement, test plan is prepare. Test Case Development: In this phase QA team write down all the detailed test cases and Testing team also prepare the test data if any requirement for testing. Test case are reviewed by the peer members or QA leads after it is complete. Environment Setup: Test environment decides on which condition software is tested. In this phase while setting up the test environment test team is not involved. Developer or customer creates the testing environment. Test team should prepare smoke test to check the readiness of the test environment. Test Execution: In this phase testing team start executing test cases based on prepared test planning & prepared test cases in the prior step. In this phase test case will be check if it is pass or fail. If the case is pass then passed will marked but if any case if fail then it will reported to the developer to solve the defect. Test Cycle Closure: Call out the testing team member meeting & evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives, and Software. Discuss will be take place to know what was good and in which stage there need some changes.
- Verification: Static Analysis Technique. Test is done without executing the code. Validation: Dynamic Analysis Technique. Test is done by executing the code.
- Design: Team studies and investigates on how the requirements could be implemented. Module Design: Methods, classes, interfaces, data types etc are all finalized in this phase. Unit testing: White box testing where piece of code is written which invokes a method to test whether the code is giving expected output or not. Integration testing: It validates whether the components of the application work together as expected. System Testing: All the system test cases, functional test cases and nonfunctional test cases are executed. UAT: Business requirement has met in the user environment or not.
- Unit testing: White box testing where piece of code is written which invokes a method to test whether the code is giving expected output or not. Integration testing: It validates whether the components of the application work together as expected. System Testing: All the system test cases, functional test cases and nonfunctional test cases are executed. UAT: Business requirement has met in the user environment or not.