Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage of py.test and test coverage #1201

Closed
andy-maier opened this issue Apr 11, 2018 · 3 comments
Closed

Usage of py.test and test coverage #1201

andy-maier opened this issue Apr 11, 2018 · 3 comments

Comments

@andy-maier
Copy link
Contributor

andy-maier commented Apr 11, 2018

This issue lists all unit test cases with their pytest migration status and with their missing lines of test coverage in the module the test scripts are targeting to test.

Test scripts that don't exist yet:

  • test_mock_dmtf_cim_schema.py

Test scripts that have partially moved to pytest:

Test scripts that have not moved to pytest at all yet:

  • test_mof_compiler.py (286 missing lines)
  • test_cim_http.py (195 missing lines - hard to test)
  • test_recorder.py (127 missing lines)
  • test_indicationlistener.py (114 missing lines)
  • test_cim_xml.py (15 missing lines)
  • test_statistics.py (7 missing lines)

Test scripts that are completely using pytest:

@KSchopmeyer
Copy link
Collaborator

KSchopmeyer commented Apr 11, 2018

There is a log capture for pytest-logcapture. It might even be a bit more flexible in that it does not require complete compare. Another one is pytest-catchlog forked from the first. It appears thatcatchlog has been integrated into pytest core https://github.com/eisensheng/pytest-catchlog

@andy-maier andy-maier changed the title Migrate unit tests from unittest to py.test Usage of py.test for unit tests and test coverage May 9, 2018
@andy-maier andy-maier changed the title Usage of py.test for unit tests and test coverage Usage of py.test and test coverage May 9, 2018
@andy-maier
Copy link
Contributor Author

We decided to move the remainder of testcases to the next release, and close this one for 0.13.0. A new issue will be created for the next release.

@andy-maier
Copy link
Contributor Author

andy-maier commented Feb 22, 2019

Issue #1414 has been created for the remaining migrations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants