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

feat: nextjs 15 e2e integration test setup #3772

Merged
merged 13 commits into from
Dec 18, 2024

Conversation

sidmohanty11
Copy link
Contributor

@sidmohanty11 sidmohanty11 commented Dec 9, 2024

Description

https://builder-io.atlassian.net/browse/ENG-7752

Screenshot
If relevant, add a screenshot or two of the changes you made.

Copy link

changeset-bot bot commented Dec 9, 2024

⚠️ No Changeset found

Latest commit: 7f39ee3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

nx-cloud bot commented Dec 9, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7f39ee3. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


🟥 Failed Commands
nx test @e2e/nuxt

Sent with 💌 from NxCloud.

@clyde-builderio
Copy link
Contributor

LGTM

@@ -44,9 +44,6 @@ const initializeAbTest = async (
) => {
if (!baseURL) throw new Error('Missing baseURL');

// SSR A/B tests do not seem to work on old NextJS. Likely a config issue.
test.skip(packageName === 'gen1-next');
Copy link
Contributor

Choose a reason for hiding this comment

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

🎉

!window.location.pathname.includes('can-track-false') &&
!window.location.pathname.includes('symbol-tracking')
) {
builder.canTrack = true;
Copy link
Contributor

Choose a reason for hiding this comment

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

only issue is im not sure if this will work on tests that include client-side navigations? This code should only run a single time when the JS is first loaded into the browser.

Just something to keep in mind

Copy link
Contributor Author

Choose a reason for hiding this comment

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

got it, so as canTrack=false tests are only on singular pages we don't face this

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