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: Managing Test Plans and Waterfall development (with Test Plans and Test-Execution Cycles).
Yes, TM4J is tightly integrated with Jira and Confluence, so you can link test cases, test cycles and test plans to any Issue type in Jira and any Confluence page. TM4J also offers several traceability reports to track traceability and coverage.
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: Versioning.
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: Call to Test and Managing and Reusing Test Cases.
Yes, parameters are used to unlock more flexibility when calling or reusing modular test cases. Meanwhile reusing a module, the master test case can invoke a reusable test case by passing a set of parameters, which can affect how input or output data are displayed or processed during the test execution. Learn more: Parameters and Designing Test Cases.
Yes, data-driven testing (DDT) is supported. DDT enables the repetition of the same sequence of test steps with the help of a data source in order to drive the input values of those steps and the expected values while verification steps are performed. By doing so, each time the test case is executed, the variable is replaced with the test data existing in the data source. For each row in the test data table, a new set of steps will be unfolded during the test execution (with the variable replaced with the test data). Learn more: Test Data and Data-driven testing and Managing and Reusing Test Cases.
Yes, TM4J allows the user to create BDD test cases in JIRA as well as export the test case to a feature file. This feature file can then be used as a reference for writing unit tests that will be needed for it to run. TM4J also support integration with CI/CD tools, such as Jenkins, etc. Learn more: BDD test cases, Designing Test Cases and API and Test Automation
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 then fire up single test execution directly from the issue screen in Jira or the kanban board. Plus, you can integrate BDD test cases with your test automation initiative as well as integrate with CI/CD tools, such as Jenkins, etc. Learn more: BDD test cases and Common Usage.
With our extensive 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 seamlessly 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: API and Test Automation
Yes, TM4J supports custom fields for test cases, test steps, test plans, test runs and test execution. Learn more: Configuration.
Yes, TM4J offers up to 70 cross-project reporting and 60 gadgets for improved visibility. In addition to that, you can create live reporting pages on Confluence with up to 60 macros. Custom reports are not supported yet. Learn more: Reporting.
No, TM4J runs on top of Jira but uses different database tables. In addition to that, all screens display paginated lists of data to prevent any slowdown on the server. Plus, our entities (test cases, cycles, plans) are not Jira Issues, so it doesn't cause/trigger reindexing in Jira.
Jenkins is a continuous integration tool that helps with the deployment of software projects. Through this, you can run automated tests while building a project, and monitor the results. The TM4J Jenkins plugin enables a set of tasks that both report on automated test results and run BDD test cases from within JIRA. Download here: https://plugins.jenkins.io/tm4j-automation. Learn more here.
Test Management for Jira’s Bamboo integration enables you to automate tests outside Jira, run them in Bamboo during the CI/CD pipeline and have results sent back to TM4J for reporting and tracking. Learn more here.
Yes, using macros helps you to expand the capabilities of your Confluence pages, allowing you to add extra functionality or include dynamic content. By using Test Management Reporting for Confluence (TM4C) you can get real-time insights into your test management initiative with up to 60 out-of-the box testing macros. By using these macros, you'll be able to create insightful testing reports to track coverage, progress and quality across JIRA projects, epics and user stories . Also you'll be able to share them with your colleagues for easier data analysis and collaboration. Test Management Reporting for Confluence (TM4C) is a free app for Confluence. Learn more: Confluence Macros.
Yes, TM4J offers up to 70 cross-project gadgets. You can create insightful cross-project reports and dashboards to track coverage, progress, and quality and share them with your colleagues for easier data analysis and collaboration. Learn more: Gadgets.
Yes, TM4J provides advanced searching with JQL functions. A function in JQL appears as a word followed by parentheses, which may contain one or more explicit values or JIRA fields. JQL stands for JIRA Query Language (not to be confused with Java Query Language). JQL functions are used to search issues in Jira related/linked to test entities (test cases, cycles, plans, etc). Learn more: Advanced searching with JQL functions.
Yes, you can easily import test cases from Excel or CSV files by using the importing wizard. Learn more here: Importing Test Cases.
No, TM4J is a test management app. If you manage the requirements as issues in Jira or pages in Confluence, TM4J offers native traceability. TM4J also supports web links with external web-based requirement management tools.
We release a new version every four weeks. In-between we release minor versions and bug fixes.
Adaptavist offers professional services to address training and implementation.
Adaptavist is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week. Mon - Fri 9:00AM - 5:00PM BST. Visit the service desk portal to ask questions, raise defects and request improvements.
All features are available during the trial period.
No, data will be preserved. When you buy a license and activate TM4J, you’ll have access to the data with no restrictions.
For sure, you should create a general request in the service desk asking for the roadmap.
Yes, TM4J offers out-of-the-box history tracking and versioning for test cases. Changes in the test cases don’t impact existing test executions results. TM4J also offers bi-directional traceability among all testing entities and issues in Jira. On top of that, TM4J offers 70 built-in reports to track coverage, progress, and quality.
Yes, TM4J support test environment management. A test environment is a field of a test execution used to determine the target environment to be tested for each test case. When creating and planning test environments you can define your platform attributes to address different combinations of test configurations, such as operational systems, browsers, databases, hardware, languages, etc. Learn more here: Managing Test Environments
Learn more here: Extending the Free Trial