| Table of Contents |
|---|
...
First step is to configure the machine where the test cases will be executed. It can be the same machine where the deployment workflow ran or can be a totally different machine.
There could always be scenario where we are deploying the artifact to one server however the testing software/instance is present in another machine.
As a prerequisite, we must install the software(newman) for the testing. As from below mentioned details we can find we need to install nodejs and newman on the target system where we want to execute the test cases. In case nodejs and newman are not in PATH variable by default that path should be added as part of Test Instance property.
...
Installation command
sudo yum install –y nodejs
sudo npm install -g newman
We can verify if the software got installed properly and respective locations. We did the installation of software's on a new machine teplt02.
...
FlexDeploy test instance configuration
...
We add the configured server(teplt02) as endpoint.
...
We are done with setup activity.
...
Lets first evaluate what needs to be configure to enable the testing based on newman test cases. First navigate to TEST AUTOMATION tab under Project and click on GET STARTED.
...
It will open a blank page with no UI but few suggestions. Apparently, it may look like this is a complex approach since manual intervention is required. However, on the contrary its super easy to use.
As we can see as soon as type something it would suggest potential property/parameter details. We first add a testName.
...
In our case as soon as we select Postman-runCollection , all relevant properties will appear automatically as shown below.
...
All property details with purpose and explanation can be check from plugin operation guide in confluence.
...
https://flexagon.atlassian.net/wiki/spaces/FD60/pages/9856626313/ExecuteCollection
For now we just keep the FDPMN_POSTMAN_COLLECTION_FILE and FDPMN_POSTMAN_ENVIRONMENT_FILE property with relevant details. Instead of providing exact path we can add Collection_file details in wild card format as well.
...
Now on execution, we can check the logs to find the collection file is found successfully.
...
From SUMMARY tab we can find two test cases successfully executed.
...
We can find detailed result under TEST RESULTS tab.
...
Reference Links
Test Automation - Must read for more detailed options/explanations.
...