Welcome!

XebiaLabs | Continuous Delivery and Agile DevOps Tools

XebiaLabs Blog

Subscribe to XebiaLabs Blog: eMailAlertsEmail Alerts
Get XebiaLabs Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Blog Feed Post

Clean up your mess with XL TestView!

Many organizations I’ve spoken to over the years have a similar problem. Their test scripts have grown out of control and they have a hard time managing and organizing them.  Many teams try to use tools like Jenkins to manage the execution of tests through their pipeline, which helps to a point but they still have the problem of reporting the results and organization.

A company I spoke to recently has a bunch of scripts on a network share that are organized in a windows file structure and kicked off by a batch script. They weren’t even sure what some of the scripts were doing, just that they were doing something because they produced some output.

To me this sounds insane and when it comes to the reporting, they have to comb through flat text files of result data and aren’t sure what some of it means. Does that sound safe? It’s like rolling the dice to decide what you are going to produce for your customers. They were hoping that XL TestView was a solution for getting their act together in regards to their testing methods.

While XL TestView would undoubtedly help them organize their tests into Projects and Test Specification Sets, they probably need to rethink they way they want to handle their testing practices from the top down. Tools such as XL TestView are only one step to helping organize your tests.

In XL TestView we organize test specifications in a couple of ways. First, we use projects. Projects are basically a folder to store your Test Specs and Test Spec Sets in. If you have 2 applications you are testing, then think you might use a project to represent each application. Inside the projects we would store your test specifications and test specification sets.

Pic1

 

We define test specifications as a coherent set of tests. These can be jobs or tasks that include that include automated tests. You can see the results of these tests in dashboards, reports, and qualifications.

There are four types of test specifications:

  • Active test specification: A test specification that can retrieve test results
  • Executable test specification: A test specification that can execute test runs and import the results
  • Passive test specification: A test specification to which an external process such as Jenkins can push results
  • Test specification set: A group that aggregates the results of multiple test specifications

Pic2

 

Test Specs report to XL TestView based on test qualifications. We define test qualifications as XL TestView’s determination of whether a particular test run has passed or failed, based on a configurable analysis of the test results. Qualifications are customizable which allow you seamlessly to fit XL TestView into any continuous delivery pipeline.

In closing, if you have a hard time organizing your test scripts and feel like your tests, while effective are hard to manage, disorganized and are a tedious process to make sense of, then take a look at XL TestView.

The post Clean up your mess with XL TestView! appeared first on XebiaLabs.

Read the original blog entry...

More Stories By XebiaLabs Blog

XebiaLabs is the technology leader for automation software for DevOps and Continuous Delivery. It focuses on helping companies accelerate the delivery of new software in the most efficient manner. Its products are simple to use, quick to implement, and provide robust enterprise technology.