Talk: Mindmap Driven Testing
Speakers directory
Speaker:
Prashant Hegde
Talk description
Title:
Mindmap Driven Testing
Short synopsis:
Tester’s are expected to create several test artifacts during the process of software testing. The traditional test artifacts are time-intensive, bulky and their structure does not support the agile approach of software development. Traditional documents are hard to create, update, review and modify making them anti-agile. When working in an agile environment testers work in highly compressed test execution cycles. Testers never have enough time to test. The stakeholders, on the other hand, are in an urgency to roll out their products to the end-users. When such is the case testers cannot spend too much time in test documentation. According to “State of Testing 2017” – There is a notable jump from 51% to 63% for testers that are handling documentation. Overall we continue to see a constant increase in the amount of formal testing documentation written. But are these documents adding value? Not really. Most of the test documents created go out of date very quickly as they cannot embrace changes. If testers spend too much time in documentation, they might end up having very little time to do actual testing. Documentation is NOT testing but rather a chief distraction in software testing. A mindmap is a diagram used to visually organize information. It can be called as a visual thinking tool. A Mindmap allows complex information to be presented in a simplified visual form.Mindmaps make a perfect lean test artifact. In accordance with lean principles, mindmaps should reduce waste and amplify learning. Mindmaps not only reduce waste by avoiding extensive formats at the same time trigger creative thoughts to come up with awesome test ideas that will uncover more defects. We will discover how lean test artifacts created using mindmaps can save a tremendous amount of time involved in test documentation. The participants will learn how to reduce waste by avoiding extensive formats for test documentation The presentation will deep dive into every stage of agile testing and how mind maps can add value. Mindmaps can be used in all the test stages from test planning to test case execution.
Max size: 500 chars
Long synopsis (optional):
A mindmap is a diagram used to visually organize information. It can be called as a visual thinking tool. A Mindmap allows complex information to be presented in a simplified visual form. A mind map is created around a single concept. The concept is represented as an image in the center to which the associated ideas are added. Major ideas are connected directly to the central concept, and other ideas branch out from those. A mindmap is a great tool for note-taking, planning, studying, brainstorming, etc. The term 'mind map' was first used by Tony Buzan in 1974. I drew my first mindmap when I was in school. I preferred mind-mapping over text notes and it proved to be a great aid to revise and recall the concepts quickly. This is because the information in mindmap is structured in a way that mirrors exactly how the brain functions - in a radiant rather than linear manner. A Mind Map literally ‘maps’ out your thoughts, using associations, connections and triggers to stimulate further ideas. In my presentation, we will deep dive into the history and science behind mind maps. The participants will learn how to draw a mindmap right from scratch using the best practices. Tester’s are expected to create several test artifacts during the process of software testing. The traditional test artifacts are time-intensive, bulky and their structure do not support the agile approach of software development. Traditional documents are hard to create, update, review and modify making them anti-agile. When working in an agile environment testers work in a highly compressed test execution cycles. Testers never have enough time to test. The stakeholders, on the other hand, are in an urgency to roll out their products to the end users. When such is the case testers cannot spend too much time in test documentation. According to “State of Testing 2017” – There is a notable jump from 51% to 63% for testers that are handling documentation. Overall we continue to see a constant increase in the amount of formal testing documentation written. But are these documents adding value? Not really. Most of the test documents created go out of date very quickly as they cannot embrace changes. If testers spend too much time in documentation, they might end up having very little time to do actual testing. Documentation is NOT testing but rather a chief distraction in software testing. Mindmaps make a perfect lean test artifact. In accordance with lean principles, mindmaps should reduce waste and amplify learning. Mindmaps not only reduce waste by avoiding extensive formats at the same time trigger creative thoughts to come up with awesome test ideas that will uncover more defects. We will discover how lean test artifacts created using mindmaps can save a tremendous amount of time involved in test documentation. The participants will learn how to reduce waste by avoiding extensive formats for test documentation The presentation will deep dive into every stage of agile testing and how mind maps can add value. Mindmaps can be used in all the test stages from test planning to test case execution. Mindmaps can be used for: - Test Planning - Requirement analysis - Impact analysis - Task allocation - Test case design - Traceability - Test reporting - Quick test reports Tools - There are tons of commercial and open-source tools that lets us visualize your ideas as a mindmap. During my presentation, we will discuss a few free tools that can be used for collaborative mind mapping that best suite testing teams. Test Planning While test planning, testers can draw an initial mindmap keeping in mind the list of tasks, schedules, tools, roles, responsibilities, milestones and present the mindmap and discuss it with the stakeholders. We modify the mindmap easily by adding or deleting nodes on mindmaps. Mindmap's are incredibly flexible to changes.This flexibility might not happen when you draw on a paper, but a mind mapping software assists any changes easily. The final mind map shows the scope of testing in one glance. The final version of the mindmap can be used as a blueprint or later converted into a plan. This ensures that no test activity is missed. In my presentation, we will learn how to create a lean test plan using two simple approaches -1.In scope/Not in the scope test plan 2.Using 5w's technique Test case Design Mindmaps are an efficient way of creating lean test cases. It reduces the time required for creating test cases yielding better results. Mindmaps are very easy to maintain and are flexible to changing requirements. Draw branches from every user story/epic and associate all its functionalities as sub-nodes .Start adding test ideas/test cases for each functionality. I created a mindmap covering test ideas for the major functionality. My team started to expand the mindmap by branching out more and more test ideas. We kept adding new nodes when we found unique scenarios that uncovered the bugs during our test sessions. This drastically increased our test coverage. The final mindmap can be as the basis for test case document or it's cool if it's used as it is. The best part of mind mapping is that we generate more ideas when drawing them. Collaborative mind mapping with the team gives you the best results. In my presentation, we will learn how to design lean test cases to boost our test coverage using 4 innovative approaches - 1. User Features 2. Types of Testing 3. Heuristics and Nmemonic's 4. Free Style Traceability Mindmap A traceability matrix is an essential tool for every tester to analyze and improvise the test coverage. Testers can use a mindmap instead of a tabular traceability matrix. To create a traceability mindmap - we need to add nodes of all the Epics. Draw branches from every module and associate all its user stories as subsequent nodes. Then link the test cases for every module. We can link the 'requirement number' of the test management tool.This ensures that we have not missed out on writing test cases for any user story. This mindmap gives us the birds-eye view of your test coverage. We can identify the areas where we need to strengthen our coverage
Max size: 5000 chars
Tags:
Speaker directory:
Listed in directory
Not listed
Speakers directory