Previous:
Function Index
, Up:
Top
6 Concept Index
antimethodology
:
Introduction
benefits, developer
:
Introduction
compilation testing
:
Introduction
developer benefits
:
Introduction
example code
:
Introduction
interpretation testing
:
Introduction
parse testing
:
Introduction
regression testing
:
Introduction
release qualification
:
Introduction
source code control, improve
:
Introduction
testing, compilation
:
Introduction
testing, interpretation
:
Introduction
testing, parsing
:
Introduction
testing, regression
:
Introduction
unit tests
:
Introduction
XP
:
Introduction
Short Contents
1 Introduction
2 General API
3 C-Unit
4 Webliography
5 Function Index
6 Concept Index
Table of Contents
1 Introduction
1.1 What is a Unit Test?
1.2 Why should we use Unit Tests?
1.2.1 Benefits to Developers
1.2.2 Benefits to Consumers
1.3 How do you write a Unit Test?
1.4 How do you organize your Unit Tests?
1.4.1 Hand Coded Suites
1.4.2 Automatically Generated Suites
1.5 How do you run your Unit Tests?
1.5.1 Within GNU Automake Managed Sources
1.5.2 Within Aegis Managed Sources
1.6 How long should it take to run all my Unit Tests?
1.7 When are Unit Tests run?
1.7.1 As a Developer
1.7.2 As a Consumer
2 General API
2.1 Interaction with Source Building Tools
2.1.1 GNU Automake
2.1.2 Aegis
2.2 Data Structures
2.3 Function Calls and Macros
2.3.1 Test Setup
2.3.2 Assertions
3 C-Unit
3.1 Header Files and Library
3.1.1 Header Files
3.1.2 Library
3.1.3 Autoconf
3.2 Type Reference
3.3 Function and Macro Reference
3.4 Utilities
3.5 Self-Testing Proof
4 Webliography
5 Function Index
6 Concept Index