-
Notifications
You must be signed in to change notification settings - Fork 2
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
Declutter functionality test #218
base: develop
Are you sure you want to change the base?
Conversation
Looks good and tests pass. Just fix the merge conflict. |
ReSolve::VectorHandler vector_handler(&workspace); | ||
ReSolve::GramSchmidt GS(&vector_handler, ReSolve::GramSchmidt::CGS2); | ||
ReSolve::LinSolverIterativeFGMRES FGMRES(&matrix_handler, &vector_handler, &GS); | ||
FGMRES.setMaxit(200); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For test I guess it is okay, but as you are using CliOptions, it may be well-suited to document how you use it here. So, if the CliOptions has been provided for Maximum iterations use it or use the default is 200.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very good point @maksud. This will also simplify the test case further by hiding data conversion from the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test looks clean indeed. It works for me.
This is a proposal how to declutter functionality tests and expand testing scope. Checking results and computing different error norms is moved into a testing helper class to make the main body of the test cleaner and more focused on solver calls. The proposal also includes using command line input to configure tests and generating multiple tests from a single source file.