Software Testing Life Cycle

-

Different Phases Of Software Testing Life Cycle(STLC)
THERE ARE FIVE PHASES OF (STLC) :

1.TEST PLANNING AND CONTROL: Test planning is the first step of the testing process. 
In test plan and control we prepare test plan document with the help of the SRS document. We create the planning document as per the standardized format.

 Example: ISO, IEEE829

There are two types of document we create :
1.DPD (Development Plan Document) 
2.PPD (Project Plan Document)

2.TEST ANALYSIS AND DESIGN: The requirement from a testing point of view to identify the testable requirements. This defines what to be tested. To identify the test conditions.
To design the tests. The analysis is maintaining an agreement with the client on the requirement for the project. Test analysis is identifying test conditions. In design, we create a plan for how to implement an idea and technique is a method or way for performing a task. 

 3.TEST IMPLEMENTATION AND EXECUTION:  In this test developing implementing and register test cases and also create test data. verifying that the test environment has been set up correctly.to compare actual result with expected result. Where there are difference between actual and expected results so it will be forward to a junior tester for creating defect
report.

 4. EVALUATING EXIT CRITERIA AND REPORTING:  In this phase, maximum test cases are executed with a certain pass percentage. To check the test logs against the exit criteria specified in test planning.to write a test summary report for the project manager. This is the important activities which inform the required project manager of the status of the testing. test summary report is a document which contains a summary of test activities and final test result.

 5. TEST CLOSURE:  Checking which planned deliverables have been delivered. Test closure activities are done when the software is delivered, because of all the information has been gathered which are needed for the testing. Finalizing the product to released.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more