Image Processing Reference
In-Depth Information
Build 213
Build 111
30°C
30°C
Build 1
Low battery
Full battery
15°C
Half battery
0°C
0°C
Low battery
Full battery
Resource configuration
e.g., battery levels
FIGURE .
Environment and resource configuration can be controlled for automated, continuous testing of
regression builds.
11.4.2 Architecture Overview
As depicted in Figure ., the test and instrumentation architecture is composed of three basic
components: a software repository, an infrastructure for continuous integration (CI), and a testing
infrastructure. he software repository provides a central location for all software under development
and associated tests. It allows to keep track of the development progress and allows interaction of
multiple users.
The core of the testing architecture is the infrastructure for CI. While CI is an established method
and tool commonly used in enterprise software engineering [], we propose to integrate it with a
specialized testing infrastructure to account for the peculiarities of WSN development—execution
on a real embedded target and in a distributed testbed environment [,] with tools for hardware
testing and stimulation. he CI server regularly checks for changes in the project software repository
and upon detection of a change initiates a clean checkout and then builds the project. he extension
with a testing infrastructure allows to deploy and execute the software under test directly on the
specific hardware platform it is being designed for. he tight integration with the test infrastructure
allows to monitor the test and provides detailed information about functional and physical details
of the execution on real target nodes. All data monitored during the test is collected and logged into
a central database referencing the exact software version in the repository that was used to generate
therespectiveinstance.
Inthefollowingwewillprovidethedetailsonthebuildingblocksusedinourtestingarchitecture
with a special focus on the integration of the physical test, i.e., the test on real motes in a real envi-
ronment. The mechanics and equipment used in our prototypical setup is briefly explained in the
following.
11.4.3 Continuous Integration
CI [] is a methodology, which promotes frequent integration, i.e., after each code check-in,
in order to provide rapid feedback to developers. This facilitates identifying software defects,
