Earlier, the output from the code was not compared to a result description for the framework tests. The tests were passing if they run through without any errors. In this MR, a result description is added in the input file, which is then compared to the output and an error is thrown if the results do not match.
Related Issues and Pull Requests
Closes #43
Blocks
Is blocked by
Follows PR #51
Precedes
Related to
Part of
Composed of
How Has This Been Tested?
Running ctest with incorrect results in the result_description shows up as a failed test. Not providing any result_description in the input file does not constitute any error.
Checklist
[ ] My commit messages mention the appropriate GitHub issue numbers and are longer than one line where appropriate.
[ ] I have added/updated documentation where necessary.
Description and Context
Earlier, the output from the code was not compared to a result description for the framework tests. The tests were passing if they run through without any errors. In this MR, a result description is added in the input file, which is then compared to the output and an error is thrown if the results do not match.
Related Issues and Pull Requests
How Has This Been Tested?
Running
ctestwith incorrect results in the result_description shows up as a failed test. Not providing any result_description in the input file does not constitute any error.Checklist
Additional Information
Interested Parties / Possible Reviewers
@isteinbrecher @mayrmt