[WLB] Software Test Strategy — micro learning Day 04

Day 04: Mon 11 Nov 2024

recap Q2 and Q3

• Q2–100% automation, select tool that applicable with the source code framework
• Q3–100% manual

continue at “Technology Facing”, south side of the Quadrant

this is all coding

• Q1, Test case from Test Design Technique -> to Guide the development
• This functional test as the unit test which is 100% automation
• The out put from Q1 is the test source code

example unit test in Go Language from github/sck-seal-team-one/shopping-cart

QA/Tester should know about unit test for structure, what have been done in the unit test,

• not required to write unit test, is great if can do :)

E2E test as UI

E2E test as API

Who would perform the Test Analysis and Design as the input for test scenario ?

• this is designed from Need and Business requirement
• -> everyone who participate in requirement clarification: BA,SA,QA/Tester,PM,PO
• QA/Tester could guide those related team member to enable them to perform this as the early stage as possible

as in the role and responsibilities

Now we are at the end of Test Approach

Let define the Test Process

Test Process with different SDLC model

for Waterfall Model, Test Development — perform in

• Requirement gathering phase
• Analysis and design phase

for Agile Software Development, by default (Manifesto & Principle) doesn’t have anything to do with software development process

with the methodology / framework under the Agile

for example with Scrum Framework, there is Scrum Events

• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective

not mentioned in Scrum guide, but there is the acting in Product Backlog Refinement

• adding details
• Estimate
• Ordering the item

refers to Scrum Guide July 2016 - page 14, or 2020 version, mentioning about the Product Backlog refinement

So, the Test Development could be in Product Backing Refinement at Adding detail !

combine with XP — Extreme Programming methodology, use the User Stories

for the Software Requirement Development, at

• Requirement Validation
• Requirement Verification

in XP, there is the User Stories → Test Scenarios → Acceptance Test

XP — Extreme Programming

Who will be in Product Backlog Refinement ?

• Scrum Team, which contains

1 x Product Owner

1 x Development Team: who is in here ?

1 x Scrum Master, temporary role

in WLB, there is another person that would be involved: Requirements Owner

• this could be called “The Three Amigos” (BA, Dev, Tester)

• “Power of Four” (cannot find the reference picture in Google yet), which include the Business people

Thank you for today ka :)