1. Dispatcher IO TestlinkDispatcher TEEBEE Required TEEs XSLT 1. Testlink XML 3. Get Asset Build Id 6. Bee Build result* 8. Testlink XML 9. Tee specific input XML 10. Tee TL compliant results XML 11. Testlink compliant result XML 12. Write results to TL DB 4. Asset Build Id 5. Build Asset * 2. Get Build Info, BEEs, TEEs from TL xml Dispatcher Cache 7. Set Assets locations * Optional Step

2. Testlink-Dispatcher IO A TestSession request is issued from TestLink to the dispatcher. The request includes test data information in an XML file. The structure of the XML test data file is defined by Testlink’s export operation. The dispatcher copies the XML test data and sends a test session started message that contains a test session handle to the testlink staf client. The Dispatcher partially processes the XML test data file, and obtains the Build Information, BEEs and TEEs types required for this test session The dispatcher calls the appropriate BEEs to service the request. The dispatcher processes the BEEs results and calls the appropiate TEEs to service the request. The dispatcher processes the TEEs XML results and writes the results in the testlink database. The structure of the XML result file is defined by Testlink’s import operation.

3. For each BEE and asset associated with the BEE the dispatcher will: –Send a request to the resource manager for the BEE type specified. –Send a request to the BEE for the build id* of the software asset required. –Based on the build id* returned in 1 the dispatcher checks its cache to see if the software assets is present. If the software asset is not present the dispatcher continues with step IV; otherwise the dispatcher jumps to step VI. –Sends a build request to the BEE. –Once the BEE has serviced the request the dispatcher processes the BEE response* and copies the built asset from the BEE location to its local cache. –The location of the asset in the cache is saved to be used later in the Dispatcher-TEE data flow. * See Build Execution Engines (BEE) Interface design artifact for message syntaxBuild Execution Engines (BEE) Interface Dispatcher-BEE IO

4. Dispatcher-TEE IO For each TEE type required by the test session the dispatcher will performed: –A request to the resource manager for a tee of the type needed. –For each asset type specified in the test session request the dispatcher will set a staf {auto/sw_asset/ } variable in the tee that points to the location (step VI in Dispatcher-BEE) in the dispatchers cache where the binaries built by a BEE for this element can be found. –Filter the XML test data file, based on the TEE requirements. The result of the filtering operation is an XML file that is compliant with Testlink’s export operation and only contains the test cases that can be executed by that TEE. –The dispatcher sends a Run* request to the TEE granted by the resource manager. *See Test Execution Engines (TEE) Interface design artifact for message syntaxTest Execution Engines (TEE) Interface

5. –The TEE processes the request and responds to the dispatcher using a STAF Map class that contains a “resultsfile” entry which points to the tee results xml file. The structure of the tee results XML file is specified by Testlink’s import operation. –The dispatcher uses a Staf service to write back results to TestLink and sends a test session completed message to the testlink staf client. Dispatcher-TEE IO