Ticket #1366 (closed enhancement: fixed)
3d party QA software integration for Testing Tools
| Reported by: | Jani Laakso | Owned by: | Jani Laakso |
|---|---|---|---|
| Priority: | undefined | Milestone: | Testing Tools 1.0 |
| Component: | Testing Tools | Version: | |
| Keywords: | Cc: | joonas.lehtinen@…, ville.ingman@…, jouni.koivuviita@… | |
| Known Issue description: | |||
| Hours estimate: | 14 | Deadline (dd.mm.yyyy): | |
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | yes | Contract: | |
Description
Customers have their own QA software such as Caliber (VM-Data has this), Cruise Control (-removed- * asks for this integration *) or even ANT / Maven.
Offer clean, simple and documented API for integration to other systems. It involves events and few helper commands
Events such as
- Test case added, modified, deleted
- Test case results received
- Task started, finished
- Testing host is OK / down
Commands could be such as
- Make HTTP GET (Java has this, sample is enough)
- Send email notification (we already got this implementation on TT Server)
- Make System Process call: a'k'a execute any platform specific exe/script (Java has this, sample is enough)
Helper commands (no JDBC schema understanding is required)
- Get all test case ID's for suite X
- Get all test case results for test case X
Few simple HTTP GET REST API's might get handy (no authentication required)
- execute task X, returns task run ID
- print test case result IDs for given task run ID
- print test case result for given test case result ID
(If configuration or datastore is required)
- use same database
- or even through config (commons class is excellent for simple / complex configuration files), editable by text editor
Rationality why I am suggesting integration API and not strict integration to product X,Y,Z:
- customers can do their integration itself based on their environment: QA software, internal processes.
- This is a high end "enterprise" feature and in any case would require considerable amount of configuration and most likely even TT Server tailoring.
- Much later we may ask for customer created module and ask if we can integrate it to our product even better (if real business reason exists)
Opposite alternative is to do strict tailored integration to every specific system ensuring that "it just works" without too much of configuration. Requires multiple times more implementation and testing to get it right..
