Unit Testing

From Gcube Wiki
Revision as of 17:48, 15 January 2012 by Gabriele.giammatteo (Talk | contribs) (Created page with 'Unit testing is a testing methodology by which a software system is split in elementary units and each unit is tested in isolation and independently from other units. A unit coul…')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Unit testing is a testing methodology by which a software system is split in elementary units and each unit is tested in isolation and independently from other units. A unit could be an entire module, a class or a single method or procedure.

The ETICS build system gives the possibility of running automatically Junit Testsuites during the build process. The ETICSJunitPlugin (further explained here) is capable of finding and executing Junit Testsuites in gCube components home directories. Reports generated are published along with other build reports.


ETICSJunitPlugin is driven by following properties that developers can customize in ETICS configuration of their gCube component.


Please note that ETICS will only execute Testsuites found after the component's check out from the SVN. Therefore, developers are responsible for committing Testsuites in the source code repository along with their component's code.