Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/OTE/Users Guide"
< OSEE
(→Output files) |
(→Test Source File) |
||
Line 31: | Line 31: | ||
==Test Source File== | ==Test Source File== | ||
− | + | *Test files are color/tool tip annotated with failures | |
− | + | ||
− | + | ||
==Tightly Integrated into the Open System Engineering Environment== | ==Tightly Integrated into the Open System Engineering Environment== | ||
<ul> | <ul> |
Revision as of 19:16, 7 May 2009
Contents
OSEE Test Environment (OTE)
Documentation
Test Environment Service
- Provides dynamic lookup of resources
- Provides both soft real-time and simulated capabilities
- Schedules periodic execution of models (simulation components)
- Supports user configurable number of simultaneous connections
- manages the I/O and testing resources
Fully automated testing
- Automated test point tally and rollup of pass/fail determination
- Functional Testing
- Simulated Environment (eases demand on limited test station resources)
- Tests (without modification of any kind) can be run in both soft real-time and simulated environments (simultaneously, if desired)
- Real-time messaging system that supports MIL-STD-1553 MUX, serial, wire, analog and digital discretes, and publish/subscribe Data Distribution Service (DDS)
- Unit Testing
- Java
- C++
- Automated Display Testing (ADT)
Interactive Testing (automated tests with user input)
Output files
- Output file in XML
- Interactive outfiles (user can navigate the out file)
- User selectable views of outfiles: normal, debug, and flat
- Direct linking of output file lines to source test lines
- Automatic correlation of a run-time test point to the test source line that generated it
- XML output file can be automatically transformed into any format
Test Source File
- Test files are color/tool tip annotated with failures
Tightly Integrated into the Open System Engineering Environment
- Utilizes OSEE Application Framework to provide bidirectional traceability between software requirements, application code, and tests
- Leverages Java Development Toolkit (JDT) and C/C++ Development Toolkit (CDT)
- Facilitates seamless flow between test development, debugging, execution, and result analysis
- Supports the execution of multiple simultaneous batches within a single workspace
- Built-in help system extended with test manger user guide
Test Manager GUI
- Consistent, clean interface for the control of unit and functional test in the real-time and simulated environments
- Test results streamed in real-time from test service to test manager
- Remote viewing and manipulation of test service
- Single/Batch run mode
- Enable/disable running of individual scripts in the run list
- Drag and drop test files into run list
- Integrated with code debugger
- Access to test and output files from the GUI
- Lists available test services that can be used to run test files
- Real-time display of test service usage information
Message GUI
- Monitor, manipulate and record real-time messaging data
- Common user interface supporting P/S, 1553, discrete, analog, serial
- Advanced regular-expression searching
- Import/Export view lists
- Remote attachment to message service
- Playback environment
- message recording playback environment that allows for the analysis of Ethernet and MUX recordings
- supports advanced debugging of the test environment using repeatable conditions
- investigate flight recordings