What's New in This Guide

This section shares the list of new features introduced in every ATS release. For more release specific information, please refer to its release notes.

ATS Release 1.1.0

Following new features are introduced in ATS 1.1.0:

Table - Features

Feature NRF PCF SCP
One-click start of <NF> New-feature and Regression pipelines for 'All' option after successfully logging into the Jenkins GUI. Yes

Example:

  • New-Features One-Click - To run "All" testcases in NRF-NewFeatures pipeline, use http://<Jenkins_IP>:<Jenkins_Port>/view/NRF/job/NRF-NewFeatures/build link to open Jenkins and click "Build".
  • Regression One-Click - To run "All" testcases in NRF-Regression pipeline, use http://<Jenkins_IP>:<Jenkins_Port>/view/NRF/job/NRF-Regression/build link to open Jenkins and click "Build".
Yes

Example:

  • New-Features One-Click - To run "All" testcases in PCF-NewFeatures pipeline, use http://<Jenkins_IP>:<Jenkins_Port>/view/PCF/job/PCF-NewFeatures/build link to open Jenkins and click "Build".
  • Regression One-Click - To run "All" testcases in PCF-Regression pipeline, use http://<Jenkins_IP>:<Jenkins_Port>/view/PCF/job/PCF-Regression/build link to open Jenkins and click "Build".
Yes

Example:New-Features One-Click - To run "All" testcases in SCP-NewFeatures pipeline, use http://<Jenkins_IP>:<Jenkins_Port>/view/SCP/job/SCP-NewFeatures/build link to open Jenkins and click "Build".

Allows to deploy ATS using either Helm2 or Helm3 helm versions Yes Allows to deploy ATS using Helm 2 only. Yes
Does not requires manual intervention to add environmental variable, like ATS-1.0.0 Yes Yes Yes
One-time configuration on Jenkins GUI to execute the test cases. Yes Yes Yes
No need to login to ATS pod through CLI. Users can perform all operations through Jenkins GUI. Yes Yes Yes
Allows to execute Sanity cases to validate the NF and ATS deployment. Yes No No
Provides an option to execute either All, Sanity and Single/Multiple feature files in the New-Features pipeline. Yes Yes but it does not have Sanity option Yes but it does not have Sanity option
Does not display Skipped cases in the console output when executing the cases using Single/Multiple feature files option. Yes No No
The Documentation section shows all the testcases according to the service operation supported by NF. Yes Yes Yes
Automatically executes the failed test cases. Default re-run count is 2. The overall pipeline status shows the result of re-run so, it is recommended to provide the value of re-run count variable. Yes Yes. Default re-run count is 1. Yes
New TestCases added to Jenkins Pipeline Provides a total of 251 scenarios clubbed together in 100 feature files of NRF ATS - 1.6.1 New Feature pipeline. Provides 19 Feature files in PCF-NewFeatures pipeline. Provides a total of 65 scenarios clubbed together in 9 feature files of SCP ATS - 1.6.0 New Feature pipeline.
Previous Release TestCases Provides a total of 163 scenarios clubbed together in 80 feature files of NRF ATS - 1.6.1 Regression pipeline. Provides 10 Feature files in PCF-Regression pipeline. Not applicable
Backward Compatibility ATS is NOT backward compatible. It means NRF ATS - 1.6.1 will work only with NRF 1.6.1. For NRF 1.5.0, user still need to use ATS - 1.0.0 version. ATS is NOT backward compatible. It means PCF ATS - 1.1.0 will work only with PCF 1.6.1. For PCF 1.5.0, user still need to use ATS - 1.0.0 version. Not applicable
Supports NF with TLS Enabled (server side) and Disabled mode Not applicable Yes. PCF ATS supports PCF with TLS Enabled (server side) and Disabled mode Not applicable
Test cases delivered in ATS Release 1.0.0 are added to its respective Regression Pipeline. User can run any pipeline but not parallel. Yes Yes Not applicable

Following table shares information about pipeline statuses:

Table - Pipeline Statuses

Condition Result Stage Status Pipeline Status
If all the test cases pass without rerun Re-run function executes. It does not initiate any test case as none of the test case has failed. Green All other successful stages appears as Green and Build Status appears as Blue.
If some test cases fail in actual execution and all of them pass in re-run stage The Execution stage appears as YELLOW. Yellow. It indicates that the stage was not successful in first attempt. All other successful stages appears as Green and Build Status appears as Blue.
If some test cases fail in actual execution and some of them pass in re-run, and some test cases still have failed in re-run even after exhausting the re-run count The Execution stage appears as YELLOW Yellow. It indicates that the stage was not successful in first attempt. All other successful stages appears as Green and Build Status appears as Red.