We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When tests are run in STRICT mode, we check for any errors or warnings in the report.
We currently have two functions:
test_utils.check_report https://github.com/EducationalTestingService/rsmtool/blob/main/rsmtool/test_utils.py#L767 checks for both errors and warnings
test_utils.check_report
collect_warning_messages_from_report https://github.com/EducationalTestingService/rsmtool/blob/main/rsmtool/test_utils.py#L737 once again collects warning messages.
collect_warning_messages_from_report
The warnings that are excluded under check_report would still be flagged as errors by collect_warning_messages_from_report.
check_report
We need to figure out why we have these two functions and streamline them.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When tests are run in STRICT mode, we check for any errors or warnings in the report.
We currently have two functions:
test_utils.check_report
https://github.com/EducationalTestingService/rsmtool/blob/main/rsmtool/test_utils.py#L767 checks for both errors and warningscollect_warning_messages_from_report
https://github.com/EducationalTestingService/rsmtool/blob/main/rsmtool/test_utils.py#L737 once again collects warning messages.The warnings that are excluded under
check_report
would still be flagged as errors bycollect_warning_messages_from_report
.We need to figure out why we have these two functions and streamline them.
The text was updated successfully, but these errors were encountered: