Test engineering is hard, even harder than software development. Being test engineer puts you in a wider context, with no clear boundaries. You have to find those by yourself. This requires courage. Courage to take action, courage to make mistakes. As a test engineer, you do mistakes every day. You do them so often that sometimes you feel you can predict the future. Scientific explanation to this phenomena is patterns recognition. It is an ability of our brain to match the information from a stimulus with information retrieved from memory. Defect prevention is hard. Together with technical skills one have to develop high social awareness. Working on safety nets never was so important, different types of checks on different levels to make sure software is reliable and serves its purpose to the variety of everyday use-cases. We know that life is so complex and sometimes complicated which makes it impossible to predict all possible outcomes and scenarios. But striving for excellence never was so important as nowadays in such an open, transparent and competitive environment.
Goal of my talk will be to show you my everyday job as a test engineer. Not only how to look for defects, but how to prevent them from happening. Not only how to automate tests(noun), but how to build safety nets to minimize end-user impact. Not only how to inform testing status but how to influence quality on company level.
Ch10-Global Supply Chain - Cadena de Suministro.pdf
What does it mean to be a test engineer?
1. WHAT DOES IT MEANTO BE
ATEST ENGINEER?
Andrii Dzynia
http://bit.ly/1GYquoR
2. MY BACKGROUND
• 8 years in software engineering
• started as a test engineer in a team of 20 testers
• currently working on improving product quality
and development productivity at Spotify
https://www.linkedin.com/in/andriidzynia@adzynia
7. WHAT DID I LEARN?
• Software always has bugs. If
you have not found any, does
not disprove their existence
• Developers do not spend
much time looking for edge
cases, testers do
15. FAULT MODELS
“From the model, the designer or user can predict
the consequences of a particular fault.” - Wikipedia
video: https://www.youtube.com/watch?v=rEumMkAhwzA
17. BASED ON EXPERIENCE BRAIN RECOGNISES
SEQUENCES WHICH LEADSTO UNDESIRED
OUTCOME.
NOTE: BE CAREFUL WITH FAULTY ASSUMPTIONS.
FACE ONTHE MOON SURFACE IS PAREIDOLIA.
“Pareidolia is a psychological phenomenon when the mind perceives a
familiar pattern of something where none actually exists.” - Wikipedia
18. LOOK FOR PATTERNS WITH
HIGH FAILURE RISK.
video: https://www.youtube.com/watch?v=qoQssWPRNR0
22. SOLUTION WAS
Create a #slack channel
Start asking video integration questions
Rise bugs early and facilitate conversations
23. DID WE PREDICTED ALL DEFECTS BEFORETESTING?
SURELY, NOT.
Data collected by Stefan Rungardt
24. BUT HOW DIDTHAT HELP?
Integration ended up to be much easier
Testing started earlier
# of production issues was low
25. WASTHAT EASY?
Not really.You have
to ask questions
people do not want
to hear
http://media2.giphy.com/media/wrTHBbla7suPu/giphy.gif
26. Tester: Shall video be playing when I lock a screen?
Programmer: I do not know.
Tester: who can know?
Programmer: Product manager?
Product manager: I do not know.
Tester: who can know?
Product manager: let’s take a look howYoutube does it.
After a while we figured why video has to be paused
when you lock a screen. Licensing constraints.
30. ENGINEERING QUALITY
• Start testing as early as possible
• Build safety nets
• Fix bugs as fast as they occur
• Conduct root-cause analysis and take actions
http://www.slideshare.net/AndrewDzynia/quality-built-in
31. PRODUCT QUALITY
• Product success metrics
Time to first video frame
Number of users streaming video content
Average viewing time, etc.
• Number of production defects
33. TAKE AWAYS
• Testing is a process, not a set of artefacts
• Cost of defect can be lowered.Think about that
• Find ways to influence quality on organization
level. It is hard, but possible, even for a test
engineer