question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Report tests results

See original GitHub issue

Issue Type

  • Feature request

Molecule and Ansible details

  config file = None
  configured module search path = [u'/home/vagrant/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /home/vagrant/vEnv27/lib/python2.7/site-packages/ansible
  executable location = /home/vagrant/vEnv27/bin/ansible
  python version = 2.7.5 (default, Aug  2 2016, 04:20:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]
molecule, version 2.22rc3

Molecule installation method :

any

Ansible installation method (one of):

  • pip

Desired Behavior

I need to display a report of failed test and for each, the reason of failure. I didn’t see any option to do it in molecule. Even in proposed related issues/features.

In my environment, i will be use tox. I found pytest-molecule but it seems to focus only in infra test and not other molecule tests (as idempotence for example).

Will I have missed something ? If no, I think it might be a good improvement. The final goal is to have something like cucumber report in Jenkins but the first step will be to have the tests results generated somewhere.

Thanks

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
seandstcommented, Jul 15, 2019

In addition to pytest’s ability to write out junit xml when running the testinfra tests, ansible has the junit callback plugin that can export the results of a playbook run to JUnit xml: https://docs.ansible.com/ansible/latest/plugins/callback/junit.html

I do recommend working with Ansible 2.8 or higher, as the “test_case_prefix” param to the callback plugin is great for only including specific tasks in the output for test reporting.

0reactions
ssbarneacommented, Feb 1, 2020

I will close this because there are already few solutions (pytest and junit callback) and it is very unlikely that we will want to make a reporting tool out of molecule. That reminds me of the issues pytest-coverage went into due to the decision to include reporting. Now they struggle to take it out.

Read more comments on GitHub >

github_iconTop Results From Across the Web

NIH establishes website for self-reporting COVID-19 test results
Reporting a positive or negative test result just became easier through a new website from the National Institutes of Health.
Read more >
Test Results Reporting and Follow-up - HealthIT.gov
As part of quality assurance activities, organizations monitor selected practices related to test result reporting and follow-up. Monitored practices include.
Read more >
How to Report COVID-19 Laboratory Data - CDC
As of April 4, 2022, reporting of negative results for non-NAAT tests (rapid or antigen test results) is no longer required. These data...
Read more >
Reporting COVID-19 Self-Test Results: The Next Frontier
SYCT program participants could voluntarily report test results using a digital companion application developed by the company CareEvolution.
Read more >
Report a COVID-19 rapid lateral flow test result - GOV.UK
Use this service to report your result to the NHS after using a rapid lateral flow test kit to check if you're infectious...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found