in the software design portion of this document. All test procedure will test for the following: Software operates and handles any exceptions generated during operation time All function requirements meet defined standards Implementation design takes into account unusual operation modes Implementation does not produce any unintended results. 19.2 Test Environment The primary test environment to test software will be AVR Studio 5 Integrated Development Environment. The IDE features full support for developing and debugging embedded Atmel AVR applications with an embedded C compiler, assembler, and simulator. This was ran in a Windows XP-32 bit environment. Testing will be conducted at two levels, the first level will be tested by the primary developers, testing Functions as they are implemented. The second set of testing will be done by the entire development team for quality assurance and to perform redundancy testing of implementation, functionality, and overall implementation of COLLide-3 AVM, to ensure this product meets all design specifications. The secondary testing was done with the AVM module in hardware. This was done at the final stage of project development and only after all other milestones has been met, this is to catch any errors that may not be observable under simulation and to get a real world sample of what AVM will have to work in. 19.3 Stopping Criteria Testing procedures was done in an iterative fashion. Functionality essential to successful operation and required features were primary test procedures, secondary test procedures consisted of non-functional requirements as listed in software design. Stopping criteria can only be achieved by 100% completion of ALL primary test procedures. Requirements will be tested by Q&A testers each release version to ensure functionality and adherence to all obligations. All other test procedures will first be tested at the unit level by the developer. Once the implemented functionality has been validated by the developer it will undergo
of software for duration of 30 minutes to test continued operations of Space Ace. Test procedure Step Condition/Action Intended Results Fail Criteria 1. Software is initialized All functions are ready, and all data structures are initialized. Any noticeable deviation of software, or failure to initialize 2. Initialize UIM Software correctly sends and received data to UIM UIM does not recognize commands from or Micro fails to receive data 3. Accelerometer will be simulated Accumulator increments on positive signal from sensor Accumulator does not increment, or fails to process signal 4. 25 minutes of standby The software will remain running for 25 minutes Within those 25 minutes a software exception is generated or goes into unplanned state 5. Repeat of test The software will retested after 25 minute operation, all functions should still be operational Any function becomes or AVM becomes unresponsive. 19.4.1 Shows the test procedure steps Test Title: Experiment Start Test Objective: To test AVM experiment mode initializes all components. Test Description: The following actions will be tested:
AVM peripheral control AVM peripheral time constraints. Test Conditions: From the simulator, peripherals will be a emulated by having a method of inputting hard-coded test condition. In the physical test environment the actual peripherals will be present. Step Condition/Action Intended Results Fail Criteria 1. Software is initialized All functions are ready, and all data structures are initialized. Any noticeable deviation of software, or failure to initialize 2. Accelerometer is set to High Accumulator increments until experiment start condition is met Experiment Start isn’t reached. 3. LED is activated LED activates under default timing constraints LED does not turn on, or not under correct time 4. PWM is activated PWM operates under correct frequency and under default timing constraints PWM does not turn on, or not under correct time, or incorrect frequency 5. Camera is activated Camera activates under default timing constraints Camera does not respond or not on correct timing constraint 6. Experiment end time is reached All peripherals are turned off Any peripheral stays on, or are not properly shut down Table 19.4.2 Shows the test conditions Test Title: Protocol Networking Test Objective: To test AVM Ethernet and SATA protocol interface correctly with microcontroller Test Description: The following actions will be tested: