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

In the contemporary digital era, launching software functionalities without suitable Quality Assurance practices is unthinkable.

Different specialists utilize diverse strategies to sustain the reliable quality of their offerings.

Despite the surge in the popularity of automated testing, manual assessment continues to hold significance.

The reasons are diverse: 

• Certain features may not be handled by automated evaluations;
• Some sections are overly basic and don’t necessitate the complexity of automation;
• Quality assurance engineers may not possess the requisite knowledge and competence for comprehensive automation.

As a result of these factors, Quality Assurance teams will probably resort to the conventional method of managing test cases.

Today, we will provide an in-depth review of the new case management software – TestCaseLab.

This software enables you to organize your test cases, test blueprints, and test executions in a web application and report cases (if needed) to a defect tracking system. Although alternatives are present in the market with similar capabilities, TestCaseLab distinguishes itself with its intuitive UI/UX and innovative method for test case coordination. Additionally, the platform offers depictions of overall advancement on test runs.

Let’s briskly peruse through the elementary functionality and exhibit how it functions.

To begin, registration is the initial requirement. After supplying the necessary details in a simplified form and verifying your account creation via the verification email, you can log into your account.

 

By adhering to the guidelines in the guide, the creation of your initial project and the invitation of team members (if needed) become achievable.

Configuring:

In the domain of TestCaseLab, two kinds of roles exist:

1) Organizational role

• Organizational Administrator (possesses complete control of the account and projects)
• Organizational Employee (possesses zero control of the account)

2) Project role

• Project Admin (retains comprehensive control of the linked project(s))
• Project Member (can conduct ordinary tasks within linked project(s))

As a result, there are 2 categories of Administration panels:

1) Company Admin panel

(Clue: For a magnified view, tap on any image)

Within here, you can:

• Invite new users, adjust their roles within the Company, or eliminate them;
• Construct new Projects, abolish, or transform existing ones;
• Oversee your Organizational profile (name, domain, membership).

2) Settings (Project Admin) panel

In this panel, you can:

• Edit your Project specifics (Project name and Project key);
• Add associates to the Project, eradicate them, modify their Project roles, or invite new users and add them as Project associates concurrently;
• Amend types of test cases of a current Project;
• Establish integration with your defect-tracking system and the current Project. Systems supported at present: JIRA, Redmine, Pivotal tracker;
• Export existing Project details to a CSV file;
• Import your personal data with a CSV file to the Project.

Test Cases

Upon setting all elements and extending invitations to users, you can commence operations with test cases.

The fabrication of categories and test cases are simple operations. Once a structured inventory of necessary categories is accessible, test cases can be populated.

Fields Obtainable for Test Cases:

Usually, every test case should harbor its contents. In this tool, you’ll access a fluctuating list of mandatory fields:

• Name
• Test case key
• Category
• Tags
• Created by
• Last updated by
• Type
• Priority
• Execution
• Test Plans
• Description
• Steps
• Expected outcomes
• Add-on

Every field is modifiable and can be accessed all through your testing process: Test Cases -> Test Plans -> Test Runs.

The editing history of each test case is also viewable.

The application also enables synchronization for same-time editing of test cases by assorted users. If another user edits the same test case, you’ll receive an alert.

Each test case carries a unique URL that can be duplicated and disseminated with other users. When a user is an associated member of the active project, the test case will be visible directly.

Extensive Search Alternatives:

The system provides searching, assortment, and filtration selections. Any test case can be sourced by keyword or test case key. When searching, several filtration selections can be employed:

• By Type
• By Priority
• By Execution
• By User
• By Category
• By Tags

Search results can be arranged by:

• Creation time
• Title
• Last edit time
• Category

The search results will appear in the same segment:

Test Plans

Upon fabrication and population of your test cases, the commencement of your initial Test Plan can occur. Creating your Test Plans is equally an effortless job. The Test Plans page possesses an interface akin to the Test Cases page. It simply necessitates defining the name and beginning the addition of test cases.

Creation of your Test Plans is also an effortless task. The Test Plans page carries an interface similar to that of the Test Cases page. The task merely needs asserting the name and starting the supplementation of test cases.

In the pop-up pane, your accessible categories can be perused and applicable test cases chosen for inclusion in the Plan. Test cases can even be searched using keywords or other properties. Simply select the checkbox for every necessary test case.

The conclusion of your Test Plan is simple. All test cases from a specific category or multiple categories can be selected, or even all accessible test cases can be chosen.

Whilst stuffing the Test Plan with test cases, modification or editing of them can still be performed. Any alterations will be conserved in the initial test case and synchronized throughout all sections (Test Cases, Test Plans, and Test Runs).

If you wish to create Plans with minor dissimilarities, an existing plan can be duplicated with ease and the content of the new plan edited. To access the context menu:

There is no restriction on the count of test plans or test runs that can be created, enabling the creation of as many as necessary. Your QA team can adapt diverse testing scenarios, repurpose needed test cases, and modify plans.

Test Runs

Upon the readiness of the Test Plans, progression to Test Runs can happen.

On this page, you simply input the name of the run and select the test plan that will act as the foundation for this specific run (the ‘TestPlan’ field can be left devoid).

The constructed test run will resemble this:

It depicts all the necessary parameters (creation date, colored statuses, and their percentages) that visualize the advancement of the test run.

Now you or your QA team are equipped to perform the testing simply by accessing the lately created object.

<img class=”alignnone wp-image-9591″ src=”https

Related