Black and white: Software testing for scientists. Katrina Clokie. Let s Test Oz

Size: px

Start display at page:

Download "Black and white: Software testing for scientists. Katrina Clokie. Let s Test Oz 2014. @katrina_tester"

Nathaniel Chase
8 years ago
Views:

1 Black and white: Software testing for scientists Let s Test Oz 2014 Katrina

2 Session Based Introduction Visualising Visual Test Strategy Modelling Management Black and white: Software testing for scientists Katrina

3 Context Test consultant embedded in a scrum team for three days a week Create cross-skilled resources by training the existing team of developers, business analysts and subject matter experts in testing Specialist financial domain Team was University educated > Economics & Finance > Mathematics > Computer Science

4 100% Automation

5 101 Workshop

6 Session Based Introduction Visualising Visual Test Strategy Modelling Management Black and white: Software testing for scientists Katrina

7 101 Workshop

8 IDEA PRODUCTION

9 In our test strategy and we re doing it In our test strategy and we re not doing it Not in our test strategy, but should be

10 Availability Package Performance Unit Component SpecFlow End-to-End Disaster Recovery SME Interaction Release Integration Regression Acceptance Security Mind Maps Automated Manual Manual Exploratory Usability Operations Specification Workshops System In our test strategy and we re doing it Parallel In our test strategy and we re not doing it Read more: Not in our test strategy, but should be

13 Starting Together

14 Session Based Introduction Visualising Visual Test Strategy Modelling Management Black and white: Software testing for scientists Katrina

15 Think Talk Act

16 What do you think this does?

17 Does everyone agree that s all?

18 How are you going to test this?

19 Are you happy that this testing will mean the story is done?

20 Test Ideas That the acceptance criteria are met That each function does what it is supposed to do (positive testing) The problems that each function could have (negative testing) Input data for typical, boundary and invalid cases Output data for typical, boundary and invalid cases A flow through the system, with functions in different orders Reference: Bach, James (2013). Heuristic Test Strategy Model

22 What should we automate? What matters most? Are there any problems with high impact? Are there any problems with high probability? Reference: Marick, Brian (1998). When should a test be automated?

24 The greatest enemy of knowledge is not ignorance, but the illusion of knowledge Stephen Hawking

25 Session Based Introduction Visualising Visual Test Strategy Modelling Management Black and white: Software testing for scientists Katrina

26 Manual Tasks

27 Session Based Test Management

29 Peer Review

30 What happened? Multiple manual testing tasks for a story Focused investigation with consistent reporting Review improved testing by creating competition Increased SME confidence in testing by the team Reduced duplication

31 Conclusion

32 Availability Package Performance Unit Component SpecFlow End-to-End Disaster Recovery SME Interaction Release Integration Regression Acceptance Security Mind Maps Automated Manual Manual Exploratory Usability Operations Specification Workshops System In our test strategy and we re doing it Parallel In our test strategy and we re not doing it Read more: Not in our test strategy, but should be

34 Session Based Test Management

35 Black and white: Software testing for scientists Let s Test Oz 2014 Katrina

Agile Testing. What Students Learn

Agile Testing. What Students Learn Agile Testing Transition sound traditional test practices into an Agile development environment. By using a step-by-step approach, this course documents how to transition from traditional test practices