Why a Tester Needs to Think Out of the Box While Testing
Why a Tester Needs to Think Out of the Box While Testing

Software testing can be defined not only as a process to test software for bugs but also as a challenge that tests the skill and aptitude of professional software testers. Most software testing companies in Dubai require testers to be capable of thinking out of the box to overcome challenges and locate bugs effectively.

Thinking out of the box means the tester will have to think from a completely different perspective or just in an unconventionally creative way. Testers already have to deal with two types of boxes – the white box and black box. They program themselves to be good at white box and black box testing. However, they end up delimiting themselves in the process, losing sight of what lies beyond the boxes. 

Going beyond can not only help a tester learn new things but could also help his career grow along with his skills. Here are a few out of the box ideas conceived by some very creative testers.  

Rapid fire test cases creation

As the name suggests, this technique involves creating test cases rapidly without using requirement documents and excel sheets, and without following guidelines from the organization the tester works at. The tester needs to only list down every test case scenario he can think of, until he runs out of ideas. Remember that the tester will be doing this without using the requirement documents for reference. 

Cross testing ideas

This technique requires the tester to work from a different perspective. The application to be tested should be seen as something familiar i.e. the tester should see the application as something he’s already used before, and then test it. This will help the tester identify issues that are not part of the requirements – issues that are linked to general features such an application should have, that are often overlooked during development. 

For instance, if the tester is testing a portal, he can run test case scenarios based on his experience using other portals similar to the one he is testing.   

Backward testing ideas

There is a reason why production defects or UAT defects still exist in tested products even if the product is subjected to unit, integration, and system tests. The testing team generally tends to go in a direction that covers more positive testing. However, the end user of the product may not go in that same direction every time. For example, when an application allows uploads of files up to the size of 10 MB, the tester might try uploading 1 MB files first and then try to successively increase the size of files by 1 MB. A backward testing idea here would mean the tester will be starting with 10 MB from the beginning, then try 11 MB, and later check lower file sizes. 


Researching requires the tester to collect a lot of relevant information before starting the test. Information gathered from people who have experience with similar assignments could prove to be of great benefit for the tester. An instance is, when a tester gathers data from people on cross-browser testing for a similar product, he will have an idea about the issues that users might encounter in a particular browser even before testing officially begins. 

The article just lists a few ideas that could help testers come up with more creative ideas for testing on the go. The key is to be completely focused while testing, and take time-outs when you feel like you are running out of ideas.