TUnit

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
  • TUnit Philosophy
  • TUnit Test Flow
  • TUnit Assertions
• Setting up TUnit
  • suite.properties
  • tunit.xml
• Single-Node Unit Testing
  • Your First Test
  • Assertion Playground
  • State Interface Test
  • Characterization Testing with Statistics
• Multi-Node Unit Testing

Case Studies

• TestRxFifo
  • Isolation test testing the receive functionality of a radio stack from the rest of the system, allowing us to test edge cases observed by receiving various types of data in the software implemented RX FIFO.

• AckBehavior
  • Isolation test of the acknowledgements layer of the CC1100/CC2500 dual radio stack.

• CsmaBehavior
  • Isolation test of the CSMA layer of the CC2500 radio stack.

• TestTxThroughputNoCca
  • Integration Testing and Characterization: Collecting transmitter throughput statistics.

• TestMac
  • Multi-Node Testing and Characterization: Multiple statistics logging

• TestRxThroughputWithNoCca
  • Multi-Node Test: Upon receiving the first message from the Driving Node, the Supporting Node receiver starts a timer and accumulates received messages. When the timer fires, it reports performance and verifies enough packets got through.

• TestSwAcks
  • Multi-Node Test: An idle Supporting Node simply sends back an acknowledgment to the Driving Node.

• TestLplDefaultContinuousDelivery
  • Multi-Node Test: A Test Suite where 2 to 19 Supporting Nodes deliver LPL messages to a single listener, the Driving Node. At the end of a period of time, a dynamic threshold is calculated at +/- 10% and assertions are made against each of the nodes in the network to determine if the channel is being shared fairly amongst the multiple transmitters.

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