9b9e37bed2 | ||
---|---|---|
.vscode | ||
solutions | ||
src | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
LICENSE.txt | ||
README.md | ||
appveyor.yml | ||
build.cake | ||
build.cmd | ||
build.ps1 |
README.md
NUnit3 Test Demo
The Test Demo is primarily intended to be opened in the IDE for the purpose of viewing the visual treatment of various elements. For that reason, there are failures, warnings and ignored tests as well as successful ones.
As a secondary purpose, the demos can be run using command line VSTest, like in a CI, to ensure that the results under VSTest are as expected.
Usage
There are a set of solutions to be found under the folder 'solutions', diveded between 'VS2017' and 'VS2015'. There you find 'CSharpDemo' and 'NUnit3CoreTestDemo'. The first is .net framework 4.5, the latter is .net core 1.1.
Expected results
NUnit3CoreTestDemo
After opening the solution (no build), 66 tesst should be discovered. This comes from the source based discovery process in VS and has nothing to do with the adapter.
Structure
Each demo is represented by a VS solution containing a single project. This allows a single demo to be opened in the IDE.
The project and solution are in the same directory in order to make scripting simpler and all demos are organized at the top level by the version of Visual Studio used to create them.
Source code is common for all demos and is organized by the language supported.
ExpectXxxx Attributes
The Test Demo code includes definition of special attributes like ExpectPass
and ExpectFailure
for use on the tests. This allows the tester to group the tests by Traits and easily see that the outcome for each group of expectations is what it should be.
C++ Demo
The C++ version of the Demo includes a much smaller number of tests since certain features of NUnit are not directly accessible from C++. More tests may be added as we develop shims for those features.