osvalda/pitaya

API test coverage reporter for TestNG and JUnit5

pitaya's Issues

PAC-010 Add summary data to landing page:

-new block of total/covered
-covered endpoint lists statistics (average test num, passed failed ratio, etc)
-least tested area
-fully tested areas

Add swagger input file support

Add Swagger open API docs support.

Parallel with current endpoint list file format an Open API support would widely extend the usability of the tool.

See parser for more info.

PAC-003 - Use github page structure in package naming

Increase Unit Test Coverage

Currently the unit test coverage is low and misses important classes such as the EndpointCoverageReporter.class

All public method shall be covered with positive and negative cases especially focusing on input data handling and computation.

Add Junit suport

Extend the tool with JUnit support.

JUnit 5

Enhance the HTML output

Currently the HTML output is contains the basic data of the api coverage status. Enhance its look and feel to a more modern and pleasing format.

• Change the global pie chart to a donuts with central legend
• Change the endpoint list tables color to white
• Set the content's alignment to the left
• Add Jenkins workaround for css issue (https://stackoverflow.com/questions/35783964/jenkins-html-publisher-plugin-no-css-is-displayed-when-report-is-viewed-in-j)
• Add SUT name property to page title