-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Tweak pangram tests per canonical-data #153
base: main
Are you sure you want to change the base?
Conversation
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.
Nice! Only one thing I would revert.
} | ||
|
||
pub fn a_m_and_upper_a_m_are_26_different_characters_but_not_a_pangram_test() { | ||
pub fn a_m_and_a_m_are_26_different_characters_but_not_a_pangram_test() { |
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.
I think the previous title was better, lost in generation I suppose
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.
Hm, yeah you're right, they get lost in the generation. I'm going to see if I can improve the test title upstream and regenerate.
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.
Nice! Could you revert the should.be_true
be changes please? It produces a worse error that does not include the location of the assertion.
I took another look at this and the include=false should actually be present, because it's been reimplemented with a different description and different (but equivalent) data. I'm going to put this one on hold while I look at the upstream fix. |
This removes an include=false from the tests.toml, as the
exclusion seems to have been unintentional (the new test
passes with no changes to the example solution).
It also switches to use the should.be_false / should.be_true style
that other tests use, rather than assert False / assert True.