Skip to main content

7 Stages Of Testing Life Cycle

Systems development life cycle is also referred to as the application of development life cycle; it is a word used in system’s engineering information’s system or in software engineering to describe the procedure for planning, creating, developing, testing, or deploying information’s system. The system’s development life cycles concept applies to the range of hardware or software configurations, as a system can be buildup of hardware’s only, software’s only, & a combination of both.

7 Stages of testing life cycles:

1.       TEST PLAN
A Software testing should always initiates with establishing a well thought out of test plan to ensure efficient executions of whole testing process. Efficient test plans must involve clauses about of amount of work to be completed, deadlines or milestones to be met, methods of testing & other formalities like contingencies or risks.
2.       ANALYSIS
In this stage, a functional validations matrix is made. In house & offshore testing team analyzes requirements or test cases which are to be automated & which are to be tested by manually. At the time of this phase you will:
a.       Creates one un-ambiguous set of requirement’s that establishes an agreement between all of the stakeholders on what the system should do.
b.      Provides the developers & all of other stakeholders with clear understanding of the requirements.
c.       Defines boundaries of systems.

3.       DESIGN
If testing team has reached in design phase, it means that there is no confusion and miss-understanding of concerning test plan, validations matrix & test cases. At the Designing Phase, testing team makes appropriate scripts for automated test cases or generates the test data for both automated & manual test cases.
4.       DEVELOPMENT
In this phase scripting is provided. In distinctive cases of development stage, it also involves the unit tests or generating of performance & stress test plans. Generally, it happens when testing initiates together with the software development activity.
5.       EXECUTION
As soon as, the whole scripting has been made it is execution started. Testing team executes the unit tests, & then functionality tests. They identify the bugs on superficial level or report to the software’s developer. After that the extended testing is carried out. Execution section is completed when test or bug reports are made up.
6.       BUG FIXING
If the development team considers the fixing of the bugs, testing team has to re-test the software in the sequence to checks that no new bug has been created while fixing. The Bug Fixing is the least in "Requirement Gathering" section.  Which one is Top down approach?  So bugs are reduced in the preparatory phase.  Bug Fixing is high in last section i.e. "Release and Maintenance". Which one is the bottom up approach?
7.       SOFTWARE IMPLEMENTATION AND MAINTENACE

This is the final & last phase of software testing when each of the test cases is executed & all processes are carried out. The software is delivered for the end users, who tests it or reports if any bug can take place. Maintenance involves in all the activity after installation of software i.e. performed to keep system operational. Two major forms of maintenance processes are adaptive the maintenance or the corrective maintenance.

Comments

Popular posts from this blog

Why Driven Testing Important for every Software Tester

Context driven testing, Tester have to set their own path to complete their testing objectives, Test product, test documentation and test deliverable. The meaning of context-driven testing is project capture application of skill and opinion. Tester start testing with context driven testing it is very easy to understand and test application, therefore testing is a human activity that involves a great deal of skill to do well. The context-driven software testing methodological analysis indicates for continuous and creative valuation of testing opportunities. A tester always wants to do testing with context driven testing. It’s a very good practice to hands of explore and able to be proud of that work.   Why we need context driven testing- Context driven methodology like as agile process. Agile methodology generally depends on all-inclusive of unit tests. But in context driven testing, tester have to knowledge on unit testing as well testers will change, In context driven te...

Want to know about Mobile Application Testing? Came to right place

What is Mobile Application Testing ? Mobile Application Testing is a phenomenon of testing functionality, usability and consistency of application software designed for mobiles. It is done in two ways: Automated and Manually. When you buy a new mobile, various applications came pre-installed and some you install as per your need from mobile software distribution platforms such as Google Play, Nokia Store etc. In the recent years, mobile devices had shown a rapid growth rate .  Factors that give an open challenge to Mobile application Testing : 1. Mobile devices models : Different models have different hardware configurations, input methods (some are QWERTY, some are touch while others are normal). 2. Several different operating systems (OS) : Market  is full of availability of different operating  systems  (   Android , IOS, BREW, BREWMP, Symbian,   Windows Phone , and   BlackBerry   (RIM)).Each operating system is unique in ...

SELENIUM TESTING: SELENIUM IDE (& its installation)

In our previous post of selenium testing, we discussed selenium testing briefly. But it was just an introduction about that. And the selenium is much wider in its own. In today’s article, we are going to discuss the selenium, IDE Tool. What is Selenium IDE?? In selenium testing, selenium IDE (Selenium Integrated Development Environment) is a simple tool present in selenium suite Selenium IDE has an inbuilt record and playback functionality that allow us to create tests very quickly, easily and efficiently. Selenium IDE is very easy to install and use. As selenium IDE is a Firefox plugin, it aims to support Firefox browser only. Therefore, we can execute our created test scripts on Firefox only. Selenium IDE supports auto complete mode which allows the user to: * Enter commands more quickly *Restricts the user to enter invalid commands. The most impressive thing about the Selenium IDE in selenium testing that the user need not to have any prior knowledge of pr...