TAUtilities overview

TAUtilities' APIs can be invoked from application programs that are based on Microsoft Component Object Model (COM) technology or Java. TAUtilities is a library which allows you to connect and retrieve data from a TestArchitect repository server .

With TAUtilities you can connect to a TestArchitect repository server to retrieve test modules, test cases, results, etc., and then export the returned information to your summary report in an application such as Microsoft Excelâ„¢.



Tip: Read here for a full list of APIs provided for TAUtilities.

TestArchitect provides the files TAUtilities.dll and TAUtilities.jar (included with installation of TestArchitect) that expose the automation library objects and functions that are used in TAUtilities:

Both files are located in directory TA_INSTALL_DIR\lib.

As a rule, processing data queries between your application program and TestArchitect involves six steps:
  1. Register TAUtilities.dll in COM application programs.
    Remember: In Java application programs, instead of registering TAUtilities.dll into the registry, you must reference the following .JARs from within your Java project (learn more):
    • TAUtilities
    • SLF4J API module
    • Logback Classic module
    • Logback Core module
  2. Create a Repository type object to establish the connection to a TestArchitect repository by calling the CreateObject() and Connect() methods.
  3. Call the Login() method to log on to the repository.
  4. Call getProject() to access objects of a single TestArchitect project, or call the getProjects() method to access objects of multiple projects.
    Note: Data can only be retrieved after the connection has been established successfully and you have logged on to the repository. In case of exceptions that TAUtilities functions may throw, use the static getLastErrorMessage() method of the Repository class to catch the most recent exception message.
  5. Based on your particular scenario, call the appropriate methods to interact with the TestArchitect items such as test folders, test modules, or test cases.
  6. When you are done with the connection, explicitly close the it by calling the Disconnect() method.