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

[TASK] Test finding util #2430

Open
5 of 10 tasks
caleb-sitton-inl opened this issue Jan 28, 2025 · 0 comments
Open
5 of 10 tasks

[TASK] Test finding util #2430

caleb-sitton-inl opened this issue Jan 28, 2025 · 0 comments
Assignees
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@caleb-sitton-inl
Copy link
Collaborator

caleb-sitton-inl commented Jan 28, 2025


Issue Description

Is your feature request related to a problem? Please describe.
It would be helpful to have a util that lists all the rook tests by name in a specified directory.

Describe the solution you'd like
The get_coverage_tests script is very similar to this and can be expanded to include broader functionality.

Describe alternatives you've considered


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@caleb-sitton-inl caleb-sitton-inl added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Jan 28, 2025
@caleb-sitton-inl caleb-sitton-inl self-assigned this Jan 28, 2025
@caleb-sitton-inl caleb-sitton-inl changed the title [TASK] Expand get coverage tests script functionality [TASK] Test finding util Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

No branches or pull requests

1 participant