Nishi Grover
Member for
12 years 4 monthsNishi is a Consulting corporate trainer, Agile enthusiast and a Software tester at heart! With almost a decade of experience working in Agile environment in product-based companies, she has had a chance to work in all stages of software testing life cycle. She now works at Agile Testing Alliance as a coach, trainer and mentor in areas of Agile, DevOps, agile testing, test automation, BDD using Cucumber etc. along with conducting QA Induction boot-camps and ISTQB workshops in corporates and as public courses.
In her spare time she likes reading and sharing knowledge about Software Testing, Agile and various aspects of software testing processes and practices. She is certified by Agile Testing Alliance (ATA) as a CP-DOF, CP_SAT, CP-AAT, CP-MAT and by ISTQB as a Foundation and Advanced Test Analyst and likes to keep updating her skills periodically.
She is passionate about writing on new topics of interest in the industry and also on her own blog at www.testwithnishi.com
All Articles by Nishi Grover
All Stories by Nishi Grover
|
Using Tours to Structure Your Exploratory TestingIn testing, a tour is an exploration of a product that is organized around a theme. Tours bring structure and direction to exploration sessions, so they can be used as a fundamental tool for exploratory testing. They're excellent for surfacing a collection of ideas that you can then further explore in depth one at a time, and they help you become more familiar with a product—leading to better testing. |
|
Paying Off the Technical Debt in Your Agile ProjectsJust as you should not take out a financial loan without having a plan to pay it back, you should also have a plan when incurring technical debt. The most important thing is to have transparency—adequate tracking and visibility of the debt. Armed with the knowledge of these pending tasks, the team can devise a strategy for when and how to “pay off” technical debt. |
|
Let the Agile Manifesto Guide Your Software TestingAlthough its values are commonly associated with agile software development, the Agile Manifesto applies to all people and teams following the agile mindset, including testers. This article examines the four main values of the Agile Manifesto and reveals how they can bring agility to test efforts—improving quality for your team and your customers. |
|
5 Ways Agile Testing Is Different from Traditional TestingIt’s the distinctions between agile and traditional software development approaches, as well as the adaptability of testers in these very different environments, that makes agile testing different from traditional testing. Agile demands more from its testers, and, in turn, it values them more, too. Let’s look at five main things that make an agile tester’s life different from that of a traditional tester. |
|
Don’t Guess Your Tests—Strive for Complete Requirements Many teams struggle with test creation due to miscommunication or a lack of requirements, testers not being present during design phases or discussions, a shortage of time, or incomplete information. But that doesn’t mean you should turn to guesswork. Your tests will suffer in quality and completeness. We must always strive to get the desired requirements. |
|
The Real Key to Agile Success: Communication Think about the common practices of an agile team: daily stand-up meetings, retrospectives after every sprint, pair programming and buddy reviews, collaborating with customers, and more face-to-face time instead of mountains of documentation. What is the agenda behind all these operations? Frequent and open communication. |
|
5 Ways Testers Can Mitigate Practical Risks in an Agile TeamTesters who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid. |
|
Using Agile Pods to Realize the Potential of Your Team Agile pods are small custom agile teams, ranging from four to eight members, responsible for a single task, requirement, or part of the backlog. This organizational system is a step toward realizing the maximum potential of agile teams by involving members of different expertise and specialization, giving complete ownership and freedom, and expecting the best quality output. |
|
Automation Test Suites Are Not God! In today’s age of tight deadlines and accelerating delivery cycles of software, test automation is surely favorable for the world of functional testing and critical to the success of big software development companies. But its various benefits have led to unrealistic expectations from managers and organizations. This article highlights the role and use of automation in an agile context and the irreplaceable importance of manual testing. |