The purpose of the test plan is to provide an overall test planning and test management view of your test initiative. You can customize the test plan’s fields to track: Scope, Risks, Strategy, Pass/Fail Criteria, Test Bed and so on. If that makes sense, you can also track test execution cycles by associating test cycles to a test plan. By doing so, you will be able to track test cycles from the test plan perspective. In addition to that, there are several reports you can filter by test plan (which will aggregate all stats/results from the child test cycles linked to the test plan). Test plans are not required for regular TM4J usage. Learn more: Waterfall Development with Test Plans.
Yes, TM4J is tightly integrated with Jira so you can link test cases, test cycles and test plans to any Issue type in Jira. TM4J also offers traceability reports to track traceability and coverage under the 'Legacy reports' section. We will be introducing all reports in this section within the new reporting section for TM4J in the coming months.
Yes, basic versioning functionality is available to test cases. Version control is enabled by default and allow teams to collaborate and manage multiple versions of test cases in parallel while keeping data integrity and providing an audit history of changes. Versions can be viewed and compared for audit purposes. Learn more: Creating New Test Case Versions.
The order of test cases within a test cycle can be set from the 'Test Cases' tab under the test cycle view. Here, you can drag and drop test cases into the preferred order. This is how they will be shown from the test player.
TM4J does not currently support the 'test suite/set' functionality, which allows you to organize groups of test cases outside of a test cycle, though you can use folders to organise your test cases at this stage.
Yes, call to test is supported natively. Instead of duplicating or copying and pasting test cases or steps, you should focus on breaking down them into smaller, reusable pieces and then recombines these tests to achieve larger end-to-end testing scenarios. Test cases can be referenced (called) in other test cases to create nested reusable structures. Learn more: Reusing Test Data with Call to Test.
TM4J Cloud does not currently support parameters to be used within test cases. This feature will be introduced in the near future.
Yes, with TM4J, small and agile teams can manage testing in a lightweight and straightforward fashion. You can create and link test cases or acceptance tests to user stories/bugs and create test cycles directly from the issue screen in Jira or the kanban board.
TM4J Cloud does not currently support test data to be used within test cases. This feature will be introduced in the near future.
TM4J Cloud does not currently support BDD type test cases. This feature will be introduced in the near future.
With our REST API, which is free when you install Test Management for Jira, you can access testing data from Jira and carry out a variety of useful tasks, such as migrating from another tool by importing your data, integrating with automated testing tools, and more. By using the API, you can publish automated test-execution results to Test Management for Jira and use our powerful reporting to view metrics on your entire testing process. The API is HTTP-based and can be used from any framework, programming language, or tool. Learn more: REST API.
Yes, TM4J supports custom fields for test cases, test cycles and test plans. Learn more: Configuring TM4J.
Yes, TM4J offers a range of cross-project reporting and for improved visibility. There are also 4 legacy reports that will soon be moved across to the new reporting suite. Custom reports are not supported yet. Learn more: Reports.
TM4J Cloud does not currently provide a plugin for seamless integration with Jenkins. However, you can use our REST API to integrate with automated testing tools. This plugin will be introduced in the near future. Learn more: REST API.
Yes, you can easily import test cases from Excel or CSV files by using the importing wizard.
TM4J Cloud does not currently provide gadgets for the Jira dashboard. This feature will be introduced in the near future.
TM4J Cloud does not currently support JQL functions.
Atlassian requires that you purchase the same license level for apps as you have for your base product. They explain this here.
There is unfortunately not a way to purchase a lower license tier for apps at this time.