Introduction

In order to understand Qualitia SVN integration in detail, please refer the diagram below showing the physical layout of Qualitia and SVN.



Qualitia automatically updates the latest changes from your SVN server whenever required. SVN actions like Update and Commit are implicitly handled by Qualitia.

To understand this implicitness better, you can go through the different cases below in which you might have to use SVN in.

Setting Up a New Project

Create a new project in Qualitia called "Project ABC." Qualitia automatically creates a directory "Project ABC" and also creates Test Cases, Tasks, and Custom Action sub directories. As Project ABC is still not checked into the SVN server, you cannot allocate users to it and expect it to start working.

You have to do the following explicitly:

1. Add and commit your newly created Project ABC directory to SVN.
2. Once SVN commit is done, you need to ask your team to check-out Project ABC to their Qualitia Project Path.

Once this is done, Qualitia will automatically update and commit all your Qualitia test cases and tasks to your SVN repository as and when required.

Qualitia will also automatically update and commit changes during test case development, task development, and execution.

Creating/Editing Test Cases and Tasks

To understand what Qualitia does when a test case/task is created or edited, refer to the table that shows a sequence of steps performed by a user.

The table below considers a user working on a test case ABC containing Task A, Task B, and Task C.

When the user "A" clicks Test Case ABC to open it, then Qualitia gets an update for Test Case ABC and all tasks from SVN, so that the latest update is always available to the user and the impact is known as early as possible.

Managing Artifacts by Qualitia SVN

Test cases and tasks are automatically managed by Qualitia SVN.  Environment.XML and Custom Action files do not get managed by Qualitia and you have to continue managing these artifacts using SVN client.