How to write clear and robust unit tests: the dos and don'ts

• Audacia.Random

  1 4 3.1 C#

  Random data generation library

  

This point doesn't prohibit you from using randomised information, and Audacia even have an open-source repo of extension methods to help generate randomised information, so long as you're randomising information that has no effect on the outcome of the test.

• Roslynator

  17 2,972 9.3 C#

  Roslynator is a set of code analysis tools for C#, powered by Roslyn.

  

The reason I say 'similar' above is that though you may treat it as production code, there are some things in the nature of writing tests that may require different coding standard to be enforced. A good example of this is the RCS1046 analyzer, enforcing names of asynchronous methods to be suffixed with 'Async'; in this case it would be acceptable to override this rule (with an .editorconfig for example) so that you're method name continues to describe the behaviour of the application, and we don't have tests named like public async Task My_descriptive_method_name_async().

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project