Quality starts with requirements. In small to mid-size companies, it is not uncommon for the communication chain to be broken. Florin Ursu shares ways to avoid miscommunication through a streamlined process in which requirements are communicated to both developers and testers simultaneously; then developers write code while testers document what will be tested. Florin explores what mindmaps are; what they can be used for, both in general and applied to software development; and then dives deeper into how mindmaps can be used for testing. He describes how his teams use mindmaps to brainstorm, organize testing scenarios, prioritize work, review test scenarios, present results to stakeholders highlighting what was tested and—just as importantly—what was not tested, issues found, and risks. Using example mindmaps, Florin highlights important details captured in day to day work, including tips regarding format, communication style, and how to “sell” the idea of mindmaps to your stakeholders.

1. W6
Session
10/26/2016 11:30:00 AM
Design for Testability in Practice
Presented by:
Nir Szilagyi
PayPal
Brought to you by:
350 Corporate Way, Suite 400, Orange Park, FL 32073
888-­‐268-­‐8770 ·∙ 904-­‐278-­‐0524 - info@techwell.com - http://www.starcanada.techwell.com/

2. Nir Szilagyi
PayPal
Senior quality engineering manager Nir Szilagyi brings more than sixteen years of
experience to the risk platform engineering team he leads at PayPal. Previously at
eBay, he led the products platform quality engineering team in Israel and US. In
both companies, Nir led the team transformation from a classic advisory group to
an agile engineering team, focusing on quality throughout the product
development lifecycle. Passionate about automation and testing smarter, Nir
believes that agility, engineering solutions for quality, influencing testability, and
open communication drive organizations forward. Nir had been involved in
shaping eBay's test automation framework and is leading the development of
similar quality initiatives at PayPal.

3. External Use
Using mindmaps
Lightweight documentation
for testing
Florin Ursu

4. Using Mindmaps – lightweight
documentation for testing

5. Using Mindmaps – lightweight
documentation for testing

6. Documentation
A lot of it
NO Documentation!
Some
Documentation
What will I test?
What are my priorities?
What did I test?
What did I NOT test?
What are my
observations?
Risks?
Did I find any issues?
Documentation

7. Using Mindmaps – lightweight
documentation for testing

8. Using Mindmaps – lightweight
documentation for testing

9. What are the mindmaps?
• Mind mapping techniques have been around for a while,
with origins going back several hundred years.
• Mind mapping in testing has become popular in recent
years as it assists in lateral thinking and allows complex
information to be presented in a simplified visual form,
making important relationships visible. This can assist
teams with key tasks including:
• Creating test plans;
• Designing test scenarios;
• Choosing effective test data.

10. Which tool did we adopt for Pong Studios?
•The tool I chose for mindmaps is MindMaple
• Cross platform: PC, Mac, iOS
• FREE (paid version also available with some non
essential additions)
• Ability to export to Microsoft Office
• Accepts attachments and notes
• Visually integrate important task details
http://www.mindmaple.com/

11. • "Mind map": A mainly-hierarchical diagram used to organize
information, ideas and understanding of a topic. It is a type of
diagram that can aid visual thinking, learning, planning and
creativity.
• A mind map is a diagram for representing tasks, words, concepts,
or items linked to and arranged around a central concept or
subject.
• A mind map uses a non-linear graphical layout that allows the
user to build an intuitive framework around a central concept. A
mind map can turn long list of monotonous information into a
colorful, memorable and highly organized diagram that works in
line with your brain's natural way of doing things.

12. Historical use
• “Visual mapping” can be traced back to 3rd Century CE by Greek philosopher
Porphyry of Tyre’s Tree of Porphyry
• 692 CE - graphical representation of the outline of the Bible
• 1527 - Dante’s Divine Comedy published by Panganino & Alessandro Paganin
• 16th Century - “Treatise on the virtues of excellence, and how one may acquire
them.” by d’Anguerrande
• 1664 – religious visual representation by John Bunyan, of Pilgrim’s Progress fame
• 1957 – Walt Disney produced a visual representation of his business model and
relationships between organizational units
• 1974 – Tony Buzan on BBC television series “Use Your Head” introduced the term
“Mind Map”

13. Mind Mapping in Software Testing
Where can you use mind mapping in software testing?
• Test Planning
• Test Strategy design
• Test Plan design
• Test Case Design
• Test Data planning
• ** ANYWHERE ** where thought, creativity, analysis, design,
planning, etc. is required

14. • In our team, we use
mindmaps for:
• Structuring test plans
• Presenting test plans to
stakeholders
• Prioritizing tests
• Exporting to test cases
• Presenting test results
and highlight:
• Completion percentage
• Level of confidence
• Risks

15. Intuitively we might build a mindmap
like this

16. Standardizations adopted
• Format – Growth Direction – Right
• Style – Branch Shape – More – Rounded Elbow/Outside

17. Conventions adopted
• Priorities
• Percentage of completion
• Resources
• Pass/Fail Test Cases
• Trickle Down quality
indicators

18. I see what you did there…
Documentation
A lot of it
NO Documentation!
Some
Documentation
What will I test?
What are my priorities?
What did I test?
What did I NOT test?
What are my
observations?
Risks?
Did I find any issues?
Documentation

19. Example mindmaps
• Creating a mindmap – Mindmapple demo
• Initial mindmap
• Priorities
• Resources
• Testing results mindmap
• Priorities
• Resources
• Completion level
• Level of confidence
• Example mindmap

20. Group Exercise
Create the mindmap needed
for testing a basic calculator
to the level that it can be
presented to the stakeholders.