Lab Reduction is a companion web based tool to Data Reduction except that it operates on real test data rather than simulated test data. The data reduction is performed in real time as the test executes. Anyone on the network can view the test results in real time during the testing.
where all [fields] are optional and [blank] or [-] is default or are set as follows:
| filename.txt | Is the test file name, the default is testlog.txt. The report name is derived from this file name. The default report name is testlog.html. When entering a file name the .txt extension must be used (e.g. AAAa.txt, AAAb.txt). |
| delayinsecs | The script executes 100 times before ending, this is the delay between executions, the default is 20 seconds. |
| TocCor | If set to [y] correlates the log events to requirements. |
| TocCov | If set to [y] shows which requirements were addressed and which requirements were not addressed by the test results. |
| LabData | If set to [y] shows the raw test data. |
| LeFind | If set to [y] shows the log events that were found. The default is [y]. |
| LeNoFind | If set to [y] shows the log events NOT found in these test results. |
| Results | If set to [y] shows the test results correlated to the original log events. The deafult is [y]. |
| CPC | If set to [all], [red], or [a cpc] shows req's satisfied and NOT satisfied by these test results. |
| Filter | If set to [y], filters items containing certain words from the reports. The deafult is [y]. |
The file containing the test results is automatically updated by the BOOT application for some test cases. In all other BOOT and RED test cases the file is manually updated by the testers by either copying log events from the emulator window or entering log events based on emulator profile points. Using appropriate file naming conventions, parallel testing can be performed.
This application requires the inclusion of a special file (translate.dat) that is created by the logevent application and stored with the instrumentation analysis results. This file translates the log event codes to the original english equivalents. It also requires a version of the TOC (s_toc.dat) to correlate the TOC requirements with the lab test results.
If the results appear to be reasonable, copy and paste them into the test procedures. They will form the factory template that will be used during formal testing.
As part of an offline analysis, use the IAT reports and software source to locate the test result log events. Examine the software and look for potential missing log events or wrong long events. This is a final examination to confirm that the test results are as expected.
For dry run, create a single complete test results report following the sequence that is expected during formal test. Use these dry run test results to support the formal test.
At the conclusion of all the DRY RUN tests enable the log events found, log events not found, requirements correlation, and requirements coverage reports. Look for log events and requirements that were not captured during the all the test activity. If needed, create new tests to capture the missing requirements.
| Analysis Reports | Script Option | Comment |
| Func Call Seq | Design | This report shows the file and function calling sequence. It is read from top to bottom, left to right. |
| Test Comments | Comments | Summary of the comments entered by testers into the test file. |
| PUIs Verified | Comments | The list of PUIs verified in this test sequence. Use it in the filter service to compared different test sequences. |
| Req Coverage | Comments | This is a list of PUIs and the number of times the PUI was encountered in a log event with this test sequence. Use this to gain confidence in the test coverage. For example, a PUI that has been hit 50 times was probably the result of slightly different code paths. |