Privacy Policy. This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website.
We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent.
You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information. Requirements specification document Application design document User acceptance criteria document.
Brainstorming on the requirements. Create a list of requirements and get your doubts clarified. Understand the feasibility of the requirements — whether they are testable or not. If your project requires automation, carry out automation feasibility study.
Updated requirements document Test feasibility reports Automation feasibility report. Test Environment Setup Activities Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment. Setup test Environment and test data Perform smoke test on the build. Test Execution Phase Test Execution Phase is carried out by the testers in which testing of the software build is done based on test plans and test cases prepared.
Test Cycle Closure Test Cycle Closure phase is completion of test execution which involves several activities like test completion reporting, collection of test completion matrices and test results. Document the learning out of the project Prepare Test closure report Qualitative and quantitative reporting of quality of the work product to the customer.
Test result analysis to find out the defect distribution by type and severity. What is a Test Script? How to write with Example. Report a Bug. Previous Prev. Next Continue. Home Testing Expand child menu Expand. SAP Expand child menu Expand. Web Expand child menu Expand. Must Learn Expand child menu Expand.
Big Data Expand child menu Expand. Live Project Expand child menu Expand. From the above discussion of the advantages and disadvantages of the waterfall model, it is very well clear that the waterfall model can be used in: 1. Projects where the testing activities are performed by the sponsor itself. V Model The waterfall model is an old and outdated model which has many disadvantages and limitations.
Different Phases involved in the V Model The advantages of the V-model are similar to that of the waterfall model. It is easy to understand and simple to use. Its simplicity makes it even easier to manage. No overlapping of phases takes place. Works very well for projects where the requirements are well understood like in smaller projects. It has a specific review process and deliverables for each phase.
The disadvantages of V-model are: High uncertainty and risk. Not good for projects that are object-oriented and complex. Not good for long projects. Not good for the projects where there is a moderate or high chance of requirement changes throughout the process.
Spiral Model In the above two models, the V model and the waterfall model are good only for smaller projects where the requirements are very well specified. It allows the accommodation for the required changes, unlike the last two models where the requirements should be specified very clearly and should not change throughout the process.
It allows users to check the system very early. More accurate capturing of requirements. It allows dividing the development process into smaller parts so that the parts which are riskier can be developed earlier which leads to better and precise risk management. The process involved is also complex. The date on which the project will be finished cannot be known early.
Not suitable for projects involving low risk because it can be expensive and redundant for them. The spiral iteration can go on indefinitely. It needs excessive documentation because of many intermediate stages. It involves six different phases: Requirement Analysis Test Planning Test Case development Test environment setup Test Execution Test Cycle closure Each of the phases involves different entry criteria and exit criteria.
The entry criteria in the Requirement analysis phase are: The following documents have to be available: Requirement Specification and Application Architectural.
The acceptance criteria need to be well defined along with the availability of the above documents. Some of the Activities involved in this phase are: 1. Defining the testing priorities and focus. The Deliverables which is associated with this phase are: 1. Report on Automation feasibility if it is required. The Entry Criteria for the Test planning phase is: Requirements documents the updated version of missing or unclear requirements.
A report on automation criteria should be available. The activities associated with the Test Planning phase are: 1. Defining the scope and objective of the experiment. Listing the types of testing associated with the Software Testing Life Cycle. The estimation of test effort and planning for resources. Selecting the tools for testing if required. Defining the overview of the testing process. Preparing the schedules for the test. Defining the environment for the test required for the entire project.
Determining responsibilities and roles. Listing the deliverables of the testing. Defining the risk associated if any. Defining the suspension criteria, exit criteria, resumption criteria, and entry criteria. The deliverables in the test planning phase are: 1. Test Strategy or Test Plan document. Document for the estimation of the Testing efforts. The entry criteria for the Test case development phase is: The requirements documents the updated version of missing or unclear requirement. The report on Automation feasibility.
The Activities involved in the Test case development phase are: 1. Preparing the test cases. Preparing the test automation script if it is required. Enumerating the possible actions of the users and their objective. Setting the priorities of test conditions. Selecting the condition under which testing will take place.
Documenting test conditions. Verifying and correcting the test cases on the basis of modifications. The deliverables associated with the Test case development phase are: 1. Test cases 2. Test data 3. The entry criteria for the Test environment setup phase are: The test plan should be available. Cases for the smoke test should be available. The test data should be available. The activities involved in the test environment setup phase are: 1.
Setting up the test environment. Test Execution - Phase in Software Testing Life Cycle After developing the test case and creating the test environment he only thing left is executing the tests.
The entry criteria for the test execution phase is: Documents of Test strategy or Test Plan Test cases Test data The activities involved in the test execution phase are: 1.
Executing the test cases according to the test planning. Assigning the bug Id for every blocked or failed test cases. Retesting of the blocked and failed test cases after the bug is fixed. Tracking the defects to the closure. Please use ide. Load Comments. What's New. Most popular in Software Engineering.
More related articles in Software Engineering. We use cookies to ensure you have the best browsing experience on our website. Start Your Coding Journey Now!
0コメント