UsingDesign!Thinkingto!CreateBetter TestCases! · category method, Six thinking hats, Idea validation board, Bingo selection, now wow how matrix Tools Boords, Mockingbird, POP, InVision

W5 Test Techniques Wednesday, October 2nd, 2019 11:30 AM

Using Design Thinking to Create Better Test Cases

Presented by:

Larissa Rosochansky

Avanade

Brought to you by:

888-‐-‐-‐268-‐-‐-‐8770 ·∙·∙ 904-‐-‐-‐278-‐-‐-‐0524 -‐ [email protected] -‐ http://www.starwest.techwell.com/

Larissa Rosochansky Larissa Rosochansky is the head of Intelligent Automation at Avanade. Prior to that, she was the head of Testing and Automation at IBM Brazil for several years. She has been working with design thinking, project management, quality assurance, and software testing for the last fifteen years. She has worked in many roles, including coaching and managing projects and teams. Since 2016 Larissa has been coaching teams to deliver more value in their projects using design thinking for internal and commercial accounts. Larissa holds a law degree and a specialization in software engineering and is a certified PMP by PMI, ITIL Foundation by EXIN, and PSM I by Scrum.org, and has the IT Specialist Level 2 -‐ Test Discipline Badge and Design Thinking Co-‐Creator Badge from IBM.

1

HOW TO CREATE BETTER TEST CASES | DESIGN THINKINGL A R I S S A R O S O C H A N S K Y


UsingDesign Thinkingto Create Better

Test Cases


About Me

Head of Intelligent Automation and Testing

Services at Avanade, former Head of Test

Services and Design Thinking Chapter at IBM

Brazil, I have been working with automation,

project management, quality assurance, and

software test for the past fifteen years.

I hold a specialization in Software Engineering

and am PMP certified by PMI, PSM-I by

Scrum.Org, ITIL Foundation by EXIN, Design

Thinker co-creator badge and IT Specialist Level

2–Test Discipline Badge from IBM.

Larissa Rosochansky

[email protected]://br.linkedin.com/in/lrosocha

mailto:[email protected]

https://br.linkedin.com/in/lrosocha

3



Take 1 minute to design an alarm clock.

4



Take 1 minute to design a better way for people to wake up

in the morning.

5



DESIGN THINKING IS A USER

CENTRIC FRAMEWORK TO SOLVE

A BUSINESS CHALLENGE

DELIVERING THE BEST

EXPERIENCE FOR OUR USERS

WHAT IS DESIGN THINKING?

6



HOW DO I BEGIN?

DIVERGE!

CONVERGE!

CLUSTERING!

7



Tools Complete Process

Sprintbase, InVision, Mural, Miro

DESIGN THINKING FRAMEWORK

EMPATHIZE

Who is your user?

DEFINE

What is the test scenario

to be tested?

IDEATE

Brainstorm about the

paths to be exercised

PROTOTYPE

Build the test case

for your user

TEST

Share the test case with

the business

Tools

Typeform, Zoom, Creatlr

Exercises

Empathy mapping, Empathy

Interviews

Tools

Smaply, Userforge, MakeMyPersona

Exercises

Customer journey map, Space

saturate and group, Mind

Mapping, Why how laddering,

Design Prompt, PoV, Affinity

mapping

Tools

Typeform, Zoom, Creatlr

Exercises

Brainstorm, Bodystorm, Four

category method, Six thinking

hats, Idea validation board,

Bingo selection, now wow how

matrix

Tools

Boords, Mockingbird, POP, InVision

Exercises

Low fidelity, high fidelity,

Minimum viable product

Tools

UserTesting, HotJar, PingPong

Exercises

Usability testing, User testing,

Wizard-of-Oz prototyping,

Feedback capture grid, Remote

usability testing, field studies

8


DEVELOPMENT LIFECYCLE AND TEST LIFECYCLE

DevelopmentCycle

Test Cycle

PlanningUser

Acceptance

GroomingProduct Backlog

Sprint Planning

Sprint ExecutionConcept

HardeningSprint

•Test Estimates

•Test Plan

•AcceptanceCriteria

•Test Results

• Issues and Defect Log

•Test Report

•Defect Analysis

Planning▪ Create Estimates

▪ Create Test Plan

Grooming▪ Create Backlog

Release

▪ AcceptanceCriteria

Exit▪ Execute UAT

•Epics

•Complete Test Strategy


•Backlog Release

•PrioritizedDefects

•Test Results andTest Reports

•Defect Log

• Sign Off PO

Concept▪ Create Test

Strategy

•Test Strategy

Exit

•Estimates

•Test Plan

Planning▪ Define Product

Backlog Item (orStories)

▪ Create Test Readiness Criteria

▪ Create Test Scenarios

•PBI

•Acceptance Criteria

•Test Scenarios

•PBI


•Test Environment

Execution▪ Test Design

▪ Create Manual andAutomated Test Cases

▪ Test Results

•Codedeployed onUAT

Execution▪ Execute

Regression Test

▪ Execute Non Functional Test

•Test Cases

•Test Results

EntryEntry Entry Entry Entry Entry Entry

Exit Exit Exit Exit Exit

9



What is the Test Case?A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. The Test Case has a set test data, precondition, certain expected and actual results developed for specific test scenario to verify any requirement.

What is a Test Scenario?A Test Scenario is defined as any functionality that can be tested. It is a collective set of test cases which helps the testing team to determine the positive and negative characteristics of the project.Test Scenario gives a high-level idea of what we need to test.

10


How might we __________(what problem needs solving or improvement?) for __________ (which person is most affected by this?)

Design a better way for __________ (which person is most affected?) to __________(what does this person need to be able to do?)

DESIGN PROMPTSELECTING PERSONAS AND UNDERSTANDING THE PROBLEM

11



WHO IS OUR USER?

12


EMPATHY MAP

QuotesWhat do they say or need to say to others?

Expectations & ReactionsWhat do they think about the situation?

ValuesHow does this person feel about their job?

ActionsWhat do they do to get their job done?

13



WHAT IS OUR USER JOURNEY?

14


USER JOURNEY MAPPING

DESIGNS THE E2E PROCESS

EACH STEP IS ONE TEST SCENARIO

TEST SCENARIO -> JOURNEY MAPPING -> TEST CASE

15


Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

CUSTOMER JOURNEY MAPPINGIN THIS CASE, THE USER OF THE GIVEN SYSTEM

Feeling

Thinking

Doing

Every thought brings a feeling

16


IDEATION - BAD THOUGHTS – BAD FEELINGSWHY – HOW LADDERING

Why?

Why? How?

How?

Why?

How?

Negative Path 1

Negative Path 2

Negative Path 3

17


Test ScenarioEach Step of our User Journey

Test ConditionsBreak Happy Path and Negative Path

MappingDetailed steps for the

Test Scenario

Pain PointsIdentify Bad

feelings/thoughts

Divide the E2E Process into smaller parts – this is your test scenario –example: Login, Buying Process, Payment

Split the happy path apart, write the test case.Why/How Laddering to discover negative test casesWrite the negative ones

What are the steps the user will do to complete that section?

Example: select an item, add to the cart

What are the bad thoughts/feelings?Inefficiency?

What could go wrong?Exercise all bad paths.

1

2

3

4

TEST SCENARIO TO TEST CASE PROCESSUSING JOURNEY MAPPING

18


Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

CUSTOMER JOURNEY MAPPINGDESIGN ALL TEST CASES TOGETHER!

Expected Results

Action

19


WORKSHOP

• PARTICIPANTS – GROUPS FROM 4 TO 7 – MULTIDISCIPLINARY

• AGENDA – TIMEFRAME AND WHAT EXERCISES TO BE APPLIED

• STATIONERY

• LOCATION

• MUSIC

• INVITES

20


THANK YOU!

[email protected]://br.linkedin.com/in/lrosocha

mailto:[email protected]

https://br.linkedin.com/in/lrosocha

Documents

UsingDesign!Thinkingto!CreateBetter TestCases! · category method, Six thinking hats, Idea validation board, Bingo selection, now wow how matrix Tools Boords, Mockingbird, POP, InVision