ProtoTest.Core
1.1.4
dotnet add package ProtoTest.Core --version 1.1.4
NuGet\Install-Package ProtoTest.Core -Version 1.1.4
<PackageReference Include="ProtoTest.Core" Version="1.1.4" />
<PackageVersion Include="ProtoTest.Core" Version="1.1.4" />
<PackageReference Include="ProtoTest.Core" />
paket add ProtoTest.Core --version 1.1.4
#r "nuget: ProtoTest.Core, 1.1.4"
#:package ProtoTest.Core@1.1.4
#addin nuget:?package=ProtoTest.Core&version=1.1.4
#tool nuget:?package=ProtoTest.Core&version=1.1.4
ProtoTest.Core
This is the part every ProtoTest integration builds on.
Most test projects get this package through a runner adapter or another ProtoTest package. Install it directly when building an integration or runner adapter of your own:
dotnet add package ProtoTest.Core
Why does Core exist?
Without Core, every integration would manage setup, cleanup and tracing in its own way.
Core provides one host for the test run and one ProtoExecutionContext for each test. Integrations use that context for clients, typed contexts, resources and attachments.
It also owns the shared lifecycle. Setup, test execution and teardown can all be written to the same .prototrace file.
Learn more
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.Extensions.Configuration (>= 10.0.12)
- Microsoft.Extensions.Configuration.Abstractions (>= 10.0.12)
- Microsoft.Extensions.Configuration.Binder (>= 10.0.12)
- Microsoft.Extensions.DependencyInjection (>= 10.0.12)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.12)
-
net8.0
- Microsoft.Extensions.Configuration (>= 8.0.0)
- Microsoft.Extensions.Configuration.Abstractions (>= 8.0.0)
- Microsoft.Extensions.Configuration.Binder (>= 8.0.2)
- Microsoft.Extensions.DependencyInjection (>= 8.0.1)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.2)
-
net9.0
- Microsoft.Extensions.Configuration (>= 9.0.20)
- Microsoft.Extensions.Configuration.Abstractions (>= 9.0.20)
- Microsoft.Extensions.Configuration.Binder (>= 9.0.20)
- Microsoft.Extensions.DependencyInjection (>= 9.0.20)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 9.0.20)
NuGet packages (31)
Showing the top 5 NuGet packages that depend on ProtoTest.Core:
| Package | Downloads |
|---|---|
|
ProtoTest.Json
Shared JSON shape matching and value constraints for ProtoTest integrations. |
|
|
ProtoTest.Http
Shared HTTP foundations for ProtoTest protocol integrations. |
|
|
ProtoTest.Web
Backend-neutral, component-based web testing for ProtoTest. |
|
|
ProtoTest.Sql
A per-test database connection with transaction isolation and owned release for ProtoTest. |
|
|
ProtoTest.Messaging
Messaging integration for ProtoTest: publish and await messages with a predicate and timeout over a broker capability. |
GitHub repositories
This package is not used by any popular GitHub repositories.