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

improve tracing for tests #230

Open
1 of 4 tasks
florianschanda opened this issue Aug 11, 2021 · 0 comments
Open
1 of 4 tasks

improve tracing for tests #230

florianschanda opened this issue Aug 11, 2021 · 0 comments
Labels
tool: mh_trace Affects the tracing tool
Milestone

Comments

@florianschanda
Copy link
Owner

florianschanda commented Aug 11, 2021

  • All code in a "testing" directory (as indicated by a miss_hit.cfg should be flagged as a test)
  • Otherwise, the following block properties indicate setup code and should also flag code as test:
    • TestMethodSetup
    • TestMethodTeardown
    • TestClassSetup
    • TestClassTeardown
    • TestParameterDefinition
  • Auxiliary functions (in a test class or at the end of the file) should be flagged as tests
  • New config parameter to defined how auxiliary code (all the above) should be treated by mh_trace
    • ignore (the default: exclude it all, never shows up in tracing)
    • include_when_tagged (don't show, except if there is a tag)
    • include (always include it)
@florianschanda florianschanda added the tool: mh_trace Affects the tracing tool label Aug 11, 2021
@florianschanda florianschanda added this to the 0.9.27 milestone Aug 11, 2021
florianschanda added a commit that referenced this issue Aug 30, 2021
* Now all files/directories under the testing directories are
  considered to be test code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tool: mh_trace Affects the tracing tool
Projects
None yet
Development

No branches or pull requests

1 participant