The document discusses improving communication when software tests fail. It advises moving beyond simply saying "it just doesn't work" and instead providing specific details about what was tested and what went wrong to allow others to fix the problem. It also notes that software issues often stem from multiple small errors combining rather than a single large one, so all contributing factors should be investigated. The key is learning from failures, understanding different perspectives, and working as a team to continuously improve testing practices.

1. It’s Just….
Alex Schieren

2. As you’re testing...
! Something you don’t expect happens
! Something crashes
! Something produces an incorrect value
! A test/scenario “fails”

3. What’s the follow up?
! Conversation?
! ‘Bug Report’
! Meeting
! ….
Somehow this information needs to be communicated

4. What’s the content of that follow up?
! It should just…
! It didn’t work…
! I clicked and it broke
What information have you provided to allow the problem to be fixed?
How can we improve?

5. “Just”
I always try to catch myself when I say this

6. Let’s get one thing
straight… The problem
isn’t that someone
decided to display the
wrong value on screen.

7. Perception and
Relationships

8. Differences in
Mental Models &
Thinking

9. Perspective Matters

10. Constraints

11. Let’s not be lazy!
! ‘I changed something that should have not
broken anything’

13. Many small things
“—and it’s not just one error. The typical accident
involves seven consecutive human errors. One …
does something wrong that by itself is not a problem.
Then ... another error on top of that, which combined
with the first error still does not amount to catastrophe.
But then ... a third error on top of that, and then
another and another and another and another, and it is
the combination of all those errors that leads to
disaster”

14. You already know
that things will go
wrong

15. Just like Outliers says, often
times it’s many things and not
just one.
This goes for bugs as well as
ways for us to improve ourselves

16. Learn
! This keeps coming up
! Work with the team to understand the more fragile parts
! Work with the team to understand some nuances
! Work with your team to be a more cohesive unit -- there can be some
negative side effects to this when you all start thinking too similarly.
! Never stop working to improve yourself

17. Data
Not to be confused with “big data”

18. LOGS
! Can understand more about the system then you know
! Can generate tests off logs
! Can get metrics what is being used or not used
! Can go back to see if you covered something
! Can understand the flow of data through the system
! Use an artifact when explaining something
! What would be useful information for you to have?

19. Test more effectively
When you have all these tools and you can continually work on improving yourself
you are invaluable.
Work with your team
Understand
Know what to test
What can you group together
Diagnose!

20. What can we do?
! Appreciate others and their work
! Be a team player
! Be open to the fact that someone’s mental image is different
! Be understanding of constraints out of your control
! Try to see the issue from a different perspective
! Investigate!!!
! Consider that it could be multiple causes, and not just one
! Improve your knowledge
! Work with the team to become a more valued contributor