Automation Test Scripts (MAVEN,CUCUMBER)

Reduced time for testing, increased quality concerns combined with an increase in the number of devices and configurations highlights the importance of Software Testing playing a vital role in the DevOps process. An automated continuous testing solution is a key driver in DevOps triggered early within the development process.

TestPoint has invested into developing test accelerators, solutions and dashboards for our customers which help measure the quality based on the latest release and configuration.

TestPoint’s Vansah automation framework provides an integrated and open source web service which can be invoked from any automated testing tool and framework.

This provides real time metrics on test coverage, performance trending and transaction response time for each requirement being tested directly from your automated test scripts managed and reported from Vansah. Your regression test  coverage is visible to the team allowing Manual Testers to focus on tests which haven’t been executed or specific configurations (i.e browser, environment, device…)

How is it Organized?

  • Your Automation test scripts are organized with in a maven test package and the development scripts are organized with in main package.
  • The Automation test scripts resides in same repository as of the development repository
  • Whenever the developer commits the changes, Jenkins poll for changes and it will start the build process. It is responsibility of the developers or DevOps to specify the post build action where the particular build has to be deployed.
  • As part of the build process the automation suite will also be triggered to validate test cases and to verify the stability of the builds during which environment variables needs to injected on run time for testing the appropriate build and on the appropriate environment
  • With MAVEN you can use JUNITCUCUMBER or TestNG or the frameworks of your choice.
  • During the build process the automation test scripts will pulled from the git repository and deployed on the slave machine and the test scripts will be triggered.
  • During test execution the Vansah Java interface is invoked to update the test status of a particular test case, requirement in Vansah
  • Test Results are stored correctly against your configuration (Release, Build, Test Package, Test Case, Requirement)
  • New cases, requirements and release notes are automatically created in Vansah as part of continuous integration.

How to use the new Vansah Webservice Interface from Java?

  • To use Vansah Interface with in you test script, we need to initialize the “VansahInterface” Instance.
  • Once you have the instance you can call UpdateResultsInVansah() by supplying required parameters

vi= new VansahInterface();

vi.UpdateResultsInVansah (URI, PACKAGE, RELEASE, BUILD, ENVIRONMENT, AGENT, CASE, REQUIREMENT, RESULT, TEST_LOG_COMMENT);

example:

vi.UpdateResultsInVansah (“URI”, 50, “RELEASE”, “BUILD”, Chrome-44, Selenium-PC-1, 258, 750, FAIL, “Filter failed to return customer number”);

In real time while your scripts are running you will be notified in Vansah and users can see the results of a particular test package. You can also continue execution of other test cases using the manual tester option available in Vansah.

see example from Vansah: (Test Case 258 linked to Requirement/Story 750 has failed based on the call shown above.)

Vansah-TestPackage