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

[FIX-#219] add conditions to avoid log file is still generated after succe… #288

Merged
merged 2 commits into from
Mar 10, 2022
Merged

Conversation

stu01509
Copy link
Contributor

@stu01509 stu01509 commented Mar 8, 2022

Description

Hi @bahmutov

According to this issue #219, I've implemented a new feature to check should we write the log files after the test retry is successful.

Hope you could take some time to help me review this PR, and merge it :)

Changes

  • Add getRetriesTimes() function to get the Cypress config retry times.
  • Create the failedCaseTable to record the test case retry times.

@bahmutov
Copy link
Owner

Ok, let me take a look at this.

@bahmutov bahmutov changed the base branch from master to retries March 10, 2022 14:37
@bahmutov bahmutov merged commit 9c7ee15 into bahmutov:retries Mar 10, 2022
@stu01509
Copy link
Contributor Author

Hi @bahmutov

Thanks for your merge, could you publish the new version to npm?

bahmutov added a commit that referenced this pull request Mar 10, 2022
* [FIX-#219] add conditions to avoid log file is still generated after succe… (#288)

* feat: add conditions to avoid log file is still generated after successful retry

* feat: add conditions to avoid log file is still generated after successful retry

* refactoring

* more refactoring

Co-authored-by: Cliff Su <stu01509@yahoo.com.tw>
@stu01509 stu01509 deleted the feat-retry branch April 13, 2022 14:55
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.

2 participants