Creating, scaling, and maintaining automated tests becomes a challenge when teams grow. People work on the same modules, reuse the same libraries, and update shared test assets every day. This is where the Multi User Workspace concept in TOSCA becomes essential. It allows teams to work together in a structured environment where updates stay organized, conflicts stay under control, and collaboration stays smooth. This guide explains how the repository works, how branching functions, how check in and check out behave, and how to manage real project scenarios step by step.
Introduction
Test automation teams often deal with large suites that evolve daily. A single update can affect several tests, which makes collaboration a serious concern. The Multi User Workspace system in Tricentis TOSCA Certification training solves this by giving every user their own Multi User workspace with controlled access to shared assets. It operates similarly to a version control system. You gain structure, traceability, and predictable updates without slowing down development. You also get safe change tracking and controlled merging. These principles help teams deliver stable tests while keeping productivity high.
This guide focuses on all core elements of the Multi User Workspace, including repository creation, Multi User workspace setup, branch creation, branch switching, conflict resolution, and check in strategies. The goal is to help learners gain hands-on clarity so they can use the system effectively in real projects.
Selecting a Repository and Using SQLite
Every project begins with a repository. TOSCA supports different repository types, and SQLite remains one of the most common choices for small and mid sized teams. When you create your repository you can store all modules, test cases, test data, execution lists, and reusable assets in a structured format. The Multi User Workspace setup relies on this central repository to track all changes. SQLite works well because it is lightweight and does not require a separate database server. It keeps the environment simple while still offering the structure needed for team collaboration.
In a new project, you usually create a main repository first. This main repository becomes the foundation on which all user workspaces operate. It holds the master branch, the history of updates, and all global assets shared by the team. Once the repository is ready, every team member creates a workspace that connects to the repository and synchronizes updates.
Creating a New Repository and Main Branch
When you create a new repository, the first structure that appears is the master branch. The master branch serves as the primary line of development where approved updates are stored. Just like in a version control system, users can work in separate branches and merge changes into the master branch after testing and review. The Multi User Workspace model uses this primary branch to maintain consistency. Users work in isolated environments but still share a common baseline.
Creating a new workspace is simple. You select your repository, provide workspace location details, and let TOSCA initialize the local workspace. This workspace contains a local copy of the assets. It allows you to work offline, experiment safely, and perform daily testing tasks without affecting others. When you finish your changes, you use check in to update the central repository.
Admin Credentials and User Management
New setups begin with admin access. The default admin credentials often include a simple user ID and password. Admin users create the repository, set workspace permissions, define access rights, and supervise branching activities. The Multi User Workspace infrastructure depends on this admin layer to maintain stability. Admin users can review check ins, approve merges, and control branch level access. They also troubleshoot conflicts and manage repository backups. A predictable admin workflow helps teams maintain a secure and well organized environment.
How Check Out Works
Check out controls who can edit which asset. When you check out an object, you reserve it for editing. Others can open the object in read only mode, but they cannot change it until you check it in. This prevents overlaps and ensures that updates remain clean. The Multi User Workspace system uses check out to reduce conflicts. For example, if a user wants to update a test case, they check it out first and complete all changes locally. While it is checked out, the object stays locked for other users.
Users can check out single objects or complete folder structures. This can include modules, test case folders, reusable functions, or test configuration files. Check out ensures that every change is traceable and that no two users overwrite each other’s work by mistake.
How Check In Works
Check in takes the local updated version of an asset and writes it into the central repository. Before you check in, TOSCA compares the local version with the repository version. If no conflicts exist, the check in completes smoothly. If conflicts exist, you receive a warning that other users updated the same asset. You must resolve this before continuing.
The Multi User Workspace model uses check in as the gatekeeper for repository updates. Teams often follow a simple workflow: complete changes, test locally, verify structure, and then check in. This keeps the master branch stable and reduces downstream issues. A good check in strategy helps teams avoid inconsistent test data and broken references.
Creating and Using Branches
Branching allows users to develop features, fix issues, or experiment without affecting the main workflow. You can create a new branch from the master branch or from any existing branch. When you create a branch, TOSCA copies the structure so you can work independently.
Branches work well for large updates or parallel development. For example, a team might use a dedicated branch for a sprint, an environment update, or a specific project module. The Multi User Workspace architecture gives branches full isolation so users work without disturbing others.
Once a branch is ready, you can merge it back into the master branch. Merging takes the changes from the branch and integrates them. The master branch then contains the updated version of the assets. Branching reduces risks, improves organization, and allows teams to test major changes safely. It operates similarly to source control tools while staying fully integrated into the visual TOSCA interface.
Branch Switching and Synchronization
You can switch between branches at any time. When you switch, TOSCA loads the correct object version for that branch. Your workspace adjusts to the selected branch and updates your local copy. The Multi User Workspace environment stores only relevant objects for each branch. This prevents confusion and keeps local workspaces clean. When you return to another branch, you see that branch’s version of the test assets.
Synchronizing a branch means bringing the latest updates from the repository into your workspace. This is important because other users might update the repository while you work. Regular synchronization prevents conflicts and helps you stay aligned with the team. It ensures that when you merge your branch, you merge into an updated master branch.
Comparing with Git Based Systems
The branching and merging flow resembles Git style workflows. You check out objects, complete updates, commit changes through check in, and merge branches when features are complete. The Multi User Workspace system does not require command line steps. Instead, it uses a visual structure. It still follows the same principle of distributed working and centralized synchronization. This combination helps non technical users work smoothly while giving teams a strong collaboration model.
Best Practices for Workspace Management
Good workspace management helps avoid issues and supports efficient teamwork. You should always synchronize your workspace before you start the day. This ensures you have the latest updates. You should check out only what you need so others can continue working. You should maintain small check ins rather than doing one large check in. This reduces conflict chances. The Multi User Workspace workflow benefits from consistent habits. Many teams follow a weekly branch review to keep the repository clean. Good management prevents unnecessary complications and supports clear communication.
Teams also prefer structured naming patterns for branches. You can name branches based on features, versions, or sprint numbers. You can also use comments in check ins so others understand the purpose of each update. These practices support smoother collaboration and stronger traceability.
Common Issues in Team Workflows
Conflicts can occur when someone updates an object after you check it out. TOSCA detects the conflict during check in and alerts you. The Multi User Workspace framework gives clear warnings so you do not overwrite another user’s updates. You can review both versions and decide how to merge them. Larger teams also face issues with outdated workspaces. Users sometimes forget to synchronize their workspace before starting the day. This causes mismatched versions and missing updates. Consistent synchronization solves this issue.
Another challenge involves branches that stay active for too long. When branches become outdated, merging becomes more difficult. Teams should merge frequently or rebase their branches by updating them with the latest repository changes. Small and frequent merges reduce conflicts.
Handling Merge Conflicts
A merge conflict occurs when TOSCA detects changes in the same object across multiple sources. When this happens you receive a conflict alert. You must compare the versions and decide which change should remain. The Multi User Workspace model provides a visual comparison tool to help you see details clearly. You can compare modules, test cases, attributes, or folder structures. Once you decide the correct version, TOSCA completes the merge.
Good communication prevents many conflicts. Teams often announce major updates before checking them in. This helps others prepare or avoid editing the same object. Merge conflicts are normal in collaborative environments. Clear ownership rules and predictable workflows help minimize them.
Advanced Branching Techniques
Some teams use multi level branching. For example, they create a development branch, a testing branch, and a release branch. Each branch holds a different stability level. Users develop features in the development branch. Testers validate them in the testing branch. Finally the team merges validated changes into the release branch. The Multi User Workspace architecture supports this clean structure. Each branch remains independent until merged. This helps teams handle large scale automation projects that involve multiple parallel tasks.
Teams also use branches for environment specific changes. You might have a branch for staging and another for production. This helps maintain environment specific test data or configuration differences. After testing, you merge stable updates into the shared master branch.
Real World Scenario Example
Imagine a team with ten automation testers working on a large web application. The master branch contains stable test cases used in daily runs. A new feature arrives and requires several updates in modules, reusable functions, and test case design. Instead of making these changes directly in the master branch, the team creates a dedicated feature branch. Each tester creates a workspace that points to that branch. They check out the needed objects, complete changes, test locally, and check in updates to the branch.
As testing progresses the team synchronizes the branch regularly. Once everything is stable, they merge the branch into the master branch. This entire workflow runs within the Multi User Workspace model. It supports safety, clarity, and predictability.
Importance of Repository Backup
Backing up the repository is essential. Teams sometimes perform daily or weekly backups. The repository holds all core assets. If anything goes wrong a backup can restore the structure. Admins often automate backup tasks. The Multi User Workspace system relies on a healthy repository to function smoothly. Regular backups protect against accidental deletions, file corruption, and unexpected computer issues.
Key Takeaways
A structured workspace helps teams work confidently. Check out prevents accidental overwrites. Check in provides safe updates. Branching supports parallel development. Synchronizing maintains alignment. Merging integrates stable updates. The Multi User Workspace model keeps collaboration controlled and predictable. It gives teams confidence when working on large and dynamic test suites. Combining daily discipline with a clear branching strategy helps teams scale automation smoothly.
Conclusion
In summary, mastering Multi User Workspace in TOSCA particularly with SQLite, check-in / check-out, and branching is a foundational skill for any automation team or individual preparing for TOSCA Training, TOSCA Automation Course, or Tricentis TOSCA Certification.
Take the next step and explore all core features in depth. Strengthen your skills and move forward with confidence.
