SmartTests 1.11.0

SmartTests enables you to write Smarter unit tests, wether you use NUnit, Xunit or MSTests.

It is best to install SmartTests.Analyzer and SmartTests.Extension so that missing tests will be displayed.

They are Smart in the sense that:
   1. The Act line of your test is instantly identifiable.
   2. You express your Act logical intent and the optional 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.
       a. You ensure that a PropertyChanged event is raised with only one line of code.
       b. You ensure that any event is raised with only one line of code.
       c. You ensure that an object didn't changed at all with only one line of code.
       d. 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.
       e. You show each effect of your Act code relatively to its previous value with only one line of code.

Install-Package SmartTests -Version 1.11.0
dotnet add package SmartTests --version 1.11.0
<PackageReference Include="SmartTests" Version="1.11.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add SmartTests --version 1.11.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

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.

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.

Release Notes

A brand new [example project](https://github.com/LudovicDubois/SmartTests/tree/master/Examples) with lots of explanations. Learn how to maximize Smart Tests usage.

Many enhancements:

- [`Throw`](Assertions/throw.md) Smart Assertion exist now. This enables you to ensure the expected exception is thrown and following Smart Assertions are done.
- When an exception is thrown somewhere, we try to run all the `AfterAct` methods for which the `BeforeAct` method was called. However, the first exception is reported.
- [`NotChangedExcept()`](Assertions/notchanged.md#NotChangedExceptAct()) Smart Assertion method is renamed `NotChangedExceptAct` to better reflect what is excepted.
- [`Optional`](Criteria/Optional.md) criteria added, with two values: `Present` and `Absent`.
- Act Result is now accessible from `Act<T>.Result` property. Making it accessible from within the Smart Assertion implementations.

And some bug fixes:

- `NotChangedAssertion` do not try to save/verify indexers.
- No need to specify a Property Name when testing `NotRaised_PropertyChanged`.
- Random generators for floating point numbers have better values, but is no more well distributed.

This package is not used by any popular GitHub repositories.

Version History

Version Downloads Last updated
1.11.0 79 2/2/2020
1.10.0 106 10/6/2019
1.9.0 139 6/29/2019
1.8.0 160 4/28/2019
1.7.0 158 2/17/2019
1.6.0 394 12/15/2018
1.5.0 201 9/29/2018
1.4.2 260 7/31/2018
1.4.1 257 7/29/2018
1.4.0 251 7/28/2018
1.3.0 333 4/5/2018
1.1.2 379 12/16/2017
1.1.0 389 11/11/2017
1.0.1 339 10/1/2017
1.0.0 379 9/30/2017