Even though TM4J is designed to make your life easier, challenges may still arise as you figure things out and the app grows.
Here are some frequently asked questions and answers. If you still don’t find the information you need, don’t hesitate to reach out to TM4J Cloud support.
Test plans provide a high-level view of your entire test initiative. You can customize test plan fields to track scope, risks, strategy, pass/fail criteria, test bed, etc. Associate test cycles with a test plan to better track test executions. There are also several reports you can filter by test plan, which aggregate all stats/results from the child test cycles linked to the test plan.
You aren't required to use test plans with TM4J, but they are incredibly useful if you choose to do so.
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.
Yes, basic versioning functionality is available for test cases. Version control is enabled by default and allows teams to collaborate and manage multiple versions of test cases in parallel while maintaining data integrity and providing an audit history of changes. Versions can easily be viewed and compared for audit purposes.
Learn more in the Creating New Test Case Versions topic.
Definitely. The order of test cases within a test cycle can be set from the Cycles view. Just drag and drop test cases into whatever order you prefer, and this order is reflected in 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.
Yes, TM4J supports call-to-test. Instead of duplicating or copying/pasting test cases or steps, break them down into smaller, reusable pieces to construct new tests and achieve larger end-to-end testing scenarios. That way, test cases can be referenced (or called) into other test cases to enhance reuse.
Check our Reusing Test Data with Call to Test to learn more.
TM4J Cloud does not support parameters within a test case at this time, though the feature is on our backlog.
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 Jira issue or the kanban board.
TM4J Cloud does not support test data to be used within test cases at this time, though the feature is on our backlog.
TM4J Cloud does not support BDD type test cases at this time, though the feature is on our backlog.
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.
Check our REST API for more info.
Absolutely! TM4J supports custom fields for test cases, test cycles, and test plans.
Check out Configuring TM4J to learn how to set them up.
Yes! Here's some information on our integration with Jenkins.
Yes, you can import test cases from Microsoft Excel, CSV files, or from other TM4J instances using the importing wizard.
TM4J Cloud does not provide gadgets for the Jira dashboard at this time, but this feature is on our feature backlog.
TM4J Cloud does not support JQL functions at this time.
Atlassian requires that you purchase the same license level for apps as you have for your base product. Here's the explanation. There is, unfortunately, no way to purchase a lower license tier for apps at this time.