All geek questions in one place

Create Concordion Summary Report

My project looks at using Concordion for automatic acceptance testing. The big drawback that I see in Concordion is the auto-generated summary page. In its current form, we would have to use a tester or functional user for each of the generated HTML pages to verify success or failure.

When looking at the Concordion svn repository, I see one proposed modification for generating a composite XML file, but this change was not included in the trunk line, as far as I can tell. I would prefer not to tear the source of the Concordion open and change it directly if I can.

Does anyone know of a quick and dirty way to create a page like Concordion Master / Summary Report?

+4
source share
2 answers

Definitely a late answer to your question, but this may help others who fall into this question.

We use the concordion: run = "concordion" function to create a meaningful summary page.

As you can see below, we have the source file Customer.html, which calls other concordion client flow scripts.

Customer.html

<html xmlns:concordion="http://www.concordion.org/2007/concordion"> <head> <title>Customer</title> </head> <body> <div class='testcontent'> <h1>Customer</h1> <h3>Customer flows:</h3> <ul> <li><a concordion:run="concordion" href="CreateNewCustomer.html">Create New Customer</a></li> <li><a concordion:run="concordion" href="ModifyCustomer.html">Modify Customer</a></li> <li><a concordion:run="concordion" href="DeleteCustomer.html">Delete Customer</a></li> </ul> </div> </body> </html>

Customer.java

 @RunWith(ConcordionRunner.class) public class SpecsTest{ }

The CreateNewCustomer.html, ModifyCustomer.html, and DeleteCustomer.html files will have the actual specification using the Provided, When, Then .

When we run CustomerTest.java, all three of these threads are executed, and the Customer.html summary page will display all three specifications, such as Red or Green, based on whether it was success or failure.

We have several levels of grouping Spec files like these, and we end up with a good summary page.

+7
source

Just start it yourself, but it seems the goal of the html pages is to document what is being tested. Tests are run as junit tests, and the results can be captured using any harness used.

The dashboard will be nice, but there is no need to determine if there are any glitches.

0
source

Source: https://habr.com/ru/post/1385366/

More articles:


All Articles