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

Testing Strategy Improvements #88

Closed
3 tasks
DK96-OS opened this issue Apr 6, 2022 · 0 comments
Closed
3 tasks

Testing Strategy Improvements #88

DK96-OS opened this issue Apr 6, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@DK96-OS
Copy link
Owner

DK96-OS commented Apr 6, 2022

Another piece of the strategy is to look for changes in work required on large inputs. The CompareFactors.lcm method is the most impacted by changes in inputs. It appears that this method has no tests on inputs larger than 256.

Originally posted by @DK96-OS in #86 (comment)

It is important that valid inputs to public methods be determined and demonstrated by test cases. This example of a chaotic method shows how Testing Strategy needs improvements.

Define a system that iteratively:

  • Determines testing requirements
  • Creates and organizes test cases
  • Inspects and improves existing test cases
@DK96-OS DK96-OS added the documentation Improvements or additions to documentation label Jun 3, 2022
@DK96-OS DK96-OS closed this as completed Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant