Do you want to radically simplify writing unit tests for your .NET-driven applications? Do you want to facilitate their maintenance? Do you want to discover the missing tests right from compilation?
Context
Unit test coding is now an acknowledged practice for improved development quality. First unit tests tools were easy to use, which helps make them popular.
Nevertheless, as the complexity of the software system increases, so does the complexity of unit tests. It is therefore important to simplify as much as possible their coding (using less code, and code in a more natural way) without sacrificing the multiple needs of developers.
Visual T#
Visual T# has been developed to simplify the design and the coding of unit tests for Microsoft.NET....
because it is more important to concentrate first on the objective of the test than the class under test. The tests are then more sturdy to changes.
Furthermore, when the number of tests increase, the relationships between the tests and the classes under test become more complex (What is being tested? What tests what? Which are the missing tests?) The development environment must thus provide different navigation strategies from one to another, add missing tests...
errormessage <string-expression>;
assert false errormessage <string-expression>;