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

Copy of #6173 (smoke tests + replay) #6361

Merged
merged 27 commits into from
Sep 15, 2022
Merged

Copy of #6173 (smoke tests + replay) #6361

merged 27 commits into from
Sep 15, 2022

Conversation

jtoar
Copy link
Contributor

@jtoar jtoar commented Sep 8, 2022

@ryanjduffy copy of #6173 with the commit to fix the yarn.lock. Also see #6173 (comment).

@jtoar jtoar changed the title [Debugging] Copy of #6173 [Debugging] Copy of https://github.com/redwoodjs/redwood/pull/6173 Sep 8, 2022
@jtoar jtoar changed the title [Debugging] Copy of https://github.com/redwoodjs/redwood/pull/6173 [Debugging] Copy of #6173 (smoke tests + replay) Sep 8, 2022
@jtoar jtoar added the release:feature This PR introduces a new feature label Sep 8, 2022
.github/workflows/ci.yml Outdated Show resolved Hide resolved
@@ -56,6 +56,7 @@
"@babel/runtime-corejs3": "7.18.9",
"@nrwl/nx-cloud": "14.3.0",
"@playwright/test": "1.25.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

We only officially support playwright v1.19 because newer versions do not work with Firefox. If you stick with chromium, you should be okay but keep an eye out for playwright errors if you continue to update the version.

This story will improve in the coming weeks when we update our Firefox fork to the latest ESR (102.2).

@jtoar
Copy link
Contributor Author

jtoar commented Sep 13, 2022

@ryanjduffy just letting you know that we'll get this merged soon! We're experiencing some flakiness on the Windows runners in general, so that failing test isn't related to this PR. And we're also holding back on making too many CI changes till we cut another release (which should happen in the next few days)

@ryanjduffy
Copy link
Contributor

Sounds good! We've also released a batch of fixes that have improved the stability of all of the redwood recordings. Hopefully that means you'll have a pretty good experience debugging in Replay but of course let us know when you hit issues!

@ryanjduffy
Copy link
Contributor

In case y'all hadn't seen this yet, I wanted to call out our GitHub app which will comment on PRs with replay links for passed and/or failed tests. You can always get to them from the action output as well but I find it nice to have them surfaced in the PR too.

image

https://docs.replay.io/recording-browser-tests-(beta)/pull-request-comments

@jtoar
Copy link
Contributor Author

jtoar commented Sep 15, 2022

@ryanjduffy heads up that smoke tests are failing because of a downstream dependency: mswjs/interceptors#285. Was just about to merge this too. I'm sure it'll be resolved soon!

@jtoar jtoar changed the title [Debugging] Copy of #6173 (smoke tests + replay) Copy of #6173 (smoke tests + replay) Sep 15, 2022
@jtoar jtoar enabled auto-merge (squash) September 15, 2022 16:19
@jtoar jtoar merged commit 51cfa13 into main Sep 15, 2022
@jtoar jtoar deleted the copy-of-replay-branch branch September 15, 2022 16:59
@redwoodjs-bot redwoodjs-bot bot added this to the next-release milestone Sep 15, 2022
@jtoar jtoar modified the milestones: next-release, v3.1.0 Sep 28, 2022
@jtoar jtoar mentioned this pull request Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:feature This PR introduces a new feature
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants