Thinking Out of the Box While Testing Software!

“Out-of-the-Box Thinking” or “Creative Thinking” are phrases we often stumble upon in our professional environment or in our routine life.

Ever tried to understand what it signifies when we utter “Thinking beyond the Box”?

As per Wikipedia: “Thinking beyond the box means thinking in a unique manner, unconventionally, or from a new viewpoint. This phrase typically represents fresh or Innovative thinking”

Still, the above description can be applied in our domain: Software Testing.

At the threshold of the software testing realm, the initial thing introduced or learned is the Two Boxes – a white box and a black box. After grasping it, we usually indulge in either black box testing or white box testing. This confines our thinking within the limits of these boxes.

Did you ever contemplate that stepping outside the black box or white box testing could elevate our Software Testing profession to unprecedented levels?

Ways To Implement While Performing Software Testing

In this part, we will explore a few techniques that I and numerous of my Mentors use during Software Testing:

Fast-track Test Case Creation

This method, as the name denotes, implies quickly formulating test cases. It is a people-centric approach to testing that directly links testing to human performance.

When we talk about test case formulation, the initial aspects that strike our mind are a Requirement Document, an Excel Sheet, and company regulations. However, momentarily disregard these constituents and ponder what you think needs validatory testing.

Armed with a Pen & a Paper, note down as many scenarios as you are able to in 60 seconds. Redo the process until you’re out of scenarios or solutions, and at the end, revisit them.

You will be astonished at the amount of ideas/test cases you already have without contemplating the requirement document.

Cross Testing Ideas (Analogy)

Prior to starting testing on an application, remember a similar application you have utilized previously. This will allow you to recognize problems that don’t pertain to the requirements but signify a common/generic feature that should be housed in the application but might have been missed.

An instance would be: If you are testing a portal, operate it like your email service or any other application you have interacted with before, and notice how the application acts.

I remember uncovering a crucial defect employing this method. While inspecting a secure login for a finance application, I tried to alternate the URL and divert to a different page (which was a defect in a previously examined application).

By doing this, I managed to bypass the login process using a Secure ID! This was neither a test case nor spotlighted by any other team member as a potential test scenario.

Inverse or Backward Testing Ideas

What’s the standard workflow you follow while testing? Isn’t it the precise steps utilized during application development: “Requirements >> Unit Cases >> Integration Testing >> System Testing,” or does another method exist?

Those engaged in application development tend to mull in a manner that covers most of the positive testing. However, end users may not always consider similarly. That’s why production defects or UAT defects persist even after several rounds of unit tests, integration tests, and system tests.

For instance, suppose the requirement states that you can upload a file that does not exceed a file size of 10 MB. Most testers start by uploading a 1MB, 2MB, 3 MB, or bigger file until they reach 10 MB or an error message shows up. But why not start with 10MB, then try 11MB, followed by 9 MB?

This example is essentially using Boundary Value Analysis (BVA). But, how many of us have attempted to use BVA in scenarios barring the input box?

Inquisitiveness

Every QA engineer should ideally comprehend the purpose of a requirement. Asking questions assist a QA Engineer to fine-tune their testing intent. If a QA Engineer masters the art of inquisitiveness, they will naturally excel at testing. Make sure that no questions, no matter how trivial or seemingly ridiculous, are disregarded.

Inquisitiveness also increases the Domain Knowledge of the tester.

Remember: “The only dumb question is the one left unasked.”

Investigating

Investigation turns out to be quite beneficial before initiating testing. Get accustomed to the issues faced by others while working on a similar task. For instance, if you undertake cross-browser testing:

Before executing tests, investigating the issues faced by others while using the same browser will aid you in recognizing defects before commencing actual testing.

Break: An Icebreaker

Testing can occasionally become repetitive and ideas may start to deplete. You might feel trapped, with none of the proposed solutions working, or you might be out of ideas. In such situations, taking a productive break can work miracles and assist you to resume from where you left.

A break can involve having a cup of coffee, staring out the window, or indulging in any activity that revitalizes you.

Final Thoughts

In addition to creativity, factors like timing, pace of idea implementation, and execution are vital. Forming an excellent idea is splendid, but what if it’s late for implementation?

The ideas mentioned above are just nudging the surface and can aid you in conceiving even more innovative ideas.

Extended Reading

• Software Testing Tasks – New Platform to Test Your Testing Competence and Share Practical Concepts
• What is Negative Testing and How to Write Negative Test Cases?
• 10 Skills to Transition Into a Great Tester: How A Tester Can Evolve Into A Great Tester
• Motivating Testing – How to Think Beyond Conventional Testing Boundaries?
• How Can a Tester Think as an End User?

---

This is a guest post by Mohit Khatri. The author excels in testing Banking Applications, Automation Testing Setups, and Security Testing. If you wish to guest post on this blog, go through the guidelines here.

If you have more innovative techniques that have aided you at any point, feel free to broadcast them in the comments section below.