Instead, it loads those library assemblies
when it is executed. The referenced libraries must be available when the application
is compiled, and again when it is executed.1
This concludes our description of the remote instrument software. Now we can
describe our testing and analysis.
2.6 Unit testing
We begin our testing and analysis with unit testing. Testing checks software by
executing it. The software that is tested is called the implementation under test
(IUT). Different kinds of testing can be distinguished by the amount of software
that is included in the IUT. System testing executes entire applications, such as our
Logger or Monitor programs. Unit testing executes some of the parts, or units, from
which applications are built. In C#, the units are classes or other types. When we
are doing unit testing in the .NET framework, the IUT is a library (or libraries),
such as our Client and Server libraries. Creating and running unit tests require
familiarity with the source code and access to the same files and tools that the
developers use. Typically, unit testing is done by the same developers who write the
code.
For this example we use the NUnit testing tool, the .NET member of the xUnit
family that also includes JUnit (for Java), CppUnit (for C++), and several others.2
NUnit provides a library for writing tests, which defines several attributes and
assertions.
Pages:
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55