[LYS] Add Homescreen and Settings e2e tests

[psealock]

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

Closes #47298

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

1. See tests make sense
2. Check CI passes

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Comment

add e2e tests to previously unreleased feature

[github-actions]

Test using WordPress Playground

The changes in this pull request can be previewed and tested using a WordPress Playground instance.
WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Test this pull request with WordPress Playground.

Note that this URL is valid for 30 days from when this comment was last updated. You can update it by closing/reopening the PR or pushing a new commit.

[github-actions]

Hi @ilyasfoo, @rjchow, @woocommerce/ghidorah

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Hi @ilyasfoo, @rjchow, @woocommerce/ghidorah

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[rjchow]

Tests look sound and they pass, thanks!

[ilyasfoo]

Thanks for the improvements, @psealock! This is good to go but I have a feedback on making the test more resistant to changes in core profiler

[ilyasfoo]

Optional: Since we're not really looking to test core profiler here, might it be better for us to skip it programatically? For example, here's how we reset it directly with an API, perhaps we can create a similar helper to "skip" or "complete" it.

woocommerce/packages/js/e2e-utils/src/flows/with-rest-api.js

Lines 70 to 90 in 34f8c65

	resetOnboarding: async () => {
	const onboardingReset = {
	completed: false,
	industry: [],
	business_extensions: [],
	skipped: false,
	product_types: [],
	product_count: '0',
	selling_venues: 'no',
	revenue: 'none',
	theme: '',
	setup_client: false,
	wccom_connected: false,
	};
	const response = await client.put(
	onboardingProfileEndpoint,
	onboardingReset
	);
	expect( response.statusCode ).toEqual( 200 );
	},

If we need to initialize coming soon options, we can directly call this API:

woocommerce/plugins/woocommerce/src/Admin/API/LaunchYourStore.php

Lines 39 to 49 in 34f8c65

	register_rest_route(
	$this->namespace,
	'/' . $this->rest_base . '/initialize-coming-soon',
	array(
	array(
	'methods' => 'POST',
	'callback' => array( $this, 'initialize_coming_soon' ),
	'permission_callback' => array( $this, 'must_be_shop_manager_or_admin' ),
	),
	)
	);