Even though TM4J Server/Data Center 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.
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, and other things. 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, 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.
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 organize 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.
Yes, TM4J supports parameters within test cases.
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.
Yes, TM4J supports test data to be used within test cases.
Yes, TM4J supports BDD type test cases.
With our REST API, which is free when you install TM4J, 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 TM4J 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.
Absolutely! TM4J supports custom fields for test cases, test cycles, test plans, test steps and test executions.
Yes, TM4J Server/Data Center offers a range of cross-project reporting (72 out of the box!). There are also a few legacy reports that will eventually be redeveloped for the new reporting suite. Custom reports are not supported at this time.
Yes! Check out the documentation for more information.
Yes, TM4J Server/Data Center supports various JQL functions.
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.