Setting Up Your Test Management Workstation in QAComplete
Test and Monitor | Posted March 27, 2013

A challenging part of software development is being able to manage your teams goals and data in an organized manner. Test management is the process of managing all your tests for any given project. Whether you are working with automated test cases or exploratory test cases, you still need to organize your tests and results to keep your team on track in meeting project goals. It is equally important to have a tool that everyone on your team can access and collaborate in.

QAComplete allows you to do exactly that: manage all your resources, test cases, results, defects and testing metrics in an easy-to-use, user friendly environment. You can use QAComplete as a software as a service (SaaS) in the cloud or on-premise within your work network. Even better, with more software development teams working in an Agile environment, QAComplete introduces the ability to track hours on any given task within a sprint, which allows you to focus on the real priorities for any given iteration. Time is of the essence, and using a test management tool saves you time and money in the long run.

In this part of this QA series, we will focus on setting up your users and workspace. This essential step ensures that your team members don’t end up running into each other. We can specify who will do what in the project group. This includes the tasks and functions of QAComplete they have access to, whether it be adding, removing or updating any given element of the project.

Where do we start, you may ask? QAComplete is built with the Agile process in mind, but you can use it for other types of development processes as well. Understanding how you will be developing your product is the first step in maintaining efficiency within your workflow process. Because most of you are working in an Agile Scrum environment, we will discuss how we can set up the workspace for this workflow type and how we should deal with access rights for each individual in your project group.

setting up our users

The first step is deciding how to set up access rights for the different roles/users in your team. Access rights can be configured by the Security Administrator and anyone else with those privileges. For instance, the QA Engineer should have access to managing all test cases, but may not have the ability to create and change requirements.

Likewise, a Scrum Master should have the ability to manage sprints and have access to other project members’ time to ensure the focus and scope of the project is maintained. In any case, it is up to the Security Administrator to set up access rights to suit the needs of the project.

Once you have decided the roles within your development team and their access rights, you are ready to add users to the project. Adding users is simple. Simply add the user from the Users section and enter their contact information and select their roles within the team.

How do I get ready to implement a new test management system?

Below are some easy tips in setting up your project:


If there is anything more painful than implementing new process it’s implementing a new process single-handedly without collaborating with your team. A team that contributes to defining a new way of working tends to adopt that change more easily.

Test it out

If you are a QA engineer who will be adopting a test management tool like QAComplete take some time to get comfortable with it by setting up a simple fictitious project. Press every button and experiment with customization. Maybe there is a solution to a problem you didn’t even know you had. Testing the system out is not only a great way to learn the tools of the trade, but it allows you to teach others when the time comes.

Understand your unique situation

Reaching out to learn how others have implemented their test management systems is great and may provide some useful ideas you can implement. Understand your own processes and sketch out how it would look in a tool like QAComplete. Timing is everything when making these decisions. If you are in the middle of a big project, now might not be the time for a transition.

Set goals

Transitioning to a new tool takes time and planning. The transition is slow and staging out the transition over the course of a couple months with clear goals will make the process that much easier.

See also:



By submitting this form, you agree to our
Terms of Use and Privacy Policy

Thanks for Subscribing

Keep an eye on your inbox for more great content.

Continue Reading

Add a little SmartBear to your life

Stay on top of your Software game with the latest developer tips, best practices and news, delivered straight to your inbox