Difference between revisions of "TUnit"
(→Tutorials) |
(→Tutorials) |
||
| Line 18: | Line 18: | ||
** [[suite.properties]] | ** [[suite.properties]] | ||
** [[tunit.xml]] | ** [[tunit.xml]] | ||
| − | * [[ | + | * [[Single-Node Unit Testing]] |
| − | * [[ | + | ** [[Your First Test]] |
| − | * [[ | + | ** [[State Interface Test]] |
| + | ** [[Module Isolation Testing]] | ||
| + | ** [[Characterization Testing with Statistics]] | ||
| + | ** [[Applying suite.properties Rules]] | ||
* [[Multi-Node Unit Testing]] | * [[Multi-Node Unit Testing]] | ||
* [[Advanced Build Options]] | * [[Advanced Build Options]] | ||
Revision as of 10:15, 11 January 2008
TUnit is a unit testing framework geared for TinyOS and sensor networks. The philosophy surrounding the design of TUnit stems from years of accepted industry standard testing in other languages. TUnit is used daily in TinyOS Test Driven Development, decreasing the time spent manually testing and debugging software by literally hundreds of man-hours.
Open Source Testing
The TUnit unit testing framework is available open source to be used both publicly and privately.
Unit tests can be contributed by the public to the public automated unit testing system in tinyos-2.x-contrib/tests. These tests are automatically checked out and executed on several dedicated mote hardware platforms. Results and lava lamp status indicators are available live at http://www.lavalampmotemasters.com.
Privately, any group can run TUnit standalone or as an automated process in their own team development environment.
Tutorials
- How TUnit Works
- Setting up TUnit
- Single-Node Unit Testing
- Multi-Node Unit Testing
- Advanced Build Options
- Applying Ant
- Automation
Case Studies
External Links
- http://www.lavalampmotemasters.com TUnit Public Automated Unit Testing Main Site
- Three Rules of Test-Driven Development
- Six Rules of Unit Testing
- Big Visible Charts
- Testing, fun? Really?
- Introduction to Test-Driven Design
