SmartTests.Analyzer 1.4.1

There is a newer version of this package available.
See the version list below for details. 
dotnet add package SmartTests.Analyzer --version 1.4.1                

                    
                

            
NuGet\Install-Package SmartTests.Analyzer -Version 1.4.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="SmartTests.Analyzer" Version="1.4.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add SmartTests.Analyzer --version 1.4.1                

                    
                

            
#r "nuget: SmartTests.Analyzer, 1.4.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install SmartTests.Analyzer as a Cake Addin
#addin nuget:?package=SmartTests.Analyzer&version=1.4.1

// Install SmartTests.Analyzer as a Cake Tool
#tool nuget:?package=SmartTests.Analyzer&version=1.4.1

Smart Tests

Context

We all know how unit testing is important for non-regression of our softwares.

We all know that TDD (Test Driven Development) enables us to have better code and better management of the development process.

Fortunately, it is very easy to learn Testing Frameworks and to write unit tests technically.

BUT, it is very hard to think the good way to write unit test:

  1. How do I know how many tests to write?
  2. More, how do I know which cases we have to test?
  3. According to our Act code, it is very easy to assert that:
    1. A property changed, but how do we know if any other unexpected side effect occurred?
    2. A property changed, but how do we know if our test is still correct if anyone changed our Setup? For example, by giving the value you want to set as the initial value of your object?
  4. How can we show the expected effect of the Act code as we generally use hard coded values (because it is easier to code)?
  5. Finally, how can we do high level testing without multiple lines of code?

What is Smart Tests

Smart Tests is a library and a Visual Studio Analyzer to respond to all these questions... and more!

  1. The Act line of your test is instantly identifiable.
  2. You express your Act logical intent and the Analyzer will display all missing tests.
  3. You can use smarter assertions than the ones provided by usual Testing Frameworks as Smart Tests knows what is your Act and when it is run.
    1. You ensure that a PropertyChanged event is raised with only one line of code.
    2. You ensure that any event is raised with only one line of code.
    3. You ensure that an object didn't changed at all with only one line of code.
    4. You ensure that your property set is effective by checking its value after is not equal to its value before with only one line of code.
    5. You show each effect of your Act code relatively its previous value with only one line of code.

For now, it supports C# with NUnit, Xunit or MSTests.

However, it will very easy to add other Testing Frameworks (you only write a very simple sub-class).
You can also extend smart assertions in a very easily way.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.13.0 428 1/7/2022
1.12.0 583 6/28/2020
1.11.0 528 2/2/2020
1.10.0 592 10/6/2019
1.9.0 650 6/29/2019
1.8.0 729 4/28/2019
1.7.0 710 2/17/2019
1.6.0 1,043 12/15/2018
1.5.0 864 9/29/2018
1.4.2 944 7/31/2018
1.4.1 856 7/29/2018
1.4.0 907 7/28/2018
1.3.0 1,097 4/5/2018
1.1.2 1,030 12/16/2017
1.1.1 1,028 11/19/2017
1.1.0 1,035 11/11/2017
1.0.1 1,032 10/1/2017
1.0.0 1,068 9/30/2017

Criteria can now be Ranges of integer values.
This enables you to generate a random value within this range for your test and to be sure all ranges are tested (as expected for a criteria)