Random Testing Tips

I am writing this post based on my experience that span over around seven years and I feel that things that have helped me and my other fellow team members in doing testing effectively and swiftly are worth sharing. The list will continue to evolve over time, so stay tune. I would be glad to know your feedback and tips on typical day of testing. ☺

Tip 1: Removing Distraction.

During testing there are so many distractions you come across daily but this distraction is something different. When you are verifying or executing some scenarios you see some unexpected and unusual state or things within the application under test that is not part of your current expectation so as a tester you should NOT leave your current execution and start probing the new problem you see but rather you should note down  such unusual things and continue your current tasks. When you finished then definitely as a good tester you should report and trace each and every problem within the application.

  

Tip 2: Dealing Credentials Scarcity.

There are times when you're testing with applications that require multiple unique email addresses to register for different roles and views. To cater this need there is a very handy technique you can use to create multiple users/emails. For example, if you have an email address john.doe@gmail.com and you need to create 3 different roles/users scenarios in an application say Customer, Sales, Admin or Sysadmin so you can create all user using existing email like john.doe+customer@gamil.com, john.doe+sales@gamil.com and
john.doe+sysadmin@gamil.com and you can have personalize view of each respective users based on your application and needs. All related emails (if application under test generate some) will be delivered to only john.doe@gamil.com and you can SAVE crucial time wasted in creating different valid (email receivable) email addresses.

Tip 3: Winning Developer Trust.

Sometimes as a tester we write a very robust defect report and try to put ever related stuff and condition but developer actually interested in one direct clue and source of a problem. That very clue is very easy to find. Modern browser are coming  with robust built-in debugging tool like Developer Panel within the browser. As a tester what you can do is you can keep open (Windows = F12 or CTRL+SHIFT+I; Mac = CMD+OPT+I) that panel to see which request is failing, giving error or simply not even actually triggered by clicking the specific request url and then clicking response tab to see its details. That way you will be able to add that clue in defect report that developer can directly jump into fixing quickly and definitely you will be treated as reliable tester for her code.

Tip 4: Testing with large size file

Sometimes you might need large files to test the application and creating large files is always a challenge. But there are many solution and the one am sharing is very handy, and to that we can use the concatenation of single file. Use the following command on your Unix/Linux shell:

Prerequisite: You should have at least one file with some data in it either compressed or uncompressed.

cat   < existing-file > >>  < new-file >

Repeat the above line as many time as you want to generate size of the file you needed for testing. Alternatively you can create shell script to do this automatically an repeatedly for you as follows.

../bin/generate_large_file.sh

for i in {0..100}; do cat < existing-file > >>  < new-file > ; done 

Save the above script and execute as ./generate_large_file.sh it will loop 100 times and append the existing files into new file to create large size file with same repeating contents in the same directory where original file and shell file reside.