Technology

# How to Execute Test batches and Generate the Test Reports?

Automation testing has gained popularity since 2016. Most of the small testing endeavors are fulfilled by it. Automation testing is preferred as it saves time that goes into manual testing of components. It is considered great for repeated testing endeavors.

Here in this blog today, we shall see how to execute test batches and then generate their reports

## Automated Test Runs

Squish gives direction line apparatuses that make it conceivable to robotize the running of tests. The apparatus for executing tests is squished under, yet for it to work appropriately a squishserver should likewise be running—the squish underutilizes the squishserver to begin AUTs and speak with them.

Computerized cluster tests can be made on any of the stages that Squish bolsters, including Windows and Unix-like stages.

For instance, here is a straightforward Unix shell content to execute the total test suite ~/suite_myapp and spare the outcomes to ~/squish-results-‘date’:

#!/bin/bash

export SQUISH_PREFIX=/path/to/squish

export PATH=$SQUISH_PREFIX/bin:$PATH

# Don't start squishserver in the background with verbose logging (we're using --local)

# squishserver --verbose &

# Dated directory to store report results:

LOGDIRECTORY=~/squish-results-date -I

# Execute the test suite with a local squishserver:

squish under --test suite ~/suite_myapp --local --reportgen xml3.2,\$LOGDIRECTORY

# If we started squishserver earlier, stop it now.

# squishserver --stop

Since we are utilizing – neighborhood, it isn’t important to begin a different squishserver process out of sight from our written code script.

We are utilizing – reportgen to determine the sort of yield to create. For a rundown of all report-generator designs, see squishrunner – reportgen: Generating Reports (Section 7.4.3.6).

Here is a comparative model, composed for Windows utilizing the standard cmd.exe shell. Since the Windows variable, %DATE% here and there utilizes a period and different occasions a scramble or some other character to isolate the numbers, it can’t be utilized in certain regions to shape a registry name.

REM add Squish to PATH

set SQUISH_PREFIX=C:\path\to\squish

set PATH=%SQUISH_PREFIX%\bin;%PATH%

REM Don't start squishserver in the background (we're using --local):

REM start /B squishserver --verbose

REM The Log Directory does not (but perhaps should) have today's date in it:

set LOGDIRECTORY=%USERPROFILE%\squish-results

REM Execute the test suite with a --local squishserver:

squish under --testsuite %USERPROFILE%\suite_myapp --local --reportgen "xml3.2,%LOGDIRECTORY%"

REM If we started the squishserver in the background, stop it:

REM squishserver --stop

One burden of utilizing shell contents and bunch records like this is for cross-stage testing we should keep up isolated contents for every stage. We can maintain a strategic distance from this issue by utilizing a cross-stage scripting language which would enable us to keep in touch with one content and run it on all stages we were keen on. Here is a case of such a content written in Python, which you can discover in SQUISHDIR/examples/regressiontesting/squishruntests-simple.py.

## What Is Test Data And Why is it Important?

Alluding to an examination directed by IBM in 2016, looking, overseeing, keeping up, and producing test information envelop 30%-60% of the analyzer’s time. It is certainly proof that information arrangement is a tedious period of programming testing.

By the by, it is a reality crosswise over numerous different orders that most information researchers burn through half 80% of their model’s advancement time in sorting out information. What’s more, presently thinking about the enactment and just as the Personally Identifiable Information (PII) makes the analyzer’s commitment overwhelmingly better than average during the time spent testing.

Today, the believability and unwavering quality of the test information are viewed as a positive component for the entrepreneurs. The item proprietors see the phantom duplicates of the test information as the greatest test, which decreases the unwavering quality of any application at this exceptional time of customers’ interest/prerequisites for quality affirmation.

The detailing designs are altogether different in each apparatus, yet I will attempt to list down the most significant viewpoints that ought to be available in the report.

## 1) Report for a batch of scripts:

If various experiments are remembered for a bunch and that clump is executed, at that point the significant focus to remember for the report are:

1. Total Number of contents.
2. List of all experiments in forbidden structure
3. Test Result (Passed or Failed before each experiment)
4. Duration (before each experiment)
5. Machine/Environment Name (before each experiment)

## 2) Detailed report for an individual test case:

Presently when we click on any experiment to see the point by point report, the detailed report of an individual experiment ought to contain the accompanying data.

1. Name of the experiment
2. The id of that experiment on the off chance that it is associated with experiment vault.
3. Duration of the experiment. (min: ss)
4. Status (Passed or Failed)
5. ScreenShots (just on disappointment or on each progression)
6. Where it comes up short. (The careful line number in the content where it was falling flat)
7. Any other supportive logs which we have written in the content to be shown on the report.

## Some other points to remember:

1. Duration is a significant factor. On the off chance that the experiments are taking the more extended term to finish, they should be deliberately fixed and improved for expedient execution. The faster the experiment finishes, the better it is.
2. The Screenshot ought to be taken on disappointment just to accelerate the execution.
3. The Report should be exportable in a shareable configuration, for example, a PDF or Excel File.
4. Custom Messages ought to be composed on attestations and checkpoints so that if there should be an occurrence of Failed Assertion, we precisely realize just by observing the report that what has turned out badly.
5. A great practice is to Log a line of content before each activity. This log will be shown in the report and a layman will realize that on which activity the experiment has fizzled.

## Conclusion

Here is all that we had to tell you. If you have any doubts, do let us know in the comments section of this post. We will be happy to help you.

Hi, I'm Raj Hirvate and I am a Tech Blogger from India. I like to post about technology and product reviews to the readers of my blog. Apart from blogging i'm a big Anime fan I Love Watching Naruto, One piece and Death Note.

Previous article

Next article

Technology

Technology

Technology

Technology