Tux.Net Architecture (Windows Embedded CE 6.0)
1/6/2010
Tux.Net is a managed executable that launches tests cases that live in a managed assembly. When run from a device with command line options or a configuration file, Tux.Net will locate the specified test suites and test cases inside an assembly and execute them. It has many options for specifying what tests or suites will be run, and how they should be run (for instance, should they be shuffled or repeated). Tux.Net looks for classes inheriting the TestSuite class and methods with the TestCase attribute to know what it can run, and it can run any assembly meeting these requirements.
Tux.Net test suites are C# classes that inherit from a class called TestSuite. The tests themselves are C# methods within these classes decorated with an attribute that designates them as test cases. Tests are typically organized into test suites by feature.
You can use Tux.Net to perform the following types of tests:
- Testing managed APIs
When shipping APIs of any kind, testers need to create structured test cases to validate these APIs against specification and shipping criteria. Tux.Net is ideal for creating test cases for managed code APIs.
- Unit-testing managed code
Tux.Net provides a framework for managed test code that is ideal for unit testing managed production code. Production assemblies can contain actual test cases, or test cases could be placed in a separate assembly. The Tux.Net core can be hosted in any managed process as well.
- C# test code development
If you are leveraging managed test libraries such as Datk, Tux.Net is the ideal vehicle for hosting your test cases. You can even use Tux.Net to test native code by using P/Invoke. However, if testing Native code is a principle scenario, it is usually better to use Tux rather than Tux.Net.