Scheduling integration for 3rd party tools (Ant, Perl or even Caliber..)

[Jani Laakso]

Starting test case through "Testing Host" requires single HTTP query, thats all.

Part 1: Simplest orchestration integration to other systems

This is more of documentation & testing than implementation task, but some implementation is suggested (see last two issues).

Definition: Orchestrator in this context is the scheduler which launches regression tests, e.g. ANT script, Perl script or even QA product itself such as Caliber. Testing Host worker, testing host machine which opens Firefox and starts execution of test against any Toolkit application. TT Server Testing Tools Server, where test cases and resulsts are stored.

• ISSUE: Orchestrator does not want to use SHA1 based security checks
  • SOLUTION: (Already supported) Add "skipsecuritychecks=1" to every Testing Host used
    • side effect: anyone can do anything on Testing Hosts
• ISSUE: Orchestrator may launch tests even if Testing Host is already executing an test
  • SOLUTION: (Already supported) client should query first from Testing Hosts if it's busy and skip execution if Testing Host is response is "I am currently executing an test"
  • BETTER SOLUTION: (Should be implemented) Testing Hosts denies concurrent execution
• ISSUE: Orchestrator must use akward HTTP URL's to launch test cases
  • SOLUTION: (Should be implemented): simplify GET parameters

Results are automatically send to TT server by Testing Hosts.

Part 2: Simplest test results integration to other systems

Use JDBC connection to query test case results.

• ISSUE: How to correlate executed test case (test run) to right test result
• SOLUTION: (Must be implemented): Test run id should be told back to Orchestrator when starting test execution so results are easier to query afterwards.

[Jani Laakso]

I'd advise ignoring this "enhancement", too hard to use..

See #1366