QA–QC Arena – Software Testing Home for beginners and experts

Software Testing Mnemonics


A Mnemonic is a kind of tool or technique that can assist in remembering information.

I reckon many of us can recall a mnemonic VIBGYOR (Violet–Indigo–Blue–Green–Yellow–Orange–Red, in English) or तानापिहिनिपाजा (तांबडा, नारिंगी, पिवळा, हिरवा, निळा, पारवा, जांभळा, in Marathi) that we have used for remembering the colors of the rainbow (during the school days).

Do you use any mnemonic in day-to-day life?

How about Software Testing; do you use any Software Testing mnemonic? 😇

Here are some of the Software Testing mnemonics that you can use -

🎯 RIMGEA – Bug Advocacy Mnemonic (by Cem Kaner)

🎯 SFDIPOT – Test Strategy Heuristic (by James Bach)

🎯 CRUSSPIC STMPL – Quality Characteristics Heuristics (by James Bach)

🎯 TERMS – Test Automation Mnemonic (by Albert Gareev)

🎯 GUIDABLE INCLUSIONS – for Mobile App Testing (by Brijest Deb & Shivram Mani)

🎯 There are many Software Testing mnemonics available on the internet, you can search for them and start using them as per your need.

Also, if you have ever created your Software Testing mnemonic, then do share it with the community.

If you have any questions and want to connect with me? Feel free to book a 1:1 meeting.

Keep Learning, Keep Growing 👍

Do you meet another Software Testing professional (besides regular work)?


As a Software Testing professional, do you meet another Software Testing professional (besides regular work) and have a long chat over Tea/Coffee?

The respective Tester could be your friend, someone from your Team, from a different Team, or maybe from a different organization, playing a different role and having a different set of responsibilities. If you haven't tried this so far, do try it out.

What can be discussed during this meeting?

🎯 Exchange of day-to-day experiences (in the context of Software Testing)

🎯 Discussions around today's Software Testing Trends, Job opportunities, etc. (in addition to the future of Software Testing)

🎯 Discussions around a variety of Domains

🎯 Experience based Tips and Tricks

🎯 Tools & Technologies (experiences and recommendations)

🎯 Software Testing Books (experiences and recommendations)

🎯 Training and/or Certifications (experiences and recommendations)

🎯 Experiences about past Software Testing Events (Meet-ups, Conferences, Webinars, etc.) and recommendations about upcoming once

🎯 Experiences with past Software Testing Competitions and recommendations about upcoming once

🎯 Discussions around a variety of learning platforms

🎯 Discussions around Software Testing Fundamentals

What are the benefits of such meetings/discussions?

🎯 It enables a unique platform to share your opinions, knowledge, and experiences without fear

🎯 It paves the way to learn from someone's experiences and knowledge

🎯 It brings different perspectives to look at Software Testing and the day-to-day work we do

In my opinion, everyone has different ways of learning and gaining knowledge. I reckon it's always good to experiment with the way we learn.

So, which Software Testing professional are you planning to meet over this weekend? 😊

Feel free to tag them and decide the plan, and yes do enjoy your Tea/Coffee. 😛

If you have any questions and want to connect with me? Feel free to book a 1:1 meeting.

Keep Learning, Keep Growing 👍

Software Tester and Documentation


As Software Testers, while doing our day-to-day job we need a lot of information. Maintaining or documenting this information in an organized way becomes a very crucial task.

Documentation may include (but is not limited to) as below -

🎯 Test Cases

🎯 Test Plans

🎯 Bug Reports

🎯 Test Data

🎯 Testing Checklist (Product &/or Project specific)

🎯 Regression Test Suites

🎯 Automated Checks

🎯 Test Environment Details

🎯 Database Details (Connection info, Credentials, Tables, etc.)

🎯 Product knowledge

🎯 Setup/Configuration Details

🎯 Tools (that aid Testing activities) Details

🎯 Any other information that can aid in Testing

In my opinion, we should always put consistent and conscious efforts to capture the information that can help us in the future.

🎯 As an example, let's say you are exploring a specific workflow within your application. During this exploration you struggle with the required data creation, you receive some error and/or warning messages in between, and you miss out on some pre-requisite setups or configurations. To move ahead in completing the workflow, you reached out to team members (Testers/Developers/Product) and got all your issues resolved.

🎯 In such cases; I reckon it's very important to capture all the information that has helped you along the way. This does not just help you in the future, but also it may help you to assist someone as and when needed.

🎯 With the interest of time, on every occasion, it may not be feasible to prepare a well-polished document or notes and this is fine. However; one should attempt to capture the information in whichever form and tool it's feasible then.

Food for thought -
When it comes to documentation, this is my own favorite quote "Information Dimag (
दिमाग) में रखो या रखो... Document में जरुर रखना... जरुरत पडने पर Dimag (दिमाग) नहीं काम आया तो Document जरुर काम आयेगा...", meaning "Keep the information in your brain or not... Must keep it in the document... If the need arises, if your brain does not help, then the document will come in handy..."

If you have any questions and want to connect with me? Feel free to book a 1:1 meeting.

Keep Learning, Keep Growing 👍