diff --git a/docs/docs-manifest.json b/docs/docs-manifest.json index f9202494110..9896e658e12 100644 --- a/docs/docs-manifest.json +++ b/docs/docs-manifest.json @@ -1411,7 +1411,7 @@ "categories": [] }, { - "content": "\nProperly setting up your test environment and writing tests when contributing to WooCommrece core are essential parts of our development pipeline. The links below are also included in our [Contributing Guidelines](https://github.com/woocommerce/woocommerce/blob/trunk/.github/CONTRIBUTING.md) on GitHub.\n\nIf you have any questions about testing please reach out to the developer community in our public channels([Developer Blog](https://developer.woocommerce.com/blog/), [GitHub Discussions](https://github.com/woocommerce/woocommerce/discussions), or [Community Slack](https://woocommerce.com/community-slack/)).\n\n## Unit Testing\n\n[End-to-end tests](https://github.com/woocommerce/woocommerce/tree/trunk/plugins/woocommerce/tests/e2e-pw) are powered by `Playwright`. The test site is spun up using `wp-env` ([recommended](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/)), but we will continue to support `e2e-environment` in the meantime, and slowly [deprecate](https://github.com/woocommerce/woocommerce/blob/trunk/plugins/woocommerce/tests/e2e/README.md) `Puppeteer` testing. \n\n## API Testing\n\n`api-core-tests` is a [package](https://github.com/woocommerce/woocommerce/tree/trunk/plugins/woocommerce/tests/api-core-tests#guide-for-writing-api-tests) that contains automated API tests for WooCommerce, based on `Playwright` and `wp-env`. It supersedes the SuperTest based `api-core-tests` package and `e2e-environment` setup, which we will gradually deprecate.\n\n## Calls for Testing\n\nKeep tabs on calls for testing on our developer blog, and make sure to read our beta testing instructions to help us build new features and enhancements.\n", + "content": "\nProperly setting up your test environment and writing tests when contributing to WooCommerce core are essential parts of our development pipeline. The links below are also included in our [Contributing Guidelines](https://github.com/woocommerce/woocommerce/blob/trunk/.github/CONTRIBUTING.md) on GitHub.\n\nIf you have any questions about testing please reach out to the developer community in our public channels([Developer Blog](https://developer.woocommerce.com/blog/), [GitHub Discussions](https://github.com/woocommerce/woocommerce/discussions), or [Community Slack](https://woocommerce.com/community-slack/)).\n\n## Unit Testing\n\n[End-to-end tests](https://github.com/woocommerce/woocommerce/tree/trunk/plugins/woocommerce/tests/e2e-pw) are powered by `Playwright`. The test site is spun up using `wp-env` ([recommended](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/)), but we will continue to support `e2e-environment` in the meantime, and slowly [deprecate](https://github.com/woocommerce/woocommerce/blob/trunk/plugins/woocommerce/tests/e2e/README.md) `Puppeteer` testing. \n\n## API Testing\n\n`api-core-tests` is a [package](https://github.com/woocommerce/woocommerce/tree/trunk/plugins/woocommerce/tests/api-core-tests#guide-for-writing-api-tests) that contains automated API tests for WooCommerce, based on `Playwright` and `wp-env`. It supersedes the SuperTest based `api-core-tests` package and `e2e-environment` setup, which we will gradually deprecate.\n\n## Calls for Testing\n\nKeep tabs on calls for testing on our developer blog, and make sure to read our beta testing instructions to help us build new features and enhancements.\n", "category_slug": "testing", "category_title": "Testing", "posts": [ diff --git a/docs/testing/README.md b/docs/testing/README.md index 1ad733872aa..df176bd42cc 100644 --- a/docs/testing/README.md +++ b/docs/testing/README.md @@ -4,7 +4,7 @@ category_slug: testing post_title: Testing --- -Properly setting up your test environment and writing tests when contributing to WooCommrece core are essential parts of our development pipeline. The links below are also included in our [Contributing Guidelines](https://github.com/woocommerce/woocommerce/blob/trunk/.github/CONTRIBUTING.md) on GitHub. +Properly setting up your test environment and writing tests when contributing to WooCommerce core are essential parts of our development pipeline. The links below are also included in our [Contributing Guidelines](https://github.com/woocommerce/woocommerce/blob/trunk/.github/CONTRIBUTING.md) on GitHub. If you have any questions about testing please reach out to the developer community in our public channels([Developer Blog](https://developer.woocommerce.com/blog/), [GitHub Discussions](https://github.com/woocommerce/woocommerce/discussions), or [Community Slack](https://woocommerce.com/community-slack/)). diff --git a/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/722.md b/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/722.md index 83343897605..764de5c36ea 100644 --- a/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/722.md +++ b/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/722.md @@ -6,7 +6,7 @@ ### WC-Admin doesn't crash when WC Subscriptions is installed. ([6260](https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/6260)) -1. Go to an atomic website (or locally with symlinked WooCommrece). +1. Go to an atomic website (or locally with symlinked WooCommerce). 2. Install WC Subscriptions. 3. Try to open wp-admin > WooCommerce > Home (/wp-admin/admin.php?page=wc-admin). 4. Page should load normally. diff --git a/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/741.md b/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/741.md index 5806c7c1f0f..39f3b2ac2a3 100644 --- a/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/741.md +++ b/plugins/woocommerce-blocks/docs/internal-developers/testing/releases/741.md @@ -6,7 +6,7 @@ Zip file for testing: [woocommerce-gutenberg-products-block.zip](https://github. ### WC-Admin doesn't crash when WC Subscriptions is installed. ([6260](https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/6260)) -1. Go to an atomic website (or locally with symlinked WooCommrece). +1. Go to an atomic website (or locally with symlinked WooCommerce). 2. Install WC Subscriptions. Try to open wp-admin > WooCommerce > Home (/wp-admin/admin.php?page=wc-admin). 3. Page should load normally. diff --git a/plugins/woocommerce/changelog/50333-patch-20 b/plugins/woocommerce/changelog/50333-patch-20 new file mode 100644 index 00000000000..2452062a034 --- /dev/null +++ b/plugins/woocommerce/changelog/50333-patch-20 @@ -0,0 +1,4 @@ +Significance: patch +Type: tweak +Comment: Fix typos (WooCommrece) +