You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Unit Tests

The objective of unit tests is to test the functionality of a single module isolated from the system and other functional units.

  • Test functionality of single software unit or module
  • May require dependencies of other modules that come before in the compilation order
  • Shouldn't require to run ACS
  • Shouldn't depend on functional units / modules that come later in the compilation order

There are frameworks for the different programming languages and shell scripting. ACS comes with:

  • shunit: Shell (sh, bash, etc.) unit testing framework
  • unittest: Official Python unit testing module
  • jUnit: Java unit testing library
  • cppunit: C++ unit testing library

Besides these, each project is free to include their own unit testing libraries, packages, frameworks, etc.

Integration Tests

Integration tests go one step beyond, they allow to test functionality in the interactions of different functional units and can include using a partial or complete ACS runtime environment.

  • Test functionality of multiple software units or modules
  • Would probably require several dependencies from modules that come after in the compilation order or even that come from different projects
  • Can make use of ACS

TAT

  • No labels