-
Notifications
You must be signed in to change notification settings - Fork 221
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
Add test to assert that issue 389 is resolved. #744
Conversation
Tidy up imports in tests in the same file as new test written. Resolves #389
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #744 +/- ##
==========================================
+ Coverage 96.07% 96.09% +0.01%
==========================================
Files 55 55
Lines 2244 2251 +7
Branches 246 246
==========================================
+ Hits 2156 2163 +7
Misses 53 53
Partials 35 35 ☔ View full report in Codecov by Sentry. |
Make docstring make sense!
|
||
@given(parsers.parse('Action "{action}" is taken')) | ||
def take_action1(action): | ||
print(f'take_action1:{action}') |
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.
let's use dumb_obj
and collect_dumped_obj
instead, I made them for exactly this purpose
|
||
|
||
def test_same_name_for_step_arg_and_example_parameter(pytester): | ||
"""Test that using the same name for step arg and example parameter works as intended.""" |
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.
still not clear what we are testing here. Is it about params being filled from example tables vs from parsing the step name?
If so let's make it clearer in the docstring.
Maybe let's also rewrite the step names, like:
- Given foo gets value "A" by the step parser
- Given bar gets value <example_value> from the example table
This would be much clearer to me
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 other test is actually testing the same thing and this can be closed
Tidy up imports in tests in the same file as new test written.
Resolves #389