Software Tester Expert evangelization
by Vasile Hriţcu
Day 1
•
•
•
•
•

Testers from Day 1
Learning by exploratory testing
Run of first “technological” test
“black” / “white-box...
Day 1 – Software Tester
First:
•Computer experience
•Played game
•Software/operating system/drivers installation
•“Hello, ...
Day 1 – Professional Software
Tester
Software testing
• Definition
• Role of a starter: (s)he is executing the tests
created by others
• “Hard” and “Soft” skil...
Testing pillars
•
•
•
•

Technology
Science
Mathematics
Logic

•
•
•
•

Psychology
Ergonomics
Communication
Professional
n...
Technology
•
•
•
•
•
•
•
•

Tested software application itself
Tools
Operating systems
Database
Networking
Frameworks
Prog...
Science (Physics)
• Statics and dynamics
• Abstraction (Modeling) and simulation
• Complexity
Complexity - Weather map
Mathematics
•
•
•
•

Metrics
Sets (w/ the finer vs. coarser test sets problem)
Graphs (w/ state transition testing)
Probab...
Graphs
Logic
•
•
•
•
•
•

Operations
Diagrams
Comparison
Critical thinking
Analysis
Lateral thinking
Operations & Diagrams
Psychology
•
•
•
•
•
•
•

Training
Learning
Assumptions
Continuous change
Heuristics
Role-playing
Human reliability
Change – be dynamic
Cognitive ergonomics
•
•
•
•
•
•

Perception
Memory
Mental workload
Work stress
Reasoning and motor response
Decision-maki...
Cognitive ergonomics
Communication
•
•
•
•
•
•
•
•

Reading
Writing
Conversations
Foreign languages
Document design
Common terminology
Methodol...
Common terminology
Professional networking
•
•
•
•

Contact of involved stakeholders
Part of domain groups
Part of testing groups
Visibility
...
Tester’s visibility
Acquiring the product expertise
One should acquire the product expertise after:
•fully understanding the software product
...
Acquiring the Company expertise 1
One should acquire the Company expertise after:
•knowing its entire suite of products
Al...
Acquiring the Company expertise 2
The Company expertise holder is:
•business savvy, having business kinesthesia
•able to s...
Involvement during the software
development process
Tester’s octagon of strengths
Stop
Acquiring the domain expertise
One should acquire the domain expertise, after:
•studying the software products of the
comp...
Expertise != Expert
• Horizontal evolution, beside a vertical one
• Gain another domain expertise (by repeating
the previo...
Becoming a Testing Expert
After:
•changes (depending on domain’s complexity)
•being recognized as a massive contributor to...
Don’t forget!!! As a tester:
•
•
•
•

I always tell the truth
I deliver good results
I’m efficiently using the tools and r...
Also:
• Make your point fully understood and
accepted by the customer
• Give 100% to your work
• Gather as much as possibl...
Q&A

Q&A
Thank you!
Software testing expert evangelization
Software testing expert evangelization
Upcoming SlideShare
Loading in …5
×

Software testing expert evangelization

246 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
246
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software testing expert evangelization

  1. 1. Software Tester Expert evangelization by Vasile Hriţcu
  2. 2. Day 1 • • • • • Testers from Day 1 Learning by exploratory testing Run of first “technological” test “black” / “white-box” First software application
  3. 3. Day 1 – Software Tester First: •Computer experience •Played game •Software/operating system/drivers installation •“Hello, world!” program with “test your code” experience
  4. 4. Day 1 – Professional Software Tester
  5. 5. Software testing • Definition • Role of a starter: (s)he is executing the tests created by others • “Hard” and “Soft” skills • Validate and verify
  6. 6. Testing pillars • • • • Technology Science Mathematics Logic • • • • Psychology Ergonomics Communication Professional networking
  7. 7. Technology • • • • • • • • Tested software application itself Tools Operating systems Database Networking Frameworks Programming …
  8. 8. Science (Physics) • Statics and dynamics • Abstraction (Modeling) and simulation • Complexity
  9. 9. Complexity - Weather map
  10. 10. Mathematics • • • • Metrics Sets (w/ the finer vs. coarser test sets problem) Graphs (w/ state transition testing) Probability (w/ equivalence classes to partition infinite input spaces into "testable" sets, risk-based testing, error guessing) • Statistics (w/ boundary testing, user profiling, reliability engineering) • Combinatorics (w/ pairwise, triple, or n-way combinations of a system’s test sets)
  11. 11. Graphs
  12. 12. Logic • • • • • • Operations Diagrams Comparison Critical thinking Analysis Lateral thinking
  13. 13. Operations & Diagrams
  14. 14. Psychology • • • • • • • Training Learning Assumptions Continuous change Heuristics Role-playing Human reliability
  15. 15. Change – be dynamic
  16. 16. Cognitive ergonomics • • • • • • Perception Memory Mental workload Work stress Reasoning and motor response Decision-making
  17. 17. Cognitive ergonomics
  18. 18. Communication • • • • • • • • Reading Writing Conversations Foreign languages Document design Common terminology Methodologies Practices
  19. 19. Common terminology
  20. 20. Professional networking • • • • Contact of involved stakeholders Part of domain groups Part of testing groups Visibility (project/department/company/industry)
  21. 21. Tester’s visibility
  22. 22. Acquiring the product expertise One should acquire the product expertise after: •fully understanding the software product Also, (s)he is: •creating/maintaining the Test Plan •participating to design review for new features •sometimes, the most knowledgeable person
  23. 23. Acquiring the Company expertise 1 One should acquire the Company expertise after: •knowing its entire suite of products Also, (s)he is: •involved in the initial communication phase and participating in the requirements meetings •the Test Architect, creating the Test Strategy •not involved (usually) in the execution stage
  24. 24. Acquiring the Company expertise 2 The Company expertise holder is: •business savvy, having business kinesthesia •able to see the bigger picture of the Company’s business approach and procedures •able to actively participate to its growth
  25. 25. Involvement during the software development process
  26. 26. Tester’s octagon of strengths
  27. 27. Stop
  28. 28. Acquiring the domain expertise One should acquire the domain expertise, after: •studying the software products of the competitors •working for the domain’s leader •the continuous study of alternative solutions •passive and active participation to technical and business domain’s events
  29. 29. Expertise != Expert • Horizontal evolution, beside a vertical one • Gain another domain expertise (by repeating the previous steps at a higher velocity) • The expertise is relative (contextual), the discipline Expert role is less relative, but never absolute (non-contextual)
  30. 30. Becoming a Testing Expert After: •changes (depending on domain’s complexity) •being recognized as a massive contributor to the quality of the software products •being a continuous participant to discipline events, technical publisher •being solicited to provide independent auditing
  31. 31. Don’t forget!!! As a tester: • • • • I always tell the truth I deliver good results I’m efficiently using the tools and resources I communicate and collaborate efficiently with all the stakeholders • I keep informed the clients about the risks/problems/limitations and improvements
  32. 32. Also: • Make your point fully understood and accepted by the customer • Give 100% to your work • Gather as much as possible information about the product/technologies • Don’t forget that everything is RELATIVE
  33. 33. Q&A Q&A
  34. 34. Thank you!

×