auto-tester
1.0.62
dotnet tool install --global auto-tester --version 1.0.62
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest # if you are setting up this repo dotnet tool install --local auto-tester --version 1.0.62
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=auto-tester&version=1.0.62
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
nuke :add-package auto-tester --version 1.0.62
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
.NET Core global tool continuous test runner that monitors and runs only the tests affected.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. 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. |
| .NET Core | netcoreapp2.1 is compatible. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
| Version | Downloads | Last updated |
|---|---|---|
| 1.0.62 | 2,612 | 12/14/2018 |
| 1.0.61 | 2,204 | 12/12/2018 |
| 1.0.59 | 2,310 | 12/10/2018 |
| 1.0.58 | 2,123 | 12/9/2018 |
| 1.0.57 | 2,040 | 12/9/2018 |
| 1.0.56 | 2,041 | 12/8/2018 |
| 1.0.55 | 1,940 | 12/8/2018 |
| 1.0.54 | 2,061 | 12/8/2018 |
| 1.0.53 | 2,247 | 12/8/2018 |
| 1.0.52 | 2,157 | 12/8/2018 |
| 1.0.51 | 2,292 | 12/8/2018 |
| 1.0.50 | 2,004 | 12/8/2018 |
| 1.0.49 | 1,869 | 12/8/2018 |
| 1.0.48 | 2,038 | 12/7/2018 |
| 1.0.47 | 2,012 | 12/7/2018 |
| 1.0.46 | 1,844 | 12/7/2018 |
| 1.0.45 | 1,961 | 12/7/2018 |
| 1.0.44 | 1,750 | 12/7/2018 |
| 1.0.43 | 2,065 | 12/7/2018 |
| 1.0.42 | 2,096 | 12/7/2018 |
| 1.0.41 | 1,847 | 12/6/2018 |
| 1.0.40 | 1,786 | 12/6/2018 |
| 1.0.39 | 1,901 | 12/6/2018 |
| 1.0.38 | 1,767 | 12/6/2018 |
| 1.0.37 | 1,902 | 12/6/2018 |
| 1.0.35 | 1,994 | 12/6/2018 |
| 1.0.34 | 1,812 | 12/6/2018 |
| 1.0.33 | 1,867 | 12/6/2018 |
| 1.0.32 | 1,723 | 12/6/2018 |
Updates
* Option to run all tests (-a)
* [Beta] Use Roslyn to find affected tests (-r)
Import .NET Global tool
$ dotnet tool install --global auto-tester
In the root of your C# .NET Core project
$ auto-tester
It recursively monitors and runs only the affected tests from all the nested test projects. Whether you modify a test or code that is touched by one or more tests, this should detect and run them.