How to Manage Test Cases Easily with Test Case Lab Tool [Hands on Review]

Needless to say that nowadays none of the software releases are performed without proper Quality Assurance activities.

Different professionals use different approaches on how to keep the stable quality of their product.

Despite the fact that automated testing becomes more and more commonly used, still the manual checking is important.

The reasons might be different: 

As a result to mentioned reasons, the QA team will probably shift to good old-fashioned approach with test cases management.

Today we are going to review the new case management tool – TestCaseLab in action.

This tool allows you to handle your test cases, test plans, and test runs in web application and then report cases (if required) to a bug-tracking system. Even though the market has some alternative solutions, among the similar features package TestCaseLab offers nice UI/UX and fresh look on the whole test case management process. Moreover, the platform will visualize your overall progress on test runs.

Let us quickly run through the basic functionality and demonstrate how it actually works.

In order to start, you should sign up first. After filling a simple form and approving account creation in received email, you’ll be able to access your account.

What You Will Learn:

 

While passing all the instructions in the wizard you’ll have to create your first project and invite team members if required.

Setting up:

Within TestCaseLab system there are two types of roles:

1) Company role

2) Project role

Therefore, you have 2 types of Administration panels:

1) Company Admin panel

(Note: Click on any image for enlarged view)

Here you may:

2) Settings (Project Admin) panel

Here you may:

Test Cases

Once everything is set up and you’re done with user invitations, you may start working with test cases.

Creating categories and test cases are such a simple thing to do. When you have the structured list of required categories, you may start filling them with test cases.

Available Test cases fields:

Normally every test case should have its content. In this tool you’ll have quite a variable list of required fields:

All the fields are editable and accessible at any period of your activity: Test Cases -> Test Plans -> Test Runs.

You may even check the editing history of any test case.

The system also has synchronization of simultaneous work of two different users. If other users will be editing the same test case, you will get a notification.

Every test case has a unique link which can be copied and provided to other existing users. If a user is included in the active project, the test case will be opened directly.

Advanced search options:

The system has searching, sorting, and filtering options. Any test case can be found by the keyword or test case key. When searching, user may apply a lot of filtering options:

After that search results can be sorted by:



Search results will appear in the same section:

Test Plans

When you’re done with creating and filling up test cases, it is time to start your first Test Plan. Creating your Test Plans isn’t a complicated activity as well. The whole page has similar to Test Cases page UI. You will just need to define the name and start adding test cases.

Creating your Test Plans isn’t a complicated activity as well. The whole page has similar to Test Cases page UI. You will just need to define the name and start adding test cases.

In the pop-up window, you may browse through your available categories and select the appropriate test cases to be included in the Plan. Or you can even search them by keywords or different properties. Then simply checkbox every issue you need.

It is really easy to complete your Test Plan: you can select all test cases from a particular category or even couple of them; you may even select all available test cases.

When filling Test Plan with cases, you may still modify or edit them. It means that all changes will be saved to initial test case and synchronized in all sections (Test Cases, Test Plans, and Test Runs).

If you wish to have couple similar plans with minor differences, you can easily copy existing plan and then modify the content of the new plan. In order to open the context menu:

There is no limit on the quantity of test plans or test runs to create, so you can create as many as you need. Your QA team may adapt different testing scenarios, reuse required test cases and customize plans.

Test Runs

When Test Plans are ready, a user can pass to Test Runs.

At this page, they simply enter the name of the run and select the test plan which will be the basis for this particular run (‘TestPlan’ field may be left empty though).

Created test run will look like this:

It has all the required parameters (creation date, colored statuses and their percentage) that visualize the progress of the particular test run.

Now you or your QA team is ready to perform the testing – simply by opening recently created object.

According to the previous pages, the interface here is still divided into three functional sections in order to give a user the possibility to navigate easily and modify the content if necessary.

The bar on the top demonstrates testing progress. The right section contains status buttons, comments section and navigation buttons.

If a user didn’t select any Test Plan as a basis to this particular test run, it will be created empty. After that user can easily fill the run with all required test cases manually.

In order to complete the test run, users should follow the list case-by-case and apply different statuses to test cases inside of it. Cases may be selected manually, with ‘Next’ or ‘Next Not Tested’ buttons.

In case the integration with supported bug-tracking system (e.g. Jira) was previously set up, all test cases with ‘Failed’ status will be reported to the linked project directly.

Once reported, the bug will automatically be created with the input data inside mentioned project.

According to the logic mentioned in Test Cases part, if another user is editing the same case in the test run, the initial user will have no possibility to edit and the case will be locked.

The test run is considered to be completed when all the test cases inside of it are processed. Again user may check the status bar which will indicate the success rate of mentioned test run.

If the particular test run is considered to be failed, QA team simply waits until all (or some) reported bugs are fixed and then the user creates new similar test run on the basis of the same test plan.

QA team can also perform periodic system checks and plan their activities by creating test runs for future dates.

Conclusion

So that was a walk-through of the new TestCaseLab system and its basic features.

Overall the system shows quite good performance along with having a great interface and easy user experience. It has most of the required features that test teams need.

The best part is – you can play with this tool for 60 days on a free account. Here you can sign up for the trial.

Feel free to let us know if you would have any questions, comments, or any new feature that you’d like to see.