Think outside the box is the name of 1 of Sun Sun's previous 7 core values. So, do you ask the question "think outside the box" what is the real application in testing? Or how to concretize that idea.
When we enter software testing, the first thing we are taught or learned is two boxes – a white box and a black box. After being taught, all we always do is check the Black box or the White box. This limits our thinking from thinking beyond the box.
They don't teach you how to think outside the box like a tester. What do you think outside the box mean in practice? As a software tester, if you are given two options, you will choose those two options. If you are provided with only one tool and people tell you to use it only, you will only use it. BUT, if you start looking for other tools, for other test methods, you'll start thinking outside the box. Outside the box does not mean wrong, or strange, it means creativity, spontaneity and vision. If we want different results, we have to do different things, right?
Creativity is an area and a skill that can help you to have outstanding results and develop a strong and self-conscious career in this field. Finally, what distinguishes you from others?
How to think outside the box as a tester?
To get more specific answers they will discuss here a few techniques while performing Software Testing:
1. Rapid Fire Technique
Rapid Fire techniques talk about how to create faster test cases. It is a human approach to test direct links to human performance.
The first things that come to mind when we talk about creating test cases are the Requested Documents, Excel Spreadsheets and some guidelines provided by the organization. For the first time, skip all of this and think about an idea, about what you think you're going to test.
Pick up Pen & Paper and write as many scripts as you can write within 60 seconds. Repeat the process until you cannot think of many scenarios or ideas and finally consider them.
You will be surprised to see the number of test ideas / test cases you have had without reviewing the documentation required.
The idea of checking backwards or forwards
What is the normal workflow you follow during testing? Are these the exact steps used during application development?
“Requirements >> Unit Cases >> Integration Testing >> System Testing”
The thinking of those who work in developing an application will surely think in the direction that will include most positive tests. However, end users may not think in the same direction. That's why Product Defects or UAT Defects exist even after the unit, integration, and system tests.
Example: It is required to indicate that you can upload a file that does not exceed the 10 MB file size. Most testers will monitor the upload of 1 MB, 2 MB, 3 MB and so on to 10 MB or error message is displayed. Why not start with 10 MB and then try 11 MB and then 9 MB?
This example is nothing but a BVA (Marginal Value Analysis). However, how many of us have tried using BVA in situations other than input boxes.
Make a question
Ideally, every QA engineer should know the purpose of a request. Asking questions will help QA Engineers fulfill their testing purpose. If a good QA Engineer asks questions, he / she will be good at testing. You need to make sure no questions (so silly as small) are ignored.
And, in turn, asking questions will also enhance the domain knowledge of test takers.
Remember: The only silly question is the contentless question.
Research is very beneficial before starting the test. Just be aware of the problems that others encounter while performing a similar task. Suppose, you are required to start cross-browser testing. Before starting the test, researching the problems other people encounter when using the same browser will help you find the error before starting the actual test.
Take advantage of your experience
Occasionally, you will work on applications similar to what you have done in the past. At that time, remember what you did. And you should be able to identify similar problems in a faster way and solve them faster.
All you have to do is check to see if the application you are testing now works the same as the one you used to test before. Also, by knowing how to handle problems, it is easier to come up with more ideas.
Testing can sometimes be a monotonous process and ideas can start to saturate. You may begin to feel that no solution works or you may even run out of ideas. In such cases, effective Pause can do a lot of miracles and can help you to have new creative thinking at the bottleneck that drains your ideas.
Pause can be a cup of Coffee or simply look out the window or anything you want to refresh yourself. Most creative flows come in moments when we relax and we allow our minds to be open to new ideas.
In addition to being creative, factors such as time, the speed at which ideas are implemented and their execution are also of high importance. You can get a great idea but if it's too late to implement it.