Explain STLC with an example.

  STLC –Software Test Life Cycle defines what testing activities to perform during the duration of the project. It is formalized by defining various phases of the testing process throughout the project. In modern, software products the STLC is repeated multiple times till the product reaches satisfactory software quality.

As in SDLC, there are different phases in in STLC


Lets understand each phase one by one:

Requirement Analysis:

In this phase the QA team performs following activities:

·  Understands requirements from the testing point of view to identify testing requirements of the project.

·         Develop a better understanding of the desired software product.  

·         Quantify the requirement testability via manual testing or automation.

·         Identity types of tests to be performed

·         Create a requirement traceability matrix.

Test Planning:

Following activities are performed in this phase:

·         Analyze various test approaches.

·         Create a test plan.

·         Prioritize test conditions.

·         Identify test tools.

·         Test effort estimation.

·         Resource planning

Test Design:

Following activities are performed in this phase:

·         Prioritisation of test conditions

·         Design the high level Test Case

·         Designing of Test environment

·         Identification of Tools and Infrastructure

·         Refine test conditions identified in the test analysis

 Test Implementation:

Following activities are performed in this phase:

·         Designing of low level test cases

·         Detailed test procedures are defined.

·         Sequencing of test procedures is done.    

·         Test suites are identified

·         Test execution schedule is prepared

·         Service virtualization of automated scripts are created 

·         Creation of verification of test data and test environment is done

·         Expected results are defined.

Test Execution:

Following activities are performed in this phase:

·         Categorize every test case or procedure into following categories

o    Pass

o    Fail

o    Blocked

o    Ready to Run

o    Skipped.

·         Defect reports are created

·         Detailed documentation about which test items, objects, tools and test ware are involved in testing.

·         Once test execution is complete, we know that 

o    Which requirements are passed.

o    Which requirements are failing and what are corresponding defects.

o    Which requirements are planned to be tested

·   It gives better understanding to all the stakeholders about the state of the product.

Test Completion:

Following activities are performed in this phase:

·         Test Summary reports are generated,

·         Action items for improvement of product are identified.

·         Change request are created

·        Product backlog items are added.

Comments

Post a Comment

Popular posts from this blog

What happens in requirement analysis phase in SDLC?

Image
For any  software development life cycle  (SDLC), the requirement phase is the first step toward unambiguity. It is an essential step because it reverberates with acceptance tests which are crucial for the end user acceptance. Here is the complete process of the requirement analysis and gathering phase of SDLC – Requirement gathering Also known as elicitation, software development requirements gathering is followed by an analysis of the needs so that the technology experts shall go for feasibility tests and may alter some objectives to convert the thoughts into a real product. The gathering technique involves precise research on what customers need. Nevertheless, it is not possible to put a survey questionnaire to each customer and get feedback; hence, the requirement for product, tool, or objectives is asked to the stakeholders who influence the product or who are well acquainted with the end users. The stakeholders could be software quality engineers or at times even...
Read more

What are the drawbacks in waterfall software development mode?

  What is the Waterfall Method? The Waterfall Model is a linear or sequential approach to project management and works based on fixed dates, requirements, and outcomes. Teams do not require consistent communication and, unless specific integrations are required, can be self-contained. Team members can also work independently and are often required to provide status reports somewhat less frequently (when compared to an agile approach). A typical Waterfall project is chronological and is made up of the following phases: Requirements Design Implementation Verification Maintenance Disadvantages of the Waterfall Model 1 . The waterfall model doesn’t support making changes. 2. It can invalidate the work you’ve previously accomplished. 3. This method excludes end-users and clients. 4. It delays testing until after the completion of the project. 5. The waterfall model can promote longer delivery times. 6. It typically works better for small projects. 7. Working m...
Read more