It supports the entire automated test development process, giving non-technical people the ability to design automated test cases. After they are created by TA engineers, the machine code associated with test cases in QA Craft for Jira® and the ability to manage TA from QA Craft for Jira® are created.
Each structure can be switched to the automatic test handling mode, allowing manual testers without programming skills to select test cases for automatic execution, run automated tests and finally receive an easy-to-read report presenting the test results.
There is no need to use repository templates. Based on of any structure, you can create another one, deciding which parts of it are to be cloned. It is also possible to create a structure consisting of a combination of copies created based on of several different structures, or their selected fragments.
QA Craft for Jira® is a tool created for handling large projects. We know what we are talking about, because we check it in our projects. They are not impressed by structures consisting of tens of thousands of test cases. Their service remains unaffected by the QA Craft for Jira® responsiveness.
Our import (from Testlink and Excel – that is basically everything) can deal with very large repositories. We tested it personally – the original version at some point stopped working so we got down to work – the current version works nice and dandy.
We’re not locked out by one Jira project. We can spread our test structure across multiple Jira projects, having overall metrics aggregated in one place.
Rivet Group is an official Atlassian Silver Partner
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.