Skip to content

update#283

Merged
baoduy merged 4 commits intomainfrom
dev
Mar 27, 2026
Merged

update#283
baoduy merged 4 commits intomainfrom
dev

Conversation

@baoduy
Copy link
Copy Markdown
Owner

@baoduy baoduy commented Mar 27, 2026

This pull request introduces a comprehensive specification and supporting artifacts for migrating SQL-dependent integration tests to parallel-safe execution. It includes new documentation, data models, OpenAPI contracts, and updates to CI pipelines to enable and validate parallel test runs for targeted .NET projects. The main goals are to improve CI throughput, ensure deterministic test isolation, and formalize exception handling for SQL-specific test cases.

The most important changes are:

Specification & Documentation

  • Added detailed implementation plan (plan.md), quickstart guide (quickstart.md), and requirements checklist for the parallelization of SQL integration tests, covering technical context, constitution checks, migration steps, and validation procedures. [1] [2] [3]

Data Model & API Contracts

  • Defined a data model (data-model.md) for tracking integration test projects, test store profiles, parallel execution runs, and migration exceptions, including validation rules and state transitions.
  • Introduced a formal OpenAPI contract (itest-parallelization.openapi.yaml) specifying endpoints for managing migration status, test store profiles, parallel run evidence, and exception records.

CI Pipeline Enhancements

  • Updated Azure Pipelines (azure-pipelines.yml, ai-pr-review.azure-pipelines.yml) to enable parallel test execution for targeted projects by adding the -- RunConfiguration.MaxCpuCount=0 argument to dotnet test commands and installing the required .NET SDK. [1] [2]

These changes collectively establish the foundation for migrating and validating SQL integration tests for parallel execution, improving CI efficiency, and ensuring robust exception handling for non-portable SQL scenarios.

baoduy added 4 commits March 27, 2026 15:16
# Conflicts:
#	src/EfCore/EfCore.Specifications.Tests/SpecFilterTests.cs
@baoduy baoduy merged commit a32279b into main Mar 27, 2026
8 of 9 checks passed
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 27, 2026

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 84.40%. Comparing base (d5b7459) to head (19af75c).
⚠️ Report is 10 commits behind head on main.

Files with missing lines Patch % Lines
...tensions/Extensions/EfCoreDataSeedingExtensions.cs 85.71% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #283      +/-   ##
==========================================
- Coverage   84.61%   84.40%   -0.21%     
==========================================
  Files         159      159              
  Lines        3653     3656       +3     
  Branches      568      567       -1     
==========================================
- Hits         3091     3086       -5     
- Misses        405      412       +7     
- Partials      157      158       +1     
Flag Coverage Δ
unittests 84.40% <90.00%> (-0.21%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sonarqubecloud
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

📊 Code Coverage Report

| Metric | Coverage |
|--------|----------|
| **Line Coverage** | 87.6% |
| **Branch Coverage** | 82% |
| **Method Coverage** | 86% |

**Lines:** 3204/undefined covered
**Branches:** 1216/undefined covered

📈 [View Full Coverage Report](https://github.com/baoduy/DKNet/actions/runs/23635646534)

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