Skip to content

Add SaveChanges interceptor branch coverage tests#328

Merged
cdcavell merged 1 commit into
mainfrom
branch-coverage-below-70
Jun 29, 2026
Merged

Add SaveChanges interceptor branch coverage tests#328
cdcavell merged 1 commit into
mainfrom
branch-coverage-below-70

Conversation

@cdcavell

Copy link
Copy Markdown
Owner

Summary

  • Added branch-focused coverage tests for ApplicationSaveChangesInterceptor.
  • Covered the constructor null-guard branch.
  • Covered sync and async non-ApplicationDbContext branches where the interceptor should not invoke the application save pipeline.
  • Covered sync and async after-save branches where the pipeline requests one follow-up save.
  • Verified the nested save path is bounded by using a test pipeline that returns true only once.

Validation

  • Not run locally; changes were made through the GitHub connector.
  • CI should confirm test behavior and branch coverage impact.

Notes

I targeted the recently added SaveChanges interceptor branch paths because they are likely to be among the below-70 branch coverage areas after the EF Core save-pipeline refactor.

@cdcavell cdcavell merged commit 399b1a5 into main Jun 29, 2026
9 checks passed
@cdcavell cdcavell deleted the branch-coverage-below-70 branch June 29, 2026 18:37
@cdcavell cdcavell mentioned this pull request Jun 29, 2026
cdcavell added a commit that referenced this pull request Jun 29, 2026
## Summary

- Bumps shared build and template package version metadata from `2.1.0`
to `2.2.0`.
- Adds the `2.2.0` changelog entry covering the EF Core save-pipeline
extraction, composite SaveChanges interceptor, ChangeTracker enumeration
reduction, save-pipeline documentation, branch-focused interceptor
tests, and package/documentation image refresh.
- Updates template package release notes for the 2.2.0 minor release.
- Updates README, package README, template packaging docs, citation
metadata, and Zenodo metadata to reference `2.2.0`.

## Release Notes

This is a minor release because it introduces and documents a clearer EF
Core save-pipeline extension seam while preserving the stable `2.x`
package identity, template short name, template options, and default
scaffold behavior.

The default generated scaffold continues to use the same package
identity, template identity, authentication options, data-access
options, and local SQLite development path.

## Validation

- Not run locally; changes were made through the GitHub connector.
- CI should run the release branch validation, including build, tests,
coverage gate, template packing, scaffold smoke tests, and documentation
checks.
- Before publishing, run the release gate items from `RELEASE.md`,
including `./scripts/Validate-VersionConsistency.ps1`.

## Notes

- Branch was prepared from latest `main`, including the merged branch
coverage test PR #328.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant