PRD for jenkins

Table of Contents:
-Jenkins Itself
-Jenkins vs.  Test Link
-Jenkins vs.  AEI Agile
-Jenkins vs.  Test Bed
-Jenkins vs.  Local Case Database

Jenkins Itself:
1. Capable of detecting test bed status on demand. (可以做，原生）
2. Capable of diagnosing health of test bed on demand.（可以做，原生）
3. Capable of reviewing test history.（可以做，原生）

Jenkins vs. Test Link:
1. Capable of fetching all automated test cases from certain project and test plan.（不清楚插件的原理，可以用脚本做）
2. Capable of returning test results to certain project and test plan.（不清楚testlink 插件的原理，可以用脚本做，半自动）

Jenkins vs. AEI Agile:
1. Capable of filing failed test cases to Agile under certain Agile issue as bugs.（不清楚插件的原理，可以用脚本做）
2. Capable of tagging failed test cases with Agile ID or Bug ID.（不清楚插件的原理，可以用脚本做）

Jenkins vs. Test Bed:
1. Capable of pushing test cases fetched from Test Link to certain test bed.（根据testlink 结果构建robotframework的case文件）
2. Capable of retrieving test progress from certain test bed and showing it on Jenkins.（不清楚插件原理，不知道如何做）
3. Capable of retrieving interim test results from certain test bed in process of test and showing it on Jenkins.（不清楚插件原理，不知道如何做）4. Capable of retrieving final test results from certain test bed after test completes and showing it on Jenkins.（这个是自带robotframework插件run完有结果）
5. Capable of triggering test bed to synchronise latest code from GIT server.（triggering test，有git插件，原理不清楚，要设置trigger条件）

Jenkins vs. Local Case Database:
1. Capable of fetching test cases from Test Link and updating Local Case Database accordingly.PRD（根据testlink 创建mapping关系。将结果写入prince的中间数据库当中。）