From e89172c0603ab5bbbf12d633993c4fc7fabfaa3a Mon Sep 17 00:00:00 2001
From: soumah <soumah@adobe.com>
Date: Tue, 15 Sep 2026 10:52:13 -0500
Subject: [PATCH 1/2] ACP2E-4907: Documentation for dataprovider data injection
 into fixtures

---
 .../integration/attributes/data-fixture.md    | 30 +++++++++++++++++++
 .../guide/integration/data-fixtures-guide.md  | 29 ++++++++++++++++++
 2 files changed, 59 insertions(+)

diff --git a/src/pages/guide/integration/attributes/data-fixture.md b/src/pages/guide/integration/attributes/data-fixture.md
index 6173ec8..5ce266d 100644
--- a/src/pages/guide/integration/attributes/data-fixture.md
+++ b/src/pages/guide/integration/attributes/data-fixture.md
@@ -83,6 +83,36 @@ class QuoteTest extends \PHPUnit\Framework\TestCase
 }
 ```
 
+### Supply DataProvider or TestWith data to a fixture
+
+When a test method uses PHPUnit's `#[DataProvider]` or `#[TestWith]` attribute, the Integration Testing Framework automatically exposes the current dataset row as a fixture with the reserved alias `dataset`. You can reference its values with the same `$dataset.key$` syntax described above, without declaring a `DataFixture(...)` for it.
+
+This lets you collapse test methods that are only differentiated by fixture configuration into a single parameterized test.
+
+```php?start_inline=1
+class ProductStockTest extends \PHPUnit\Framework\TestCase
+{
+    #[
+        DataFixture(
+            ProductFixture::class,
+            ['extension_attributes' => ['stock_item' => ['is_in_stock' => '$dataset.in_stock$']]],
+            'product'
+        ),
+        TestWith(['in_stock' => true], 'in_stock'),
+        TestWith(['in_stock' => false], 'out_of_stock'),
+    ]
+    public function testProductStockStatus(bool $in_stock): void
+    {
+        $product = DataFixtureStorageManager::getStorage()->get('product');
+        $this->assertEquals($in_stock, $product->getExtensionAttributes()->getStockItem()->getIsInStock());
+    }
+}
+```
+
+-  If the test method does not use `#[DataProvider]` or `#[TestWith]`, the `dataset` fixture is not injected, and fixtures that do not reference `$dataset.*$` are unaffected.
+-  Referencing a key that does not exist in the current dataset (for example, `$dataset.unknownKey$`) throws an error listing the available keys.
+-  Unnamed DataProvider or TestWith parameters can be referenced by their numeric index, for example `$dataset.0$`.
+
 ### Specifying the number of instances of data fixture to generate
 
 <InlineAlert variant="info" slots="text" />
diff --git a/src/pages/guide/integration/data-fixtures-guide.md b/src/pages/guide/integration/data-fixtures-guide.md
index c5020cf..2cd9587 100644
--- a/src/pages/guide/integration/data-fixtures-guide.md
+++ b/src/pages/guide/integration/data-fixtures-guide.md
@@ -305,6 +305,35 @@ public function testCatalogRule(): void
 
 You can reference auto-generated values using `$alias.property$` syntax without overriding them.
 
+### Avoid duplicating tests that only differ by fixture data
+
+If multiple test methods share the same fixture stack and assertions, and only differ in the values passed to a fixture, use `#[DataProvider]` or `#[TestWith]` with the `dataset` alias instead of duplicating the test method per variation.
+
+```php
+// Bad - duplicated test methods, one per configuration
+#[DataFixture(ProductFixture::class, ['price' => 10], 'product')]
+public function testProductWithPriceTen(): void
+{
+}
+
+#[DataFixture(ProductFixture::class, ['price' => 20], 'product')]
+public function testProductWithPriceTwenty(): void
+{
+}
+
+// Good - a single parameterized test
+#[
+    DataFixture(ProductFixture::class, ['price' => '$dataset.price$'], 'product'),
+    TestWith(['price' => 10]),
+    TestWith(['price' => 20]),
+]
+public function testProduct(int $price): void
+{
+}
+```
+
+See [Supply DataProvider or TestWith data to a fixture](attributes/data-fixture.md#supply-dataprovider-or-testwith-data-to-a-fixture) for details.
+
 ### Understand isolation behavior
 
 <InlineAlert variant="info" slots="text" />

From 768223fcdff66a225f67582db98211736ffab7d3 Mon Sep 17 00:00:00 2001
From: Kevin Harper <keharper@users.noreply.github.com>
Date: Tue, 15 Sep 2026 11:37:36 -0500
Subject: [PATCH 2/2] Update
 src/pages/guide/integration/attributes/data-fixture.md

---
 src/pages/guide/integration/attributes/data-fixture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/guide/integration/attributes/data-fixture.md b/src/pages/guide/integration/attributes/data-fixture.md
index 5ce266d..6eca81c 100644
--- a/src/pages/guide/integration/attributes/data-fixture.md
+++ b/src/pages/guide/integration/attributes/data-fixture.md
@@ -111,7 +111,7 @@ class ProductStockTest extends \PHPUnit\Framework\TestCase
 
 -  If the test method does not use `#[DataProvider]` or `#[TestWith]`, the `dataset` fixture is not injected, and fixtures that do not reference `$dataset.*$` are unaffected.
 -  Referencing a key that does not exist in the current dataset (for example, `$dataset.unknownKey$`) throws an error listing the available keys.
--  Unnamed DataProvider or TestWith parameters can be referenced by their numeric index, for example `$dataset.0$`.
+-  Unnamed `DataProvider` or `TestWith` parameters can be referenced by their numeric index, for example `$dataset.0$`.
 
 ### Specifying the number of instances of data fixture to generate