Skip to content

3.0.0-518.Beta

3.0.0-518.Beta: Prepare EFTools for provider-selectable Azure SQL certification (#20)
@ProphetManX ProphetManX tagged this 12 Sep 03:53 
* Checkpoint SQL Server certification work

* Retain provider state and reject foreign store identities

Each disposable test store must keep the provider and generated identity it
was created with so configuration and disposal address the same selected
database. Reject identities outside the disposable EFToolsTest_ namespace
before registration or provisioning so shared or foreign databases cannot be
treated as owned test state.

- Retain the constructor's provider and identity for configuration and cleanup
- Reject non-disposable identities before they enter the live registry

Validated with the focused external SQL Server run at 58/58/0/0 and the
unfiltered external SQL Server suite at 328/328/0/0 with zero skipped tests.
The Test Auditor and Code Reviewer are Ready; cleanup audits found zero
disposable databases before and after the final run.

* Record local SQL Server Gate 1 evidence

Document the externally selected, unfiltered local SQL Server run that passed 328/328
cases with zero failures or skips, while preserving the remaining certification
boundaries.

- Keep FR 11 Scheduled for SQLite and pipeline residual work
- Leave Azure SQL FR 19 open as the unsatisfied Gate 2
- Capture the local certificate-validation decision as Proposed FR 20
- Retain portable references to the external Gate 1 evidence report

* Record deployed Azure SQL certification fixture

* Add reusable provider test-store coverage

The provider-backed tests need to reuse isolated stores while preserving provider identity and making reset and cleanup failures observable.

* Document Azure SQL certification fixture and execution

The repository needs one consistent description of the Azure SQL fixture, its required evidence, and the boundaries around deployment and test-store use.

* Align repository scope and governance documentation

Refresh the agent guidance and repository profile. Align the README, purpose-and-scope document, decision log, and feature request record with the reusable-store and certification work.

* Record the Example repository revision

Point the EFTools proving-ground submodule at the locally prepared Example revision so the intended test inputs are recorded with the consumer.

* commiting agents changes

* Correct stale Azure SQL review status documentation

Update the Azure SQL documentation to reflect the current parameter and review
status without implying certification, infrastructure clearance, or release
approval.

- Describe the fixture identity and firewall inputs as required owner-supplied
  parameters with no defaults, and record the narrow accepted history fallback.
- Replace the obsolete planned-review date with the current pending-review
  status while preserving the Gate 2, FR 19, and release boundary.
- Keep the root status accurate about the settled fixture-source decision and
  the limits of independent verification.

BREAKING: None
Assets 2
Loading