Skip to content

armgit / spree

Public Imported from GitHub
0

Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.

Update testing.md (#10974)

Marcin Zamorski12b4b9f685e2
diff --git a/guides/src/content/developer/4_advanced/testing.md b/guides/src/content/developer/4_advanced/testing.md
index 3b354e6c9f..69d16c3b94 100644
--- a/guides/src/content/developer/4_advanced/testing.md
+++ b/guides/src/content/developer/4_advanced/testing.md
@@ -11,7 +11,7 @@ The Spree test code is an evolving story. We started out with RSpec, then switch
## Testing Spree Components
-Spree consists of several different gems (see the [Source Code Guide](/developer/source/navigating.html#layout-and-structure) for more details.) Each of these gems has its own test suite which can be found in the `spec` directory. Since these gems are also Rails engines, they can't really be tested in complete isolation - they need to be tested within the context of a Rails application.
+Spree consists of several different gems (see the [Understanding Spree](/developer/getting_started/understanding_spree.html#spree-modules) for more details.) Each of these gems has its own test suite which can be found in the `spec` directory. Since these gems are also Rails engines, they can't really be tested in complete isolation - they need to be tested within the context of a Rails application.
You can easily build such an application by using the Rake task designed for this purpose, running it inside the component you want to test: