Yoda’s ‘The Way of the Jedi Tester’: A Guide for Agile Testing
A fun little post imagining how Yoda might train software testers.
Join the DZone community and get the full member experience.Join For Free
yoda’s software testing principles for thriving in an agile environment
did you know there’s more than just one force? yes, there’s the one that has to do with the connection of all living beings, but there is also one within software known as quality. an old friend of mine, yoda, recently visited me at a place in a galaxy far, far away called uruguay and attended the conference, testinguy. after attending the session, “the agile death of the tester,” that i gave with agile consultant gabriel montero , he wanted to spread our message to all of the testers across the tech-iverse who are entering into the agile galaxy.
here yoda wrote the principles that he gleaned from it for testers to survive agile which he gave to me to share with you today.
impossible to see, the future is, but after all of my years of living, i, jedi master yoda, can foresee the longevity and ubiquity of agile. agile is an approach to software delivery that focuses on incremental improvements and quick adaptation to change which is sweeping through the “tech-iverse.”
according to the world quality report 2015-2016, which surveyed over 1500 testers, 54% said they had adopted agile. but, without its challenges, it hasn’t come. the most reported challenges were: difficulties in identifying the right areas on which testing should focus (33%), lack of appropriate test data and environment (31%), and a lack of professional test expertise in agile teams (31%).
so why do these challenges arise? well, young jedi tester, the traditional paradigm of a tester is not that of an agile team member.
at what agile means, let’s take a look. being agile means you commit to these values which form the agile testing manifesto:
people and interactions over processes and tools
working software over extensive documentation
customer collaboration over contract negotiation
responding to change over following a plan
herein, the dilemma lies. in the traditional paradigm of testing, testing is not agile because testers:
form an independent team that is part of a process or phase in development (usually left for the end)
write test cases based on requirement specifications
write test cases based on the customer contract
create test plans and maintain those tests
so, you testers seem to work counter to agile, but… fear have you not! there are ways that you can keep up with the changes so the software world doesn’t desert you like those in my world deserted poor planet tython. it is time to unlearn the way you used to think about testing. instead of seeing yourselves opposed to developers as the light side is opposed to that of the dark, the force of software quality should bring you together to create software that customers and end users love.
here’s how you can navigate the agile galaxy, a place where you can rise up to the occasion to be a jedi tester. like the jedi warrior who protects peace and justice in my universe, the jedi tester is one who defends and protects software quality, enhancing the overall software development process, instead of being involved only at the end.
the way of the jedi tester
principles, here are, of the way of the jedi tester in the agile galaxy of the tech-iverse. in mind, keeping, i am talking about agile in general and apply to any tester, these can. keeping also in mind that agile doesn’t necessarily mean rapid development, but adaptive development, responsive to change as requirements tend to change. i will go over how the jedi tester adds value during three main activities of agile: planning, doing (development), and analysis for improvement (review).
principle 1: in the whole process of releasing a new feature or version, from day 0, participate you will.
normally, in the beginning, stakeholders specify and “close” the requirements document, sign a contract, and then plan how to do these requirements. in agile, the requirements are not closed, so there is not so much documentation because it is always kept in mind that the requirements will change making it futile to spend time documenting them.
so, what can the jedi tester do? help with these planning activities of agile teams, he or she can:
● estimation, considering the testing activities to be conducted
● prioritization of functionalities, as he/she has a wider view and can see the big picture
● defining acceptance criteria. yes, after understanding what the customer wants, the tester helps to define the product!
● creating a test strategy. how will the team go about testing? for example, by implementing tdd (test-driven development), the entire development mindset will change, shifting the focus to testing (next principle, see the).
principle 2: over the detection of bugs, focus on the prevention.
according to cem kaner, testing is a technical and empirical investigation done to provide stakeholders information about the quality of a product or service. in his definition, he is mentioning detecting and reporting errors, but a jedi tester should be able to also prevent them.
to do so, it is important for testers to ask as many questions as possible before diving into development. this way, both the developers and the customers will imagine a clearer, more thorough image of what they want to make and will have to tackle issues before they arise that you, the tester, have already thought about. for example: will we need to make multiple versions for different browsers? will the end user favor design simplicity or performance?
from the initial planning activities, testers should be advocates for changing the traditional paradigm of testing from the one that views it as a later stage in development focused on the detection of bugs to one that views it as an activity carried out in parallel with development to prevent bugs.
software development activities
principle 3: using exploratory testing and other activities throughout development, be you concerned with delivering quality products.
now you don’t have the input, or all of the normal things that testers are used to working with like contracts, requirements specification documents, use cases or anything that tells you how the system is supposed to behave and so, it’s not that easy to write test cases. test cases helped you to know how to test, with what data, in what context, pre- and post conditions, expected results, etc. how are you to ensure quality without the things you have always held so near and dear? don’t worry, you already know and have everything you need. have you the skills to survive, but use them differently you must.
not so well suited for agile are test cases in the first place because they require a lot of maintenance and do not quickly adapt to change. so, the jedi tester must seek out lighter alternatives without diminishing the quality of testing or control. instead of basing everything on test cases, the jedi tester must change the strategy, aiming to minimize the time dedicated to maintaining documentation and increasing the time taken to add value.
to do so, today’s agile testers are phasing out test cases like last millennium’s light sabers, relying more heavily upon activities like mind-mapping, writing checklists, and doing exploratory testing.
exploratory testing, above all of those activities is one of the best ways can add value during agile development the jedi tester. exploratory software testing is a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. lisa crispin and janet gregory, in their book , “ agile testing: a practical guide for testers and agile teams” state that, “testing an application with a plan to learn about it as you go, and letting that information guide your testing, is in line with valuing working software and responding to change,” therefore it’s inherently agile!
so, whenever you do exploratory testing, you can be agile, even if the jedi tester is not working on an agile project. and, as the jedi tester constantly changes his or her testing, he or she can constantly optimize the value of their work instead of following the same procedures again and again that don’t provide the most value nor allow for creativity.
principle 4: becoming everyone’s responsibility, qa is. forming one unified team, work alongside developers.
traveling to the agile galaxy, one hears much discussion of test automation. test automation can occur along all stages of development from unit testing to testing on the ui level. highly effective it is to automate as many tests at the unit level, which also makes qa the developer’s concern. in this way, developers and testers both bare the responsibility of tending to the force of software quality, further uniting them as members of the same team.
to make this principle work, the jedi tester must foment collaboration as much as possible, substituting the “i” in testing for the “we” in the creation of high quality software.
principle 5: the last stages of scrum: inspection and adaptation, participate in you will.
validating product growth and giving and receiving feedback, the team does in this phase. what can the jedi tester do? due to your exploratory nature, you have a more comprehensive understanding of product features so during the product review, you can:
be an advisor to the customer and developers
it is also important to review the team’s processes as a part of the retrospective. a jedi tester takes advantage of these moments to give testing a voice and a chance for the opinions of testers to be heard not just amongst themselves. maybe the rest of the team didn’t realize that some issues could have been solved with the help of testing.
principle 6: by studying, participating in the testing community, seek professional growth continue to, you will.
and, a good jedi warrior never fails to improve over time strengthening his or her power to wield the force, even after formal training is complete. so, a good jedi tester is one who continually learns about new methods and tools, participates in the intergalactic testing community, etc. furthermore, makes an ultimate jedi tester, helping with the training of the next generation of jedi testers.
no matter what galaxy you live in (agile or waterfall) may the force be with you, meaning may quality be in everything you touch. may you choose the light side of the force to produce software that makes the world a better place instead of using it for evil. oh yes, be you can, agents of change within your organization and the entire tech-iverse!
i hope you liked this post! i’d like to acknowledge kalei white for helping me to write this post, as she is the one who is a fan of star wars who helped me out with the more creative aspects.
liked this post? try these:
Published at DZone with permission of Federico Toledo, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.