Mind maps are a creative way of gathering ideas around a central theme and categorizing them in concrete branches. Mind maps can be useful for both personal and professional life as an organization and visualization technique. They’re descriptive, easy and even fun.
In my latest post for Gurock blog, I showcase the usage of mind maps as a technique for test planning and test design. This tool’s capabilities make your documentation leaner and ideas more visual, which benefits the whole agile team. https://blog.gurock.com/agile-mind-map/
Be it test planning in an agile team which needs entire team’s insights and collaboration, or categorization of product features, test areas and backlog, Mindmaps can be used for all aspects and phases of the project.
Testers can generate their test ideas and have them categorized in a mind map around the central theme of the feature. The visual nature of a mind map helps them find more scenarios, see which parts are more heavily tested, and focus on main areas or branches. Once done, they can have other stakeholders take a look at it and get their opinions. This fosters brainstorming together and gathers the maximum number of ideas from the entire team.
Find useful tips to create your own mindmaps, as well as some samples for your reference in agile test designing as well as test planning. Read the complete article here -> https://blog.gurock.com/agile-mind-map/
My first experience with usability testing was on an agile team where the product we were building was being designed with the help of an in-house usability expert. He helped design the user interface (UI) of the application and conduct usability study on the beta version of the software to determine the ease of use of the application.
Though the experience was limited in terms of the interaction we had with the user representatives and the sessions conducted, the feedback we received opened up lots of new avenues for the tester in me around the learnability, understandability and attractiveness of the application I was testing.
Usability has matured a lot over the years. It’s now an essential software characteristic in today’s web and mobile applications. In my article published at the TestRail blog, I discuss ways of performing Usability tests and developing a mindset for Usability in an agile context.
The agile methodology focuses on building in quality from the very beginning of the software lifecycle. That is why we aim to find and fix defects early on: A defect found and fixed in an earlier lifecycle phase is a multitude cheaper than the same defect at a later stage.
But how can we more easily make it possible to prevent defects from percolating deeper in the software development lifecycle by fixing them in their nascent stages?
This is the main theme of my latest article for @Gurock TestRail blog – where I explore and explain ways to foresee, analyze and thwart defects in an agile context.
“Selenium Integration with Cucumber for an extended BDD framework”
This workshop will cover • Practical issues faced by most testing teams • Behavior Driven Development – the definition and need • Extending the Agile User stories and acceptance criteria in BDD scenarios • Cucumber as a BDD tool • Integration of Cucumber with Selenium in order to perform functional tests • Demo using Cucumber with Selenium with a real use case • Usage and Benefits of BDD In agile teams
For program details and complete agenda of the event, visit the website
The event will have enthusiasts exchanging ideas on advancing the present and future of Selenium and will bring together bright minds to give insightful talks pertaining to Selenium practice that are solution-focused, and foster learning and inspiration. * Solutions for Practical issues of testing. * Integration of Selenium with other testing tools. * Providing a key meeting place for Selenium Professionals and Executives from leading IT organizations. * A platform to share your research and experience
Looking forward to sharing my experience, learning from skilled professionals in the area and networking with the brightest minds at the event!
Every year we see the software industry evolving at a rapid pace. This implies changes in the way testing is conducted within the software lifecycle, test processes, techniques and tools, and the tester’s skill set, too.
I’ve been into agile for more than a decade, and I’m still learning, changing and growing each year along with our industry. Here are five of my key lessons and observations from 2018. I hope they help you in the coming year!
In my article published on Gurock blog, I talk about the 5 key learnings for Agile testers from the past year and how they will be key in planning your road ahead in 2019. The key learning areas discussed are —
The Agile Manifesto gives us 12 principles to abide by in order to implement agility in our processes. These principles are the golden rules to refer to when we’re looking for the right agile mindset. But are we getting the right meaning out of them?
In my latest article for Gurock TestRail blog, I examine what we mistakenly hear when we’re told the 12 principles, what pain points the agile team face due to these misunderstandings, and what each principle truly means.
Principle 1: Our Highest Priority is to Satisfy the Customer Through Early and Continuous Delivery of Valuable Software
What we hear: Let’s have frequent releases to show the customer our agility, and if they don’t like the product, we can redo it.
The team’s pain points: Planning frequent releases that aren’t thought out well increases repetitive testing, reduces quality and gives more chances for defect leakage.
What it really means: Agile requires us to focus on quick and continuous delivery of useful software to customers in order to accelerate their time to market.
I recently had a chance to chat with Mr. Thomas Cagley in an interview for his wonderful Podcast channel SPaMCAST. We talked all about Agile Testing, its differences from the traditional approach of testing, Agile Pods and the upcoming trends in the testing world!
It was a wonderful experience and I am grateful for having the chance to talk to one of the people I so look up to in the industry. Here is the link to the podcast show notes and info
A hardening sprint is an additional sprint that some teams run to stabilize the code and ensure that everything is ready just before release. Agile teams vary in their opinions on using hardening sprints in Scrum, but if your team does agree on having one before your release, there may be a lot to be done and varied expectations from the product owner, testers and developers. It may also lead to other work being delayed, leading to accumulation of technical debt.
An agile tester’s work life is intriguing, busy and challenging. A typical day is filled with varied activities like design discussions, test planning, strategizing for upcoming sprints, collaborating with developers on current user stories, peer reviews for teammates, test execution, working with business analysts for requirement analysis and planning automation strategies.
In my article for Gurock TestRail blog, I have explored a typical day in the life of an agile tester and how varied activities and tasks keep her engaged, busy and on her toes all the time!
Let’s sneak a peek into a day in the life of an agile tester — > You will go through the daily routine of an agile tester and will experience their complicated schedule in real time.