The most recent content from our members.
Support for NUnit and MSUnit are based on which API is supported, not which version of NUnit and MSUnit is supported. Please see the NUnitTests.pdf and the MSUnitTests.pdf files, located under the help folder of the dotTEST installation directory, to see a list of supported an unsupported API for your version of dotTEST,…
NUnit provides only a framework for execution of tests that the developer prepared manually. .TEST embraces and extends NUnit to provide automated test case generation. .TEST's execution engine also provides many other important features, such as coverage reporting, automatic error assignment and distribution, tracking of…
One of the important aspects of GUI applications is that they have event handlers. .TEST can generate NUnit test cases that have calls to the event handlers. The parameters for these handlers will be set to values that .TEST designs automatically. You may need to modify the parameters in some cases. .TEST ships with…
.TEST ships with some coding standards rules that help in making a multi-threaded program more robust. If you are running NUnit tests with a multi-threaded program, then .TEST handles exceptions thrown by threads other than the main test execution thread to the best extent possible and reports such violations as well.…
.Test and source control integrationHi, I need to integrate .Test in file check-in process , i.e to verify that the file are OK after check-out/check-in. The problem is that .Test works at .Test project level or at assembly level ( while nUnit works at file level, i.e nUnit test is written per single *.cs file) How i can…
It looks like you're new here. Sign in or register to get started.