Test case design techniques II: Blackbox

Contents:

• What is blackbox testing
• specifikation driven test
• equivalence classes, boundary value analysis 
• Test case implementation
• Integration Test

Litteratur

1. Pressman: Software Engineering: A Practitioners Approach -- European adaptation, 5ed. Kapitel 17.0-17.5: "Software Testing Techniques", side 448--464 (essential)
2. Pressman: Software Engineering: A Practitioners Approach -- European adaptation, 5ed. Kapitel 18:  "Software Testing Strategies", side 465--490 (essential)
3. [JUnit] JUnit Test Infected: Programmers Love Writing Tests
4. [fow07] Martin Fowler, Mocks Aren't Stubs
5. [Jef01] What is Extreme Programming
6. [CUNIT guide] Cunit User's Guide

Øvelser 

For these exercises you need to download the following zip file. A samle C-unit test case and VisualStudio workspace is located in classictest/EX3/GCD. Similar C-unit test case and makefile for Linux/GCC is located in classictest/EX3/GCD/GNU-GCD

1. Test case implementation in CUnit

2. Triangle Classification: A somewhat larger example is provided by the triangleClassification DEMO (VISUAL Studio) showing how several program compoenets can be tested and structured in several test  suites. Study the example and extend this with your own test cases,

Note if you use Windows+MinGW toolchain: 

It should run both on Linux and Windows provided that gcc and
make are installed (make on Linux and mingw32-make on Windows).

However, I could not force mingw32-make to detect the CUnit installation
in current directory, so it might be neccessary to run it with CU_HOME
parameter, like:
mingw32-make CU_HOME=CUnit-2.1-0-Windows

There's also CUnit-2.1-0-Linux with headers and libs which are detected
automatically on Linux. Although most distributions (Debian, Ubuntu,
Gentoo, RedHat) have CUnit natively it can be difficult to get it from
sf.net.