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.

Sign up for GitHub

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

Jump to bottom

Cleaned up assert_cases_equal test utility a bit. #779

Merged
merged 2 commits into from
Jul 11, 2022
Merged

Cleaned up assert_cases_equal test utility a bit. #779

merged 2 commits into from
Jul 11, 2022

Conversation

robfalck
Copy link
Contributor

Summary

The assert_cases_equal utility now prints a more terse error message when value differences are found between two cases.

Related Issues

Backwards incompatibilities

None

New Dependencies

None

@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.517% when pulling dfca11d on robfalck:assert_cases_equal_update into a5f9187 on OpenMDAO:master.

@robfalck robfalck merged commit bb1cadc into OpenMDAO:master Jul 11, 2022
@robfalck robfalck deleted the assert_cases_equal_update branch August 25, 2022 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kaushikponnapalli kaushikponnapalli kaushikponnapalli approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Cleanup assert_cases_equal.
3 participants
@robfalck @coveralls @kaushikponnapalli