Easy Refactoring
Changes are inevitable with test scripts. When they happen, TestArchitect allows you to refactor all related test assets in a snap. Although an action or interface is called from a thousand places, you only need to update it once in your testing process with the refactoring feature.
Integration for Continuous Testing
TestArchitect seamlessly integrates with powerful third-party Automation tools, to assist you in application lifecycle management, test management, and bug tracking. Everything naturally suits your in-house CI/CD & DevOps pipelines.
Tailored fit to Microsoft TFS ALM
You can import tests from TFS and automate them in TestArchitect. Automated tests can then be executed by testing tools—from either TestArchitect, Microsoft Test Manager, or silently in your CI/CD pipelines from a command line. You can choose whether test results will automatically be uploaded to TFS or TestArchitect Repository Server.
JIRA as the bug tracking system
Import JIRA bugs to TestArchitect and associate them to specific test lines confirming the bugs. On the next test run, TestArchitect will brief you whether the bugs have been resolved or not.
Failures which are already linked to a bug will be counted as Ignored Fails. Doing this filters out the noises, because those bugs have been logged in JIRA and you are already aware of them. You can focus on tackling new failures instead.
Failures which are already linked to a bug will be counted as Ignored Fails. Doing this filters out the noises, because those bugs have been logged in JIRA and you are already aware of them. You can focus on tackling new failures instead.
Designed with Jenkins pipelines in mind
Leverage TestArchitect’s Jenkins plugin to queue a new test run and dispatch any number of TestArchitect test modules to any number of Jenkins slave machines.
TestArchitect can be configured to automatically export test results to various formats in which Jenkins can interpret and display in its Dashboard.
If you’re using Jenkins, you can expect all of the “plumbing” work for an end-to-end pipeline from code commit, provisioning, test execution to result publishing has been out-of-box.
TestArchitect can be configured to automatically export test results to various formats in which Jenkins can interpret and display in its Dashboard.
If you’re using Jenkins, you can expect all of the “plumbing” work for an end-to-end pipeline from code commit, provisioning, test execution to result publishing has been out-of-box.