{"id":331,"date":"2017-01-26T18:56:17","date_gmt":"2017-01-26T18:56:17","guid":{"rendered":"http:\/\/eitzen.at\/?page_id=331"},"modified":"2017-02-14T19:23:43","modified_gmt":"2017-02-14T19:23:43","slug":"jitest-admin-manual","status":"publish","type":"page","link":"https:\/\/eitzen.at\/index.php\/jitest-admin-manual\/","title":{"rendered":"JiTest Administration Manual"},"content":{"rendered":"

JiTest Administration\u00a0Manual<\/h1>\n

for JiTest v1.7, V2.0<\/h2>\n

\"jitest-logo\"<\/p>\n

(v 1.7.0, 170126)<\/p>\n

Index<\/h2>\n
    \n
  1. Overview of JiTest’s issue types<\/a><\/li>\n
  2. How to create a new JiTest project<\/a><\/li>\n
  3. How to\u00a0add JiTest to an existing SCRUM \/ Software project<\/a><\/li>\n
  4. How to add JiTest to other projects<\/a><\/li>\n
  5. Internal structure \/ linking of JiTest issues<\/a><\/li>\n
  6. REST API of JiTest<\/a><\/li>\n<\/ol>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    Overview<\/h2>\n

    JiTest introduces a set of new test specific issue types to JIRA<\/p>\n

    \u00a0JiTest is the issue type to\u00a0use to define test cases<\/p>\n

    \"\"\u00a0JiTestsuite is the issue type to group test cases into groups and define a logical structure<\/p>\n

    \"\"\u00a0JiTestplan allows to define a set of test case or suites that should be executed in a test run together<\/p>\n

    \"\"\u00a0JiTestexecution stores the results of\u00a0running a test case\u00a0within the execution of a specific test plan.<\/p>\n

    \u00a0JiTestreports are\u00a0created when a test plan gets executed at a specific point in time and contains references to all execution issues.<\/p>\n

     <\/p>\n

    Please note that for Plans to be executable you need to have Version\/Releases defined within your project<\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    How to create a new JiTest project<\/h2>\n

    \"admin-screen01\"If your software development process asks for a separate project to be created for managing test cases, suites, plans, executions and reports than you can take the short cut and create a new project using the top navigation JiTest menu drop down:<\/p>\n

    Note that administration rights are required for this operation to be available.<\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    How to\u00a0add JiTest to an existing SCRUM \/ Software project<\/h2>\n

    First you need to add all JiTest issue types<\/strong> to your project by going to:<\/p>\n

    Admin \u2192 Projects\u00a0\u2192 “Your Project”\u00a0\u2192 Issue Types (in the left sidebar)\u00a0\u2192 Edit\u00a0\u2192 Add all (JiTest issue types)<\/p>\n

    In order to be able to work with JiTest you need to add two more fields to the default issue screen<\/strong>:<\/p>\n

    Admin\u00a0\u2192 Issues\u00a0\u2192 Screens (in the left sidebar)\u00a0\u2192 SCRUM default issue screen\u00a0\u2192 add JiTestParentSuite<\/strong> and Affects Version<\/strong><\/p>\n

    Voila your team can start using JiTest within your existing project<\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    How to add JiTest to other projects<\/h2>\n

    It is fairly the same approach as for SCRUM or software projects with the addition that you must also add\/create a Bug issue type<\/strong> so that bugs can be reported via the executions issue page and create a new issue type called “Story” which should be used as requirement issue, test cas4es and plans can be linked to, via JiTest’s custom field “JiTRequirement”.<\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    Internal structure \/ linking of JiTest issues<\/h2>\n

    The picture below\u00a0shows the internal linking and custom fields used by JiTest to ensure consistency between the different issue types.<\/p>\n

    \"IssuesNCustomFieldsv2\"<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    REST\u00a0API of JiTest<\/h2>\n

    \"\"JiTest also provides a sophisticated REST\u00a0API to allow automated tests to be run and results being imported to JIRA JiTest projects. On Request we can provide you with a preliminary Swagger YAML file documenting all the endpoints and parameters used. Alternatively you can check out our online Rest API documentation<\/a>\u00a0based on worlds best Swagger tool.<\/p>\n

    JiTest’s REST\u00a0API is quite slim as\u00a0per design JiTest makes outermost usage of JIRA’s features wherever reasonable and possible. Thus creating and modifying JiTest issues can be done with normal JIRA REST\u00a0API. For comfort reasons we have added some more methods that allow to deal with test management actions more easily.<\/p>\n","protected":false},"excerpt":{"rendered":"

    JiTest Administration\u00a0Manual for JiTest v1.7, V2.0 (v 1.7.0, 170126) Index Overview of JiTest’s issue types How to create a new JiTest project How to\u00a0add JiTest to an existing SCRUM \/ Software project How to add JiTest to other projects Internal structure \/ linking of JiTest issues REST API of JiTest           Read more about JiTest Administration Manual<\/span>[…]<\/a><\/p>\n","protected":false},"author":1,"featured_media":223,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-331","page","type-page","status-publish","has-post-thumbnail","hentry"],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/P88Djt-5l","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/pages\/331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/comments?post=331"}],"version-history":[{"count":12,"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/pages\/331\/revisions"}],"predecessor-version":[{"id":369,"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/pages\/331\/revisions\/369"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/media\/223"}],"wp:attachment":[{"href":"https:\/\/eitzen.at\/index.php\/wp-json\/wp\/v2\/media?parent=331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}