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

Systematic testing enhancements #4161

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dipinhora
Copy link
Contributor

Update SYSTEMATIC_TESTING_PRINTF to take a level argument.
Add cli argument for controlling output level of systematic testing printf's.
Add SYSTEMATIC_TESTING_YIELD and SYSTEMATIC_TESTING_PRINTF in a lot more places.

@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Jul 16, 2022
" Use a specific seed value for systematic testing.\n" \
" --ponysystematictestingverbosity\n" \
" Control verbosity of systematic testing output.\n" \
" 0 is least verbose; greater is more details.\n" \
Copy link
Member

@jemc jemc Jul 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to mention here what the highest meaningful value this could be is.

Is it 3? 5? 9? 99? 999?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now the max value used is 10 (for no particular reason) but i haven't figured out how the levels of details should work and how far they should go (any ideas?). i expect that the levels of detail is something that will eventually get well defined and stabilized over time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have opinions about how high the levels of verbosity should go - whatever you have now (e.g. 10) is probably fine.

I just think that this documentation string should mention that maximum number so that I (as a user seeing this documentation string) don't need to search through the whole codebase to find out what the highest meaningful number is.

@jemc jemc removed the discuss during sync Should be discussed during an upcoming sync label Jul 19, 2022
@dipinhora
Copy link
Contributor Author

rebased to fix merge conflicts

@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Aug 4, 2022
Update SYSTEMATIC_TESTING_PRINTF to take a level argument.
Add cli argument for controlling output level of systematic testing printf's.
Add SYSTEMATIC_TESTING_YIELD and SYSTEMATIC_TESTING_PRINTF in a lot more places.
@dipinhora
Copy link
Contributor Author

rebased to fix merge conflicts

@SeanTAllen
Copy link
Member

Once @jemc's comment about max value is addressed, I'm ok with these changes especially given that this is a new feature that I haven't used and I trust that @dipinhora is doing the right thing.

@SeanTAllen SeanTAllen removed the discuss during sync Should be discussed during an upcoming sync label Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants