TREMBLE technical manual

Next: 5.1.2 Hardware Testing Up: 5.1 Component Testing Previous: 5.1 Component Testing

5.1.1 Software Testing

The TREMBLE team members initially thought that we could get much of our coding done in the first ten weeks of the semester so that we could take that last several weeks to do testing of individual components followed by a sequence of integration tests (i.e. testing our interfaces). However, we severely underestimated the amount of time it took just to get components to work.

Although some components were individually tested with simulated data, much of our testing took place at the same time as integration. Error detection and correction was often the result of having a result show up somewhere (e.g. an error in the what was being displayed in Crossbow) and tracing it backwards to an error in a preceding subsystem (e.g. a computational error in Compass). In fact, many errors are only being found now since -- and could only be found because -- the entire TREMBLE system is in place. Thus, there is now a Known Bugs section included in the technical manual.


Next: 5.1.2 Hardware Testing Up: 5.1 Component Testing Previous: 5.1 Component Testing

author(s): Eric D. Baker
last update: 05 May 1999 6:51p by Eric D. Baker