Distributed tests are typically slower (due to extra communication between remote components) and more complex than simple automated tests and should be used only when it’s not possible to write simple automated tests.
FIGURE 1-2 illustrates the Framework configuration for running CLDC and MIDP distributed tests. Distributed tests are currently not supported in CLDC (without MIDP). For CDC, the agent is started, downloads the tests via the communication channel, and executes them, without being restarted (a single agent runs from the beginning to the end of the test run). See “Testing Communications or Networking With Distributed Tests” on page 43 in Chapter 4 for information about writing distributed tests and distributed test execution.
FIGURE 1-2 Framework Configuration for Distributed Tests
PC or Workstation | Device |
JavaTest Harness
1getNextApp
2Application Bundle (agent + tests)
Execution |
| AMS | |
Server |
| ||
getNextTest | |||
| |||
4Test Name
|
|
| Send Test |
|
|
| |
Passive |
| Result | 9 |
|
| ||
|
|
|
| ||||
|
|
|
|
| |||
Agent |
|
|
|
|
| ||
|
|
|
|
|
| Agent | |
7 |
|
| |||||
|
|
| |||||
Test |
|
|
| ||||
|
|
|
|
| |||
|
| 8 |
|
|
| ||
|
|
|
|
| |||
|
| 5 | Check/Send |
| |||
|
|
| |||||
Messaging |
|
| Message |
| |||
|
|
|
| Tests | |||
Service | 6 | Get Message | |||||
| |||||||
|
|
| |||||
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
Diagram of the distributed test configuration.
Chapter 1 Introduction 11
