Most of the time people have the issue with installing software and dependencies. For example, we want to
Schedule the collection of the postman that we have created earlier using ‘POSTMAN’ tool, Rather than installing ‘newman’ command line tool, We will use a Docker image of Linux box with already installed ‘newman’.
I have been asked why I am getting the error, ‘newman’ not working etc, my os/system is having an issue while installing or running. This post definitely help you guys.
Docker allows you to package an application with all of its dependencies into a standardized unit for software development.
In simple sentence consider it as a virtual machine which has ubuntu running with ‘newman‘ installed already.
The software utility Cron is a time-based job scheduler in Unix-like computer operating systems. People who set up and maintain software environments use cron to schedule jobs (commands or shell scripts) to run periodically at fixed times, dates, or intervals.
Below are the few points/Pre-made Test cases for the Cron Job Testing:-
Verify if It is scheduled correctly – By going here http://corntab.com/.
Mock the Cron time by 1-2 minutes by changing it for quick testing (if it’s long for hour/day long). – High
Ask the devs to create a shortcut for it. In the server or any other way to directly run it by you so that you can test it when you need.(saves time)
Ask dev to add the logs for monitor purpose and monitor it while testing.
Use below command for logs.
* * * * * /path/script.sh &> /path/script.log or
tail -f /var/log/cron
Do testing by doing changing things like we do in CRUD(Not always, Crud means update/delete etc whichever is relevant) and verify results. – High
Break something the job relies on upon and schedule it to run again in a few minutes – Verify the results.
After deployment – Validate it with real data also. – High
Keep system time and user system time in mind while testing CRON’s as scheduling is by server GMT time usually.
Negative scenario: What if CRON is stopped the midway execution, any impacts it will have?
Negative – Discuss with dev if there is any possibility of the same Cron getting run multiple times.
Negative – Discuss with dev if its fails to the job – What is the risk/ solution for it(did we get the mail if it fails ?)
Test for scenarios which shouldn’t get affected by Cron job(e.g. a other Cron should not affect other cron)
Today I am going to discuss Testing Techniques- Pairwise Testing. “Generate less number of combination with more test coverage.
What is Pairwise Technique?
A black-box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters
Pairwise testing technique can dramatically reduce the number of combinations to be covered but remains very effective in terms of fault detection
Now let’s learn how to apply Pairwise Testing by this example.
Let’s take an example –
Suppose, we have a web app with one page that we have to do the Cross browser testing (CBT) e.g for IE, Chrome, Firefox, Opera, Safari and Cross OS testing with Windows, Mac, Ubuntu. We have another parameter like HTTP 1, HTTP 2 and resolution HD, NonHD(low resolution).
So Normal combination – 5*3*2*2 = 60
To perform 60 Test cases we will need about 180 minutes(assuming 3 minutes per Test Case).
Let’s take this example in the Pairwise Testing.
We will use the Pairwiser-tool for combination to generate.
Need for Pairwiser tool
Web-based easy to use.
Generate the combination and export to excel.
Generate the Test case and export to JIRA directly.
You can apply the constraint to the input parameter.