Skip to content

Conversation

shawnemhe
Copy link

Minor change to prevent raising an error when attempting to create a cucumber json in a directory that has not been created yet. This breaks form with the standard pytest --junitxml functionality which would create the path in this situation.

Fixes error when attempting to create a cucumber json in a directory
has not been created yet.
@codecov-io
Copy link

codecov-io commented Feb 18, 2020

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.82%. Comparing base (f3b92bd) to head (1ec12d6).
⚠️ Report is 859 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #347      +/-   ##
==========================================
+ Coverage   95.80%   95.82%   +0.01%     
==========================================
  Files          57       57              
  Lines        2217     2227      +10     
  Branches      185      188       +3     
==========================================
+ Hits         2124     2134      +10     
  Misses         62       62              
  Partials       31       31              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@youtux
Copy link
Contributor

youtux commented Mar 1, 2020

Hi @shawnemhe, thank you for this fix. Could you write a test for it too?

Modified runandparse to check if the new test has added a
"missing_subdirectory" attribute. Verified that this doesn't break the
functionality of the already existing cucumber tests.
Using a fixture now to run all cucumber tests with and without
missing subdirectory.
Also fixed formatting issues identified in build test.
@shawnemhe
Copy link
Author

Hi @youtux, it is testing now by parametrizing the testdir fixture so that of the cucumber tests run with and without a missing subdirectory.

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.

3 participants