junit2html | Turn Junit XML reports into self contained HTML reports | Dashboard library

by inorton Python Version: 31.0.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | junit2html Summary

junit2html is a Python library typically used in Analytics, Dashboard, Jenkin applications. junit2html has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install junit2html' or download it from GitLab, GitHub, PyPI.

Junit is a widely used java test framework, it happens to produce a fairly generic formatted test report and many non-java things produce the same files (eg py.test) or can be converted quite easily to junit xml (cunit reports via xslt). The report files are understood by many things like Jenkins and various IDEs. The format of junit files is described here:

Support

Quality

Security

License

Reuse

Support

junit2html has a low active ecosystem.

It has 90 star(s) with 42 fork(s). There are 2 watchers for this library.

There were 2 major release(s) in the last 6 months.

There are 0 open issues and 21 have been closed. On average issues are closed in 26 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of junit2html is 31.0.1

Quality

junit2html has 0 bugs and 0 code smells.

Security

junit2html has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

junit2html code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

junit2html is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

junit2html releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 4577 lines of code, 97 functions and 40 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed junit2html and discovered the below as its top functions. This is intended to give you an instant insight into junit2html implemented functionality, and help decide if they suit your requirements.

Start the application
Parse input files
Returns a list of all failed tests
List of skipped suites
Add a report to the report
Adds a case result
True if this job has failed
Return the outcome of the test
Generate a JUnit element
Unicode string
Make an etree element from a string
Generate a summary of the matrix tests
Return the short outcome of the given outcome
Combine results
Returns a list of all test tests
Returns all tests skipped
Process the results XML
Clean an attribute from an XML element
Add a report to the report matrix
Return HTML report as a string
Generate a test suite element
Return a list of all testcases
Returns all tests that have failed
The prefix of the test
Return the result list for a given class

Get all kandi verified functions for this library.

junit2html Key Features

No Key Features are available at this moment for junit2html.

junit2html Examples and Code Snippets

No Code Snippets are available at this moment for junit2html.

Community Discussions

Trending Discussions on junit2html

GitLab CI: How to continue job even when script fails

QUESTION

GitLab CI: How to continue job even when script fails

Asked 2019-Dec-05 at 17:51

I have a job in my pipeline that has a script with two very important steps:

mvn test to run JUnit tests against my code
junit2html to convert the XML result of the tests to a HTML format (only possible way to see the results as my pipelines aren't done through MRs) that is uploaded to GitLab as an artifact
docker rm to destroy a container created earlier in the pipeline

My problem is that when my tests fail, the script stops immediately at mvn test, so the junit2html step is never reached, meaning the test results are never uploaded in the event of failure, and docker rm is never executed either, so the container remains and messes up subsequent pipelines as a result.

What I want is to be able to keep a job going till the end even if the script fails at some point. Basically, the job should still count as failed in GitLab CI / CD, but its entire script should be executed. How can I configure this?

...

ANSWER

Answered 2019-Dec-05 at 17:51

In each step that you need to continue even if the step fails, you can add a flag to your .gitlab-ci.yml file in that step. For example:

Source https://stackoverflow.com/questions/59180675

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install junit2html

You can install using 'pip install junit2html' or download it from GitLab, GitHub, PyPI.
You can use junit2html like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

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: