Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DD Test Instructions"
m |
m |
||
| Line 5: | Line 5: | ||
== DSF SDK Testing Procedure == | == DSF SDK Testing Procedure == | ||
| − | See 'GDB Integration Testing Procedure' | + | See the ''GDB Integration Testing Procedure''. |
The DSF SDK provides a set of service APIs which a debugger integration must implement and a set of UI components which exercise those service APIs. Hence, the SDK features cannot be tested without a debugger integration which implements the services APIs. Currently the only such implementation available is the GDB debugger integration. This is not ideal, because GDB does not implement all the service features that are possible, but there is currently no alternative. To address this, we are planning to create a second reference implementation based on an example PDA debugger, which we can easily extend to excercise all the services and thus allow us to test all the DSF UI. | The DSF SDK provides a set of service APIs which a debugger integration must implement and a set of UI components which exercise those service APIs. Hence, the SDK features cannot be tested without a debugger integration which implements the services APIs. Currently the only such implementation available is the GDB debugger integration. This is not ideal, because GDB does not implement all the service features that are possible, but there is currently no alternative. To address this, we are planning to create a second reference implementation based on an example PDA debugger, which we can easily extend to excercise all the services and thus allow us to test all the DSF UI. | ||
| Line 37: | Line 37: | ||
== Traditional Memory Rendering Testing Procedure == | == Traditional Memory Rendering Testing Procedure == | ||
| − | Follow test instructions for 'GDB Integration Testing Procedure'. In Step 2, also install the 'Traditional Memory Rendering' feature. | + | Follow test instructions for ''GDB Integration Testing Procedure''. In Step 2, also install the ''Traditional Memory Rendering'' feature. |
Revision as of 01:25, 12 December 2007
Nav: DSDP/DD | DSDP/DD/Testing | DD Test Instructions | DD Known Issues and Workarounds | DD Manual Test Plan
DD Project consists of several features that are have different install procedures and can be tested independently of each other.
Contents
DSF SDK Testing Procedure
See the GDB Integration Testing Procedure.
The DSF SDK provides a set of service APIs which a debugger integration must implement and a set of UI components which exercise those service APIs. Hence, the SDK features cannot be tested without a debugger integration which implements the services APIs. Currently the only such implementation available is the GDB debugger integration. This is not ideal, because GDB does not implement all the service features that are possible, but there is currently no alternative. To address this, we are planning to create a second reference implementation based on an example PDA debugger, which we can easily extend to excercise all the services and thus allow us to test all the DSF UI.
GDB Integration Testing Procedure
Step 1: Download Prerequisites
- Eclipse 3.4 Platform Downloads - use the "SDK" bundle
- CDT 5.0 C/C++ IDE
Step 2: Download and install DSF and GDB
Step 3: Record your test environment
- We're most interested in the OS name and version and JVM version. Record this information in the test matrix.
- If need be In Eclipse, choose Help > About Eclipse SDK, press Configuration Details and look for the following lines:
- Line ~7: eclipse.buildId=I20071101-2000
- Line ~47: java.runtime.version=1.5.0_11-b03
- Line ~77: os.name=Linux
- Line ~78: os.version=2.6.20-16-generic
Step 4: Basic sanity test
TODO
Step 5: Test assignment
Following the test matrix, perform assigned tests.
IP-XACT Editor Testing Procedure
TODO
Traditional Memory Rendering Testing Procedure
Follow test instructions for GDB Integration Testing Procedure. In Step 2, also install the Traditional Memory Rendering feature.