Importance of Software Testing Life Cycle (STLC)

[Urvish]

#45322

Software Testing Life Cycle (STLC) defines the various stages or phases in the Testing life cycle of software.
Stages of STLC are as below.
1) Requirements/Design Review, 2) Test Planning, 3) Test Designing, 4) Test Environment Setup, 5) Test Execution, 6)Test Reporting.

---

[Chanchal]

#45324

Software Testing Life Cycle refers to a testing process which has specific steps to be executed in a definite sequence to ensure that the quality goals have been met. In STLC process, each activity is carried out in a planned and systematic way. Each phase has different goals and deliverables.

---

[Ganesh Badgujar]

#45326

STLC is Software Testing Life Cycle. It consists of series of activities carried out by Testers methodologically to test your software product. Though STLC uses the term “testing” it does not involve just testers, at some instances, they have to involve developers as well. In STLC Test cases are executed.

---

Attachments (Allowed file type: .jpg, .jpeg, .png, .pdf):

You must be logged in to view attached files.

[Mansi]

#45328

Test Planning

A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing anysoftware/product in a project. test plan: A document describing the scope, approach, resources and schedule of intended testactivities. … It is a record of the test planning process.

Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the Test Plan. In this phase, Test Strategy is also determined.

Activities Preparation of test plan/strategy document for various types of testing:
Test tool selection
Test effort estimation
Resource planning and determining roles and responsibilities.
Training requirement
Deliverables

Test plan /strategy document.
Effort estimation document.

 

---

[amankhemka3003]

#45329

Requirements analysis is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications.

---

[Author]

Posts