Specifications

120
5.4 Software Test Procedure
The Breathalyzer system is will be sub divided into two different systems. The
control box unit and the hand held unit. There should be defined procedures in
order to test to see that the hardware and the software is producing the correct
values and data, as well as driving the correct display output at expected times.
A means by which this can be tested is with different software modules designed
for stressing the inputs and evaluating the output response for each particular
software routine. Since there are different software states, the module should be
inserted in different states to evaluate program operation in that particular state.
Examples of software routine testing include the ability to verify that LCD output
is identical to the values that were driven to its inputs by the software, correctly
measure specific input voltage levels from the ADC and digitally represent those
in software, and verify that packet data sent over the wireless infrastructure
arrives as intended.
The module called LCD_D will debug the display to see what values are being
transferred via bus to the display. The module will have an interrupt handler that
will allow the data to be interrupted mid transaction. The only way to check and
see if there is a interrupt is to debug the interrupt handler. There is a debug
handler that will be able to test to verify that the data is being sent or if the push
button has been push to interrupt the sample that will currently be taken. There is
another module that will determine the input and what values are being passed.
This module is called the Verify Input module. This module will identify the
correct input and deal with the input correctly.
These inputs are passed through the bus. The module that will test the bus lines
will be called line_d, and will have capabilities to determine which bus line is
high. This will take care of the procedure that will be on the hand held unit. The
hand held unit should be able to report to these modules the input and the output
that it sends and receives. Without an effective debugging mechanism there will
be no way to determine if the input is the same value that was given to the
MSP430. This is why it is crucial to verify that the data is coming out on the other
end. Figure 5.4-1 shows the debug modules connected to the specific devices.
This flow chart shows the description on how the developers will use module to
debug and test the inputs and outputs on the hand held unit.