Difference between revisions of "TUnit"
| Line 11: | Line 11: | ||
==Tutorials== | ==Tutorials== | ||
| − | |||
* [[How TUnit Works]] | * [[How TUnit Works]] | ||
** [[TUnit Philosophy]] | ** [[TUnit Philosophy]] | ||
** [[TUnit Test Flow]] | ** [[TUnit Test Flow]] | ||
** [[TUnit Assertions]] | ** [[TUnit Assertions]] | ||
| + | * [[Setting up TUnit]] | ||
** [[suite.properties]] | ** [[suite.properties]] | ||
** [[tunit.xml]] | ** [[tunit.xml]] | ||
Revision as of 18:13, 20 December 2007
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 spend 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
- Basic Single-Node Unit Test
- Advanced Single-node Unit Test
- Applying Ant
- Graphing Statistics
- Multi-Node Unit Testing
- Advanced Build Options
- 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
