Skip to main content

STLC - Software Testing Life Cycle

Sprint / Software Testing Life Cycle)

Where, PO - Product Owner, SM - Scrum Master, ST -Scrum Team
From Agile Scrum Terminology:
ERROR: When a developer finds a problem in coding called as ERROR.
DEFECT/ISSUES/INCIDENT/TICKET: When a tester finds a problem in sprint or software called as DEFECT/ISSUES/INCIDENT/TICKET.
BUG: When a developer accepts testers reported defect called as BUG.
FAILURE: When a client people face problem in sprint or software called as FAILURE.

SDLC vs. STLC in agile scrum


where, CEO - Chief Executive Officer, PO - Product Owner, SM - Scrum Master, ST - Scrum Team, DR - Defect Report, MS - Modified Sprint, UT - Unit Testing, IT - Integration Testing, SH - StakeHolder
Labels:

Comments

Post a Comment

Popular posts from this blog

Test Initiation

STLC process can start with test initiation. In this stage, PO can prepare a test strategy document for current sprint or software testing. Test strategy is also called as test methodology or test approach. In sprint or software testing, strategies have three types of testing such as exhaustive testing, optimal testing, Ad-hoc testing. In general, Exhaustive testing is not at all possible and ad-hoc testing is not reasonable. Due to these reasons, ST is following optimal testing strategy to conduct better testing. • Optimal test strategy document format in IEEE 829 standards i) Test strategy document ID - Unique name or number as title. ii) Scope and Objective - Importance of testing in current sprint or software. iii) Business issues – Budget allocation for testing. iv) TRM (Test Responsibility Matrix) – List of tests to be conducted. v) Roles and Responsibilities – PO can specify the roles in ST testers and specifies responsibilities for each other. vi)Test autom...
1 comment
Read more

Testing Stages or Testing Phases

I) Document Testing: In waterfall model or V model or agile model, the first testing stage is document testing. Here, PO is responsible to prepare all user stories (Product Backlog). The same PO can review those user stories for completeness and correctness. PO can join with SH’s, SM and ST to select some user stories (Sprint Backlog). The same PO can review SBL for completeness and correctness. When PBL and SBL are base lined (finalized), ST developers can prepare HLD and LLD’s.  HLD(High Level Design) is an overall architecture of entire sprint, whereas LLD(Low Level Design) is an internal logic of specific module in sprint. Due to these reasons, one sprint design is having one HLD and multiple LLD’s. Same ST developers can review those designs for completeness and correctness. Case Study: Walkthrough: Study a document from first to last. Inspection: Search a document for specific topic/factors. Peer review: Comparing two similar documents point to point. Note: ...
Post a Comment
Read more