Some consultant companies will not eliminate all the risks by offering an automagic solution (Perhaps a revolutionary testing tool). However, it could give better possibilities for applications to be evaluated in case of quality gaps and deliver accurate applications for the consumers. We see products/services failing before any launch or retiring a couple of months later.

Are you someone who has heard of mind maps and always wondered what it is? You tried your hand at one and couldn’t figure out how to apply it to your context. You have arrived at the right spot. This article intends to dive deep into mind maps and demonstrate how to use them for software testing. So, free your mind and enjoy the ride. Let us start with the fundamentals: “What is a mind map”. A mind map is a visual representation of an idea.

I began learning about accessibility as part of the first digital project I worked on. I found the subject fascinating and decided to keep on learning as my small way of making the world a little better for people. One of the main things that struck me, in the beginning, was that a lot of the things I was learning I sort of already knew, I’d just not invested any time really thinking about it.

This is Part 5 of the Requirement Gathering Blog series by Rahul Parwal where we explore more on Dealing with Objections. We’d like to thank him for sharing his expertise with the community through this information-packed piece. When facing the issue of lacking proper documentation of requirements, it is important for testers to shift their perspective and focus on the needs and wants of the end-users or customers.

This is Part 4 of the Requirement Gathering Blog series by Rahul Parwal where we explore more on Exploring Requirements. We’d like to thank him for sharing his expertise with the community through this information-packed piece. As a tester, being involved in the ideation stage is crucial in ensuring that the testing issues that may arise later on due to false assumptions are addressed early.

One of the attendee at a recent meetup I hosted(on behalf of MOT KL) asked this interesting question. Even though I answered it, the time constraint didn’t let me elaborate enough. So let me start with an apology for that and this article is in return to that question, based on my understanding of the concept. I believe this article will help you to understand the concept & moreover gives some ideas on “How to keep our Tests relevant“.

This is Part 3 of the Requirement Gathering Blog series by Rahul Parwal where we explore more on Exploring Requirements. We’d like to thank him for sharing his expertise with the community through this information-packed piece. Check out the blog on Requirements in The Agile World for Part 2 of this series.

Test management is an important aspect of software testing. Tools for test management are used to organize testing activities, report the progress of QA activities and maintain information on how testing is done. Test management tools in software testing help teams create and manage their test cases by providing the right features and functionalities. There are both proprietary and open-source test management tools available. Each tool has its pros and cons.

Cypress is an open-source end-to-end testing framework that is used for web applications. It is a JavaScript-based testing tool that is designed to make testing web applications easy and efficient. Cypress is built on top of Mocha, a popular JavaScript test framework, and it uses Chai for assertions. On the other side, Microsoft’s Playwright is a relatively new open-source test automation framework.

Following is a transcription of the AMA session with Rahul Parwal on the topic – Bug Advocacy. Here Rahul brings forth the importance of bug advocacy, its step-by-step implementation, and tips on making this process easier. We recently launched a course on Bug Advocacy instructed by Rahul Parwal. You can check the course out from our courses section.