Qualitia Automation Studio creates the following databases in the selected database management system (MySQL or SQL Server):

• A Master Database that serves as an anchor for all the projects.

• A Project Database for every project, which is stores the associated project artifacts. Every Project Database is named as Projectname_projectdb.

• A Result Database for every project, which stores the results of all the test suite executions. Every Result Database is named as Projectname_resultdb.

Best Practices

• Qualitia recommends integrating your project with a version control tool (SVN or Git).

• Take the backup for database, GIT/SVN, custom actions, and reports daily.

• While taking a project backup, ensure that you perform the following actions:

  • Take the backup for Database, custom actions, reports, and SVN/GIT at the same time so that all the artifacts are in the same state and are synchronized with each other.

  • Users must stop their work while taking the project backup.
    Tip: Close the license server temporarily to stop users from using Qualitia.

  • If you are not using a version control tool, then for every project ensure that you take the backup of the following folders:

    • Project Path, which stores the test cases and tasks as XML files.

    • Custom Action Repository Path, which stores the custom actions.
      Note: To know the location of these folders, click Setting > Configuration Settings > Dependency.

• While backing up a Qualitia project, ensure that you backup the constraints and triggers for the following databases:

  • Master Database

  • Project Database

  • Reports Database

• Similarly, while restoring a Qualitia project, ensure that you restore the constraints and triggers for the following databases:

  • Master Database

  • Project Database

  • Reports Database
    Note: If you restore a project without restoring the backup of its constraints and triggers, then after the project is restored, the object creation may fail.

• Before upgrading the Qualitia Automation Studio to a higher version, take a backup for all the projects and follow all the best practices recommended for backing and restoring the project