AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
17e0618ff6
gtk2/.gitlab-ci/meson-html-report.py

372 lines
11 KiB
Python
Raw Normal View History

ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
#!/usr/bin/env python3
Add licensing and copyright notice to report generators So that other projects can use them.
2019-04-16 10:43:23 +00:00
# Turns a Mason testlog.json file into an HTML report
#
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
# Copyright 2019 GNOME Foundation
Add licensing and copyright notice to report generators So that other projects can use them.
2019-04-16 10:43:23 +00:00
#
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# Original author: Emmanuele Bassi
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
import argparse
import datetime
import json
import os
import sys
from jinja2 import Template
REPORT_TEMPLATE = '''
<!DOCTYPE html>
<html lang="en">
<head>
<title>{{ report.project_name }} Test Report</title>
<meta charset="utf-8" />
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
<style type="text/css">
body {
background: white;
color: #333;
font-family: 'Cantarell', sans-serif;
}
h1 {
color: #333333;
font-size: 1.9em;
font-weight: normal;
margin-bottom: 1em;
border-bottom: 1px solid #333333;
}
header {
position: fixed;
padding-bottom: 12px;
margin-bottom: 24px;
background: rgba(255, 255, 255, 0.85);
box-shadow: 0 0 1px rgba(0, 0, 0, 0.15);
z-index: 500;
left: 0;
top: 0;
width: 100%;
color: rgba(0, 0, 0, 0.3);
transform: translateY(0px);
transition: .2s background-color, color;
box-sizing: border-box;
display: block;
visibility: visible;
text-align: center;
}
article {
ci: Tweak the HTML report style The header needs to take into account the job id field.
2019-04-14 19:37:21 +00:00
padding-top: 200px;
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
margin: 2em;
}
div.report-meta {
width: auto;
border: 1px solid #ccc;
padding: .5em 2em;
color: #3c3c3c;
}
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
span.result {
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
font-weight: bold;
}
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
span.pass {
color: rgb(51, 209, 122);
}
span.skip {
color: rgb(255, 163, 72);
}
span.fail {
color: rgb(224, 27, 36);
}
span.xfail {
color: rgb(163, 71, 186);
}
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
div.result {
border-top: 1px solid #c0c0c0;
padding-top: 1em;
padding-bottom: 1em;
width: 100%;
}
div.result h4 {
border-bottom: 1px solid #c0c0c0;
margin-bottom: 0.7em;
}
pre {
color: #fafafa;
background-color: black;
border-radius: 6px;
box-shadow: 0px 5px 8px 0px rgba(0, 0, 0, 0.25);
font-family: monospace;
line-height: 1.2em;
border: none;
padding: 10px 1em;
font-size: 0.9em;
overflow: auto;
white-space: pre;
word-break: normal;
word-wrap: normal;
}
ul.passed li {
display: inline;
}
ul.passed li:after {
content: ",";
}
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
ul.passed li:last-child:after {
content: "";
}
ul.images {
padding-bottom: 1em;
}
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
ul.images li {
display: inline;
}
</style>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</head>
<body>
<header>
ci: Add the backend to the reports We want the test names in the junit xml to be unique across all the tests in a job, so we need to include the backend in the test name. And we also want to see the used backend in the html report.
2020-05-15 23:49:18 +00:00
<h1>{{ report.project_name }}/{{ report.backend }}/{{ report.branch_name }} :: Test Reports</h1>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</header>
<article>
ci: Move HTML report meta from header to article Makes the bar smaller.
2020-02-13 13:52:57 +00:00
<section>
<div class="report-meta">
ci: Add the backend to the reports We want the test names in the junit xml to be unique across all the tests in a job, so we need to include the backend in the test name. And we also want to see the used backend in the html report.
2020-05-15 23:49:18 +00:00
<p><strong>Backend:</strong> {{ report.backend }}</p>
ci: Move HTML report meta from header to article Makes the bar smaller.
2020-02-13 13:52:57 +00:00
<p><strong>Branch:</strong> {{ report.branch_name }}</p>
<p><strong>Date:</strong> <time datetime="{{ report.date.isoformat() }}">{{ report.locale_date }}</time></p>
{% if report.job_id %}<p><strong>Job ID:</strong> {{ report.job_id }}</p>{% endif %}
</div>
</section>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
<section>
<div class="summary">
ci: Add internal links to the HTML report Makes it easier to link to various sections, and to specific failures.
2019-11-01 15:44:12 +00:00
<h3><a name="summary">Summary</a></h3>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
<ul>
<li><strong>Total units:</strong> {{ report.total_units }}</li>
ci: Use per-suite anchors Anchors are global, so they need to be namespaced.
2020-02-13 14:45:08 +00:00
<li><strong>Failed:</strong> {{ report.total_failures }}</li>
<li><strong>Passed:</strong> {{ report.total_successes }}</li>
ci: Generate valid HTML for the report Fix a typo in the closing <ul>, and add a missing closing <div>.
2019-04-13 13:28:53 +00:00
</ul>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</div>
</section>
{% for suite_result in report.results_list %}
<section>
<div class="result">
ci: Add internal links to the HTML report Makes it easier to link to various sections, and to specific failures.
2019-11-01 15:44:12 +00:00
<h3><a name="results">Suite: {{ suite_result.suite_name }}</a></h3>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
<ul>
<li><strong>Units:</strong> {{ suite_result.n_units }}</li>
ci: Use per-suite anchors Anchors are global, so they need to be namespaced.
2020-02-13 14:45:08 +00:00
<li><strong>Failed:</strong> <a href="#{{ suite_result.suite_name }}-failed">{{ suite_result.n_failures }}</a></li>
<li><strong>Passed:</strong> <a href="#{{ suite_result.suite_name }}-passed">{{ suite_result.n_successes }}</a></li>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</ul>
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
<div class="failures">
ci: Use per-suite anchors Anchors are global, so they need to be namespaced.
2020-02-13 14:45:08 +00:00
<h4><a name="{{ suite_result.suite_name }}-failed">Failures</a></h4>
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
<ul class="failed">
ci: Count 'ERROR' codes as failures Otherwise they'll be dropped from our reports.
2020-04-12 13:28:59 +00:00
{% for failure in suite_result.failures if failure.result in [ 'ERROR', 'FAIL', 'UNEXPECTEDPASS' ] %}
ci: Add internal links to the HTML report Makes it easier to link to various sections, and to specific failures.
2019-11-01 15:44:12 +00:00
<li><a name="{{ failure.name }}">{{ failure.name }}</a> - result: <span class="result fail">{{ failure.result }}</span><br/>
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
{% if failure.stdout %}
Output: <pre>{{ failure.stdout }}</pre>
{% endif %}
{% if failure.image_data is defined %}
<ul class="images">
<li><img alt="ref" src="{{ failure.image_data.ref }}" /></li>
<li><img alt="out" src="{{ failure.image_data.out }}" /></li>
<li><img alt="diff" src="{{ failure.image_data.diff }}" /></li>
</ul>
{% endif %}
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</li>
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
{% else %}
<li>None</li>
{% endfor %}
</ul>
ci: Use per-suite anchors Anchors are global, so they need to be namespaced.
2020-02-13 14:45:08 +00:00
<h4><a name="{{ suite_result.suite_name }}-timed-out">Timed out</a></h4>
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
<ul class="failed">
{% for failure in suite_result.failures if failure.result == 'TIMEOUT' %}
ci: Add internal links to the HTML report Makes it easier to link to various sections, and to specific failures.
2019-11-01 15:44:12 +00:00
<li><a name="{{ failure.name }}">{{ failure.name }}</a> - result: <span class="result fail">{{ failure.result }}</span><br/>
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
{% if failure.stdout %}
Output: <pre>{{ failure.stdout }}</pre>
{% endif %}
</li>
{% else %}
<li>None</li>
{% endfor %}
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</ul>
</div>
ci: Restructure the HTML report We should show all the possible result sections: - passed - skipped - expected failures - failures - timed out Even if we consider the first three to be successes.
2019-04-14 19:56:11 +00:00
ci: Rearrange the results in the HTML report Move the failures up top, so they stand out.
2020-02-13 14:26:40 +00:00
<div class="successes">
ci: Use per-suite anchors Anchors are global, so they need to be namespaced.
2020-02-13 14:45:08 +00:00
<h4><a name="{{ suite_result.suite_name }}-expected-fail">Expected failures</a></h4>
ci: Rearrange the results in the HTML report Move the failures up top, so they stand out.
2020-02-13 14:26:40 +00:00
<ul>
{% for success in suite_result.successes if success.result == 'EXPECTEDFAIL' %}
<li><a name="{{ success.name }}">{{ success.name }}</a> - result: <span class="result xfail">{{ success.result }}</span><br/>
{% if success.stdout %}
Output: <pre>{{ success.stdout }}</pre>
{% endif %}
{% if success.image_data is defined %}
<ul class="images">
<li><img alt="ref" src="{{ success.image_data.ref }}" /></li>
<li><img alt="out" src="{{ success.image_data.out }}" /></li>
<li><img alt="diff" src="{{ success.image_data.diff }}" /></li>
</ul>
{% endif %}
</li>
{% else %}
<li>None</li>
{% endfor %}
</ul>
ci: Count 'ERROR' codes as failures Otherwise they'll be dropped from our reports.
2020-04-12 13:28:59 +00:00
<h4><a name="{{ suite_result.suite_name }}-skipped">Skipped</a></h4>
<ul>
{% for success in suite_result.successes if success.result == 'SKIP' %}
<li>{{ success.name }} - result: <span class="result skip">{{ success.result }}</li>
{% else %}
<li>None</li>
{% endfor %}
</ul>
<h4><a name="{{ suite_result.suite_name }}-passed">Passed</a></h4>
<ul class="passed">
{% for success in suite_result.successes if success.result == 'OK' %}
<li>{{ success.name }} - result: <span class="result pass">{{ success.result }}</li>
{% else %}
<li>None</li>
{% endfor %}
</ul>
ci: Rearrange the results in the HTML report Move the failures up top, so they stand out.
2020-02-13 14:26:40 +00:00
</div>
ci: Generate valid HTML for the report Fix a typo in the closing <ul>, and add a missing closing <div>.
2019-04-13 13:28:53 +00:00
</div>
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
</section>
{% endfor %}
</article>
</body>
</html>
'''
aparser = argparse.ArgumentParser(description='Turns a Meson test log into an HTML report')
aparser.add_argument('--project-name', metavar='NAME',
help='The project name',
default='Unknown')
ci: Add the backend to the reports We want the test names in the junit xml to be unique across all the tests in a job, so we need to include the backend in the test name. And we also want to see the used backend in the html report.
2020-05-15 23:49:18 +00:00
aparser.add_argument('--backend', metavar='NAME',
help='The used backend',
default='unknown')
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
aparser.add_argument('--job-id', metavar='ID',
help='The job ID for the report',
default=None)
aparser.add_argument('--branch', metavar='NAME',
help='Branch of the project being tested',
Update references to master in the repository
2021-11-29 22:37:49 +00:00
default='main')
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
aparser.add_argument('--output', metavar='FILE',
help='The output HTML file, stdout by default',
type=argparse.FileType('w', encoding='UTF-8'),
default=sys.stdout)
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
aparser.add_argument('--reftest-suite', metavar='NAME',
help='The name of the reftests suite',
default='reftest')
aparser.add_argument('--reftest-output-dir', metavar='DIR',
help='The output directory for reftests data',
default=None)
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
aparser.add_argument('infile', metavar='FILE',
help='The input testlog.json, stdin by default',
type=argparse.FileType('r', encoding='UTF-8'),
default=sys.stdin)
args = aparser.parse_args()
outfile = args.output
suites = {}
for line in args.infile:
data = json.loads(line)
(full_suite, unit_name) = data['name'].split(' / ')
(project_name, suite_name) = full_suite.split(':')
unit = {
'project-name': project_name,
'suite': suite_name,
'name': unit_name,
'duration': data['duration'],
'returncode': data['returncode'],
'result': data['result'],
'stdout': data['stdout'],
}
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
if args.reftest_output_dir is not None and suite_name == args.reftest_suite:
filename = unit_name.split(' ')[1]
basename = os.path.splitext(filename)[0]
image_data = {
'ref': os.path.join(args.reftest_output_dir, '{}.ref.png'.format(basename)),
'out': os.path.join(args.reftest_output_dir, '{}.out.png'.format(basename)),
'diff': os.path.join(args.reftest_output_dir, '{}.diff.png'.format(basename)),
}
unit['image_data'] = image_data
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
units = suites.setdefault(full_suite, [])
units.append(unit)
report = {}
report['date'] = datetime.datetime.utcnow()
report['locale_date'] = report['date'].strftime("%c")
report['project_name'] = args.project_name
ci: Add the backend to the reports We want the test names in the junit xml to be unique across all the tests in a job, so we need to include the backend in the test name. And we also want to see the used backend in the html report.
2020-05-15 23:49:18 +00:00
report['backend'] = args.backend
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
report['job_id'] = args.job_id
report['branch_name'] = args.branch
report['total_successes'] = 0
report['total_failures'] = 0
report['total_units'] = 0
report['results_list'] = []
for name, units in suites.items():
(project_name, suite_name) = name.split(':')
print('Processing {} suite {}:'.format(project_name, suite_name))
def if_failed(unit):
ci: Count 'ERROR' codes as failures Otherwise they'll be dropped from our reports.
2020-04-12 13:28:59 +00:00
if unit['result'] in ['FAIL', 'UNEXPECTEDPASS', 'TIMEOUT', 'ERROR',]:
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
return True
return False
def if_succeded(unit):
if unit['result'] in ['OK', 'EXPECTEDFAIL', 'SKIP']:
return True
return False
successes = list(filter(if_succeded, units))
failures = list(filter(if_failed, units))
n_units = len(units)
n_successes = len(successes)
n_failures = len(failures)
report['total_units'] += n_units
report['total_successes'] += n_successes
report['total_failures'] += n_failures
print(' - {}: {} total, {} pass, {} fail'.format(suite_name, n_units, n_successes, n_failures))
suite_report = {
'suite_name': suite_name,
'n_units': n_units,
'successes': successes,
'n_successes': n_successes,
'failures': failures,
'n_failures': n_failures,
}
report['results_list'].append(suite_report)
template = Template(REPORT_TEMPLATE)
outfile.write(template.render({'report': report}))
Reference in New Issue Copy Permalink