open-test-reporting | Language-agnostic test reporting format and tooling
kandi X-RAY | open-test-reporting Summary
kandi X-RAY | open-test-reporting Summary
open-test-reporting is a Java library. open-test-reporting has no bugs, it has no vulnerabilities and it has low support. However open-test-reporting build file is not available and it has a Non-SPDX License. You can download it from GitHub, Maven.
This repository contains the definition of and tooling for two new XML-based test reporting formats that are agnostic of any testing framework and programming language yet concrete enough to be consumable by a wide range of downstream tools such as IDEs, build tools, and report generators. The first format is event-based which is not only suitable for writing events to a file but also for streaming events over a local socket or network connection. Instead of having to collect all data for a test only to write it to the report after the test has completed, testing frameworks can emit events as they occur, for example when a test is started or finished. The second format is meant to be closer to existing hierarchical representations of test results that users are familiar with. For example, when executing tests in IDEs, one is usually presented with a tree of tests and their results. This same structure can be found in files that use this format. Thus, instead of requiring humans or processing tools to piece together all relevant events for a test from the event-based format, this hierarchical format collects all relevant information in a single place for each test. Besides being human-readable, this format is easier to transform into an HTML report by a downstream reporting tool or CI server. The two formats are designed to complement each other such that the event-based format can be mechanically converted into the hierarchical one. This repository contains a reference implementation of such a converter as an executable and library. This way, testing frameworks can focus on writing the event-based format; build tools may use the converter to write the hierarchical format; and reporting tools can consume whichever format they prefer.
This repository contains the definition of and tooling for two new XML-based test reporting formats that are agnostic of any testing framework and programming language yet concrete enough to be consumable by a wide range of downstream tools such as IDEs, build tools, and report generators. The first format is event-based which is not only suitable for writing events to a file but also for streaming events over a local socket or network connection. Instead of having to collect all data for a test only to write it to the report after the test has completed, testing frameworks can emit events as they occur, for example when a test is started or finished. The second format is meant to be closer to existing hierarchical representations of test results that users are familiar with. For example, when executing tests in IDEs, one is usually presented with a tree of tests and their results. This same structure can be found in files that use this format. Thus, instead of requiring humans or processing tools to piece together all relevant events for a test from the event-based format, this hierarchical format collects all relevant information in a single place for each test. Besides being human-readable, this format is easier to transform into an HTML report by a downstream reporting tool or CI server. The two formats are designed to complement each other such that the event-based format can be mechanically converted into the hierarchical one. This repository contains a reference implementation of such a converter as an executable and library. This way, testing frameworks can focus on writing the event-based format; build tools may use the converter to write the hierarchical format; and reporting tools can consume whichever format they prefer.
Support
Quality
Security
License
Reuse
Support
open-test-reporting has a low active ecosystem.
It has 39 star(s) with 3 fork(s). There are 9 watchers for this library.
It had no major release in the last 12 months.
There are 2 open issues and 1 have been closed. On average issues are closed in 37 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of open-test-reporting is r0.1.0-M1
Quality
open-test-reporting has no bugs reported.
Security
open-test-reporting has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
open-test-reporting has a Non-SPDX License.
Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.
Reuse
open-test-reporting releases are available to install and integrate.
Deployable package is available in Maven.
open-test-reporting has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions are not available. Examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of open-test-reporting
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of open-test-reporting
open-test-reporting Key Features
No Key Features are available at this moment for open-test-reporting.
open-test-reporting Examples and Code Snippets
No Code Snippets are available at this moment for open-test-reporting.
Community Discussions
No Community Discussions are available at this moment for open-test-reporting.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install open-test-reporting
You can download it from GitHub, Maven.
You can use open-test-reporting like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the open-test-reporting component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
You can use open-test-reporting like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the open-test-reporting component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page