Re-enable skipped Woo signup test and update woocommerce.com URL

[chihsuan]

Related to p1736297762145419-slack-C01SFMVEYAK

We disabled the Woo signup test in #98057 because it was failing and blocking the release.

The error occurs because the page navigation is being interrupted during the account activation step.

Navigation to "https://public-api.wordpress.com/bar/..." is interrupted by another navigation to "https://woocommerce.com/?error=access-denied"

Two navigation were happening at the same time because we didn't wait for the previous navigation to complete.

We have two points in the Slack thread but I believe it's not related to the error:

• It's expected that the test user will be redirected to https://woocommerce.com/?error=access-denied because when the user signs up and is redirected back to WCCOM, WCCOM will check a URL parameter state to see if it is through WooCommerce.com to Wordpress.com signup flow. If not, it will redirect to https://woocommerce.com/?error=access-denied. Our e2e test entry point is directly to the Wordpress.com signup URL instead of to WooCommerce.com because I think the e2e test shouldn't depend on external services like WCCOM.
• We changed the activation button text to Confirm your email. However, the e2e test is using the href to match the link instead of the text.

To fix the test, I added a waitUntil: 'networkidle' option to waitForURL and page.goto() calls. This should make the test more reliable. Additionally, I updated the URL in the e2e test from woo.com to woocommerce.com since we've already moved back to woocommerce.com.

Proposed Changes

• Updated the URL in the e2e test from woo.com to woocommerce.com since we've already moved back to woocommerce.com
• Re-enable the Woo signup test

Why are these changes being made?

• It's important to have the Woo signup test to make sure the WooCommerce.com signup flow is working as expected.

Testing Instructions

Pre-Release E2E Tests should pass

To test locally:

• Checkout this branch
• Set up local e2e test env https://github.com/Automattic/wp-calypso/tree/trunk/test/e2e
• Run the following tests

• yarn workspace wp-e2e-tests test test/e2e/specs/onboarding/signup__woo-email.ts
• yarn workspace wp-e2e-tests test -- test/e2e/specs/authentication/authentication__totp.ts

• Run tests a couple of times to see if it's flaky

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129564

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129564&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129564&env=a8c-for-agencies

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[rjchow]

This LGTM but teamcity says it's flaky (?) I couldn't find any failures on the teamcity log however. The tooltip for "flaky" says "Different test status for multiple invocations in the same build".

I'm wondering if it's just outdated status?

[chihsuan]

This LGTM but teamcity says it's flaky (?) I couldn't find any failures on the teamcity log however. The tooltip for "flaky" says "Different test status for multiple invocations in the same build".

I'm wondering if it's just outdated status?

Yeah, I believe it uses the historical data to determine if it's flaky.

[rjchow]

In that case, lgtm! 🚀