[xperiandri]

Proposed Changes

A scenario is a class that writes the data of a test class into the database of each test before the test starts. The tests read this data. They do not write it. This pull request writes down how to make a scenario. It also makes the two scenarios of the repository obey the new rule. The review of #67 asked for this rule: "If you always seed the same data why don't you derive from OperationTestBase<> with scenario?"

• SingleItemScenario and MultipleItemsScenario are now in files of their own in tests/Cosmos.Tests/Scenarios/, each in a namespace of its own. Each scenario creates its data in the constructor of TestApplicationFactory and writes the data in SeedDataAsync. The tests read the values from a [<Struct>] record TestData with a record pattern. They refer to the TestApplicationFactory of a scenario through the namespace of the scenario, for example OperationTestBase<SingleItemScenario.TestApplicationFactory>. Thus the test class shows which scenario it uses. They open the namespace for the other types of the scenario. Before this change, MultipleItemsScenario gave an F# list. Thus each test had to match the list and fail on a wrong length.
• .github/instructions/test-scenarios.instructions.md has only the rules that apply to each test file: when a scenario is necessary, when a test writes its own data, and how a test refers to a scenario. Copilot uses it for tests/**/*.fs, and Claude Code reads it through .claude/rules/test-scenarios.md. The procedure is not repeated there: an instructions file loads with each test file, a skill loads only when an agent writes a scenario.
• .github/skills/test-data-seeding/SKILL.md tells how to write a scenario and its test class. It comes from the skill with the same name in the application of the maintainer. It is changed for the test infrastructure of this repository: DatabaseTestApplicationFactory, OperationTestBase<_> and CosmosAssert. Its two examples compile, and the example test passes on the emulator. Copilot finds the skill in .github/skills (skill locations). Claude Code finds it through the .claude/skills junction that Directory.Build.targets creates. This is the first skill of the repository, so the junction did not exist before.

Types of changes

What types of changes does your code introduce to FSharp.Azure.Cosmos?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

The change has no effect on the library. It changes only tests and instructions.

Checklist

• Build and tests pass locally: the 14 tests of the categories "Read", "Read many" and "Iteration extensions" pass on the Windows emulator.
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Further comments

#67 builds on this pull request. Its scenario DurationsScenario has the same form.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

The refactor preserves existing seeding behavior, and no blocking issues remain.

No open issues 🎉

What changed in this PR

Documents the reusable emulator test scenario pattern requested in #67 and updates existing tests to follow it, without changing the library.

Changes:

• Adds scenario rules and a test-data-seeding skill.
• Extracts both scenarios into dedicated files with struct TestData records.
• Updates tests to read seeded values through record patterns.

File	Description
tests/​Cosmos.Tests/​Scenarios/​SingleItemScenario.fs	Extracts the single-item scenario.
tests/​Cosmos.Tests/​Scenarios/​MultipleItemsScenario.fs	Extracts the two-item scenario.
tests/​Cosmos.Tests/​ReadOperationTests.fs	Uses the single-item data record.
tests/​Cosmos.Tests/​ReadManyOperationTests.fs	Replaces list matching with record matching.
tests/​Cosmos.Tests/​IterationExtensionsTests.fs	Uses the shared two-item data record.
tests/​Cosmos.Tests/​FSharp.Azure.Cosmos.Tests.fsproj	Compiles scenarios before their consumers.
.github/​skills/​test-data-seeding/​SKILL.md	Provides scenario guidance and examples.
.github/​instructions/​test-scenarios.instructions.md	Defines test scenario rules.
.claude/​rules/​test-scenarios.md	Shares the rules with Claude Code.

_{Review effort: Balanced}