Three activities are shown here on the top of the dashboard, as follows:

Test scenarios: Stating number of Test Scenarios against project.
Test case: Stating number of Test Cases against project.
Defects: Stating number of Defects against project.

The following graphs are displayed.

• Heat Map: Shows the health of each project by displaying the number of defects open and fixed.
• Trend Analysis: Shows the current statuses of the defects.
• Defects by Severity: Refers to the severity of the defect being logged with filter.
• Defects by Status: Refers to status of the defect logged with filter.
• Test Cases Status: Refers to the current status of the test case with filter.
• Executed Test Cases: Refers to the test cases which have been executed with filter.
• Pie Charts: Can be accessed by clicking on any bar graph to analyze the number of defects considered, which led to a particular result.
• Test Case Progress: Shows number of test cases executed at specific intervals of time.
• Defect Closure Efficiency: Shows number of total defects and resolved defects.
• Active Defects: Shows number of unresolved defects against specific intervals of time.
• Defects Reopened: Shows percentage of defects reopened against specific intervals of time.
• Test Cases Fail: Shows percentage of failed test cases.
• Bug Fix Duration Days: Shows the number of days it took to fix a particular bug.
• Requirements Test Case Coverage: Shows coverage of requirements against cases.
• Bugs Statistics: Shows status of bugs – reported, fixed, open and others.

Along with our comprehensive Dashboard that is organized project-wise, now you will also be able to see a Global Dashboard comprising data related to Defects for all the projects you are a part of, in one place.

How this feature will help you:

If you need to see the data for all the projects, you can check the Global Dashboard and have a quick overview of all the stats of defects according to their type, priority, severity, etc.

Follow these steps to see the Global Dashboard:
1. Go to the ‘Dashboard’, click on the Project selection bar in the middle of the screen, and scroll to the top.
2. Click on ‘Global Dashboard’.
3. Your Global Dashboard will be displayed and if you want to navigate to your regular dashboard, click on the ‘Back To Dashboard’ button.

The project screen contains a list of all your active and archived projects.

Create Project

To create your project you simply click on ‘New Project’ button.

Not all testing projects are the same so you have the option to choose your project type and even customize the project type if required.

Choosing any project type will subsequently make any related OS, browser and devices field appear dynamically.

Fill out the following text fields to create your project.

• Project Name (Project Name must be at least 5 characters long.)
• Choose Project Type from project type drop-down
• Choose the Operating system from the given Operating system drop-down
• If you select Native Mobile Applications you can select device tab will appear to enter the devices.
• “Operating System” field is now enabled
• Write down any operating system in the “Operating System” field
• Provide a brief description of your project
• If clicked on “Cancel” link, the project will not be created and user will be redirected to “Create New Project” page

Once the details are final click on create to save your project. A success message confirms that your project is saved successfully.

Edit and Delete Projects

To edit project details, add users to projects or archive your projects, you simply hover the mouse to the list and click on any of the action buttons

Copy Project

When you click on the ‘Copy Project’ option, it will create a replica of the project you have selected. This will include all the data of your existing project, and save it as a newly created project. This data includes the build, modules, requirements, test scenarios, test cases, defects, and tasks, with all their associations.

How this feature will help you:

If you need the same data for another project, you can simply copy this project and save yourself the hassle of creating all the data again in a new place. All you have to do is copy the project, thus saving time and effort!

Follow these steps to Copy your existing project:
1. Go to the ‘Project Management’ tab. You will land on the ‘Projects’ page.
2. Hover over the project you want to copy and click on the ‘copy’ option.
3. Your project will be copied and will be available in the projects list.

‘Add Users’

Hover your mouse over the first icon (i.e. ‘Add Users’) given in the row of 4 icons beneath ‘Integration’.  

When you click on it, a pop-up will appear with a list of users available in the domain. You can select the users of your choice and add them in your project. 

Archived Projects

When you click on ‘Archived Projects’, you will be able to view all your archived projects. You can either restore or permanently delete them.

Team Management on the project level can be done through the team page in project management.

Users on Kualitee domain can be assigned to different projects. In case, a new user needs to be added you can click on add new user to start with adding a user to the domain first.

In User, you simply provide First Name, Last Name, Email, and the role that you would like to assign to this user within the project you want the user to be added. 

The build is the process of naming and providing the details of the software build/iteration/sprint that you would be testing as part of your project. Each project can have multiple builds.

Creating a new build

Fill the following fields:

• Build ID
• Start date
• End date
• Users
• Description

Click on “Create Build” button

To edit and delete the build hover the mouse to the list.

The next step after build creation is of modules.

Each build within a project can contain multiple modules. The Module Management screen will display a list of all modules within a specific build.

Creating a Module

Editing or Deleting a Module

You can edit or delete a module by hovering the mouse on the listing.

You can use requirements planning to associate your existing test scenarios and test cases with parent and sub-requirement.

Creating Requirements & Sub-Requirements

To create requirements, you simply go to project management, select requirements, and click on create a requirement. Your first requirement is your parent requirement and you can assign sub-requirements by selecting the parent requirement from the drop-down. A parent requirement can have multiple sub-requirements and the user can also associate test scenarios and test cases with these sub-requirements.

Associating Test Scenarios and Test Cases

If you already have test scenarios and test cases in your project, you can associate them with your requirements, or you can edit your test cases in Test management and select the requirement from the drop-down field.

Import & Export Requirements

To import your already created requirements you can simply download the CSV template and enter all the relevant information including your test scenario and test cases if you want them to be associated with your requirements. This will automatically create all the entries and populate the information.

Note: Kindly make sure that all the fields are mapped properly to avoid any issues.

Bulk Edit

You can edit your requirements in bulk. When you tick the checkbox against your requirement, you will be able to see the “Bulk Edit” option. Click on it and a pop-up will appear. You will then be able to update the associations of your requirements in bulk also you can edit your custom created fields too from the “Bulk Edit” option

Action Buttons

Clicking on ‘Action’ will give you the options to ‘delete’ or ‘copy’ your requirement. 

Filters

You can filter your requirements by the below-mentioned filters. You can also save your filters by ticking the ‘Save my Setting’ checkbox. 

Customize Listing:

You can now view your custom fields in your listing pages from the custom listing option.

To add customize your listing pages, follow the steps below:

1. Click on the “Custom Listing” option.
2. Select the fields you want to view in your listing pages, and they will be displayed.

The test case contains a summary, test steps, precondition, postcondition developed for a specific test scenario to verify any requirement. Multiple test cases can be associated with test scenarios and requirements for any build and module.

Creating a test case

1. Ensure that a Project has been selected from the ‘Select Project’ drop-down on top bar
2. To create a new Test Case select the ‘Test Case’ tab from within the Test Management tab
3. Click on the “Create Test Case” button

While creating a test case, Test case ID and Summary are compulsory fields. While others are optional fields.

Kualitee by default has different roles with a specific set of permission. If you are a tester creating test cases, you will need to get them approved before moving them forward for execution. By default, your domain admin, test manager has the permission to approve test cases. You can ask for approval with each created test case or in bulk when importing them.

Test Case Steps

Now make your test cases more granular by breaking down detailed steps into smaller yet precise actions with well-defined expected results. 

Import and Export of Test Case

Additionally, you can also import your already created test cases, you can either upload your own copy and map the fields according to Kualitee fields using the in-app mapping wizard or you can download the template and use that to upload your list of test cases.

You can export your data in three different formats CSV, Excel, and Word. Click on any of the icons will get your file ready for export and prompt you when it’s ready for download.

Bulk Edit

You can use the bulk edit option to change associations between data e.g build, module, requirements and test scenarios associated with your test cases can be changed using the bulk edit option for selected or otherwise all of the items in the listing. Also, you can edit your custom created fields too from the “Bulk Edit” option.

Note: Associations once changed cannot be reverted back to an earlier state.

Bulk Action

1. Save as copy: You can save a copy of your selected test cases, in the same project. 
2. Save as template: You can save a test case template, so you don’t have to create a new one when making the same kind of test case again.  
3. Status: You can assign a status to your selected test cases as Approved/Rejected.  
4. Delete: You can delete your selected test cases in bulk.  
5. Copy to project: You can copy your test cases to another project as well. (Note: No associations will be copied, only the test cases will be copied). 

Filters

Multiple filter options are available in the Test Cases tab to filter the test cases according to your requirements. 

Customize Listing

You can now view your custom fields on your listing page from the custom listing option.

To add custom fields to your listing pages, follow the steps below:

1. Click on the “Custom Listing” option.
2. Select the fields you want to view on your listing page, and they will be displayed.

Test scenarios are tied with builds and requirements. Test cases can be grouped according to scenarios to provide further coverage for testing.  The listing shows associations that each test scenario has with build, module, and requirements. Test Scenarios can also be created independent of the mentioned associated.

Creating a test scenario

To start with creating your test case, follow the steps below

Import and Export of Test Scenarios

Additionally, you can also import your already created test scenario and test cases, you can either upload your own copy and map the fields according to Kualitee fields using the in-app mapping wizard or you can download the template and use that to upload the your list of test scenarios.

You can export your data in three different formats CSV, Excel and Word. Click on any of the icons will get your file ready for export and promp you when its ready for download.

Bulk Edit

You can use the bulk edit option to change associations between data e.g build, module, or requirements associated with your test scenarios can be changed using the bulk edit option for selected or otherwise all of the items in the listing. Also, you can edit your custom-created fields too from the “Bulk Edit” option.

Note: Associations once changed cannot be reverted back to an earlier state.

Action Button 

1. Delete: You can delete your selected test scenarios in bulk. 
2. Copy: You can save a copy of your selected test scenarios in the same project. 

Filters

Multiple filter options are available in the Test Scenarios tab to filter the test scenarios according to your requirements. 

Customize Listing:

You can now view your custom fields on your listing page from the custom listing option.

To add custom fields to your listing pages, follow the steps below:

1. Click on the “Custom Listing” option.
2. Select the fields you want to view on your listing page, and they will be displayed.

The test cycle contains test cases or entire test suites that spans multiple builds. These cycles can be your functional cycle, UI cycles etc. They can also be your regression cycles. Cycles are created to move your test cases for executions.

Creating Cycle

• To create a cycle, ensure that a project has been selected
• Go to ‘cycle’ under ‘test lab’
• Click on ‘create cycle’

While creating cycles, you choose the respective build which is being tested. The testing dates would be within the same period that you have set for the build.

You can now also assign cycles to your teams so they can commence testing.

Deleting a cycle

You can also delete the cycle by hovering your mouse over the specific cycle.

Copy Test Cycle

You can make a copy of your test cycle and execute your test cases again, and generate new results, through the copy cycle option. Hover over the cycle name and a “copy” button will appear; click on it and the cycle will be copied.  

Users can drag and drop Test Scenarios and Test cases from the project repository to the cycle repository

You can move the same test case from your project repository to multiple cycles in the cycle repository. Each test case execution transaction history is maintained exclusively with regard to the cycle it was integrated.

Note: only those test cases will be available in the Project Repository, which are approved by the Test Manager.

In test case execution screen, you can execute both your manual and automated test cases. In the listing section, you will see test cases associated with build and cycles with which you have created the association. You can directly execute the test cases from the listing

To view the test case detail you can simply click on the test case and pop-up view will open.

Executing Test Case

To execute the test case simple click on execute. To manually execute, simply select the status from the drop down and click on execute. This will update the status of the test case and save the transaction.

When you have marked a test case as failed, the system will ask if you would like to associate a defect with it. Clicking on add defect will ask two options

• Create defect
• Attach existing defect

Clicking on create defect will take you to the defect management to create a defect from scratch. Clicking on Attach existing defect, will open a pop to choose the defect from your already created list of defects

Attaching files to executed status

You also optionally attach images, documents, and mp4 files to each executed status. Attachments will be available as links when generating an executed status report

Steps-wise Execution:

With multiple steps, teams can now execute steps and provide feedback by associating defects and attachments. 

Defect Management gives you a detailed picture of the type of defects. You can capture a bug by reporting different aspects of abnormalities in our information-rich format. You can further manage your defects by approving, assigning to developers, rejecting, and logging comments for future references. Bugs can be tracked in multiple ways, simplifying the process manifold through different viewing formats. You can monitor the bug history at any time with multiple information pointers.

Creating Defect

Ensure that a project has been selected and then move to defect management by clicking on the left side pane.

Defects Ids are auto-generated. You have the following fields to provide details on the defect in defect management.

• Build
• Module
• Defect Description
• Defect Type
• OS
• Severity
• Status
• Steps to Reproduce
• Actual Result
• Expected Result
• Comments
• Assign to
• Priority
• Attach Video
• Attach multiple images
• If you have integrated with JIRA, also select the JIRA user

Clicking on the Save button will create the defect.

Import and Export of Defect

Additionally, you can also import your already created defects, you can either upload your own copy and map the fields according to Kualitee fields using the in-app mapping wizard or you can download the template and use that to upload your list of defects.

You can export your data in three different formats CSV, Excel and Word. Clicking on any of the icons will get your file ready for export and prompt you when it is ready for download.

Bulk Edit

You can use the bulk edit option to change associations between data — e.g build, module and requirements associated with your defect can be changed using the bulk edit option for selected or otherwise all of the items in the listing. Also, you can edit your custom created fields too from the “Bulk Edit” option.

Note: Associations once changed cannot be reverted back to an earlier state.

Action Button  

1. Delete: You can delete your selected Defects in bulk. 
2. Copy: You can save a copy of your selected Defects in the same project. 

Filters

Multiple filter options are available in the Test Scenarios tab to filter out the defects. 

Customize Listing:

You can now view your custom fields on your listing page from the custom listing option.

To add custom fields to your listing pages, follow the steps below:

1. Click on the “Custom Listing” option.
2. Select the fields you want to view on your listing page, and they will be displayed.

In tasks, you will see tasks and timelines for your project. You can view the details of each task by bringing the cursor on it. The details include:

• Project Name
• Start and End date
• Module
• Assigned to
• Assigned by

We offer customization of colours, so users can differentiate between projects.

You can create, edit and assign new tasks to your team members by clicking on any of the dates you wish to start your project from.

Once you have successfully created and assigned the task, a notification will appear on the ‘Notification Bell’. Your task will also be represented on the calendar under the color you have chosen from the start to end date. You can check the brief details of the task by bringing your cursor on the color.

No matter what methodology you use Scrum, Kanban, or your own unique approach; Boards are built to support you, so you can work your way.

Columns:

Define your own columns for each process, and use them to quickly see the status of each task — and what still needs to be done before you can reach your goals.

Drag & Drop

You can drag and drop tasks and columns to reorganize your work or move it through stages. Project members can rearrange tasks as needed, and followers will get updates when tasks move columns so all members stay on the same page.

The task created by you is also shown in ‘Task Detail’ where you are able to log and track time against those tasks. Task Detail page shows your current tasks.

Time Log

You can log time and select whether you would like these hours to be logged as your billable hours.

The bug tracking report is one of the most important elements of a bug tracking system. The report is what tells every detail about a bug and how it was handled or is being handled. It is very important that each report is detailed. Bug tracking reports need to include certain pieces of key information. The following list portrays what’s in each and every report issued.

• Build
• Module
• Status
• OS
• Browser
• Assign to
• Severity
• Cycle
• Date

Export Defect report to Excel, CSV and Word. Also, you can make an extended search on the basis of defined parameters.

Under test reports you can develop custom test reports with key information such as:

• Build
• Module
• Test Case Status
• Cycle
• Date

Extended search allows you to filter through to the exact Test Report you are searching for and then take exports of the custom report that you have generated.

Export Test Case report to Excel, CSV and Word. Also you can make an extended search on the basis of defined parameters.

Under test execution reports, you can develop custom reports with key information such as:

• Build
• Cycle
• Tested By
• Selected Executed Status

Extended search allows you to filter the exact results that you are searching for.

Export the report in a format of your choice, e.g. Excel, CSV or Word. Also, you can make an extended search on the basis of defined parameters.

Scheduling reports help you streamline the information during off-peak hours. You can set the frequency of all the reports available in the reports module.

To get started you simply,

Save filters as templates for reusability

Scheduling Reports

To schedule auto-recurring reports. You simple

• Choose the report type as in Bug Report, Test Case Report, or Execution Report
• Choose one of the saved templates so you don’t have to set filters every time
• Choose Frequency whether you want daily, week, biweekly or monthly reports*
• Choosing the report format whether you want it in CSV, Excel, or Word
• Choose team members who are part of the project who should receive similar updates

*Kindly note that the reports are generated according to GMT

Once the reports are scheduled, they show up in the list. You can discontinue at any time by simply deleting the scheduled report from the list.

A cycle comparison report comprises of comparison of multiple cycles and the stats of those cycles. You can make a comparison of cycles having the same test cases but are executed in different environments and get a report of their execution statuses. Besides a graph, there is a table in which you can get the count and percentages of the test cases according to their status. Also, you can select your desired cycles for comparison too.

Steps to generate a Cycle Comparison Report:

1. Go to “Reports”.
2. Go to “Cycle Comparison Report”.
3. The cycle comparison report will be displayed.

A test case traceability report encompasses the following: your test cases, their execution, and the defects associated during the test runs/cycles. Kualitee has now implemented the feature of a test case traceability report, letting you extract a report related to your test case execution in multiple test runs/cycles and their associated defects. You can also export the generated report in xlsx. format. 

Follow these steps to extract a test case traceability report: 

• Go to the Reports section. 

• Click on “Test Case Traceability”. 

• Apply filters according to your requirement from the left panel, and select the desired columns you want in your report from the right panel. 

• Click on the “Generate Report” button and your report will be generated. 

A Requirement Traceability report encompasses the following: your requirement, test cases associated with those requirements, their execution, and the defects associated during the test runs/cycles. Kualitee has now implemented the feature of a requirement traceability report, letting you extract a report related to your requirement coverage and its test case execution and their associated defects. You can also export the generated report in excel.

Follow these steps to extract a Requirement traceability report: 

• Go to the Reports section. 
• Click on “Requirement Traceability”. 
• Apply filters according to your requirement from the left panel, and select the desired columns you want in your report from the right panel. 
• Click on the “Generate Report” button and your report will be generated.

Test Effectiveness – Test Effectiveness represents critical and major defects in relation to total number of defects for every module.
Team Effectiveness – Team Effectiveness represents rejected defects and defect quality for each team member. Defect quality is percentage of Critical and Major defects in proportion to total defects. 
Test Efficiency – Test Velocity covers the average number of testcases executed per week. 
DEV Team Effectiveness – Development Team Effectiveness is measured through the percentage of resolved defects in comparison to defects assigned. 
Test Execution Coverage – Test Execution Coverage represents test cases against requirement and shows the percentage of the executed test cases with each requirement. 

Kualitee allows you to create roles with certain set of privileges that are provided to keep users under specific job roles. You select and apply privileges to a role and transfer them to a User.

The user then can use the role to perform the task that has been delegated to him under the parameters of his role.

Create Role

Permissions:

Only admin has the option to edit and change permissions of users. You can edit the role name, description and permissions

• Role: Allows you to define the designation for the user being added
• Description: You can add description to the provided role
• Removable: Whether the created role or designation can be deleted.
• Permission: Includes what information the user can view while on Kualitee and actions that he/she can perform.  Permissions include
  • Reports: Whether it can be viewed or not
  • Project Management: Whether it can be viewed or not
  • Dashboard: Whether it can be viewed or not
  • Test Management: Whether it can be viewed or not
  • Bug Management: Whether it can be viewed or not
  • Test Lab: Whether it can be viewed or not

“Users” is a very important feature of Kualitee. Here, Admin can add a list of Users and build their team on the domain. These users can later be assigned to different projects from the project management tab.

• Click on “Settings” tab shown on the dashboard.
• Click on “Users” button.

Create New User

To start adding your team to Kualitee, simply click on ‘Create New User’ and provide brief details, assign each member a role, and select the project you want them to be added to. The roles are domain based which means the user’s level of access will remain the same on every project.

Inactive Users

Users who have been sent the invitation link but have not yet activated their account are listed in the inactive users page.

Under the tab of ‘Email Notifications’ you select what email should be send to which role

Scenarios are:

• Test Cases
• Test Case Execution
• Defect Management

Email notifications are user based. So, we can customize the notifications for each user according to each module.

In case, you require adding more information to your defect reports, test scenario or test case, you can add them through the custom field feature in settings.

Take advantage of the wide array of fields like e.g. Text Box, Text Area, Multiple Selection, and date fields etc.

Create, Edit or Delete:

You can create custom fields by clicking on ‘Create New’ Select your Project and then select the module in which you would like to add the fields.

In “Select Project” select the project in whose module you would like the custom fields to appear.

Select Module the particular module you would like the custom fields to appear. You can create custom fields in your Defects, Test Scenarios and Test Cases.

Name your fields, add description and choose the type of fields you would like to add. You have the option select

• Text Box
• Text Area
• Multiple Selection
• Single Selection
• Date

Once you have inserted all the required information, click on “Create Field” to let it take effect.

The dropdown feature allows you to insert custom values that you require in different fields. Currently, you can add values in different fields in Project Management, Bug Management, Test Scenario and Test Case.

Create, Edit or Delete:

To create a custom dropdown option, go to Settings and select customizations and then choose dropdown.
Here, you’ll see the option ‘Create New’; click on it and you’ll be presented with the page below.

Teamwork is a project and team management software tool that facilitates you to deliver projects on time and on budget. Kualitee’s integration with Teamwork lets you sync Teamwork tasks with Kualitee issues through its two-way exclusive integration. You can link multiple Teamwork projects with Kualitee; whether you create requirements or issues in Teamwork or in Kualitee, you don’t need to switch applications for assignment or tracking.

Create Integration:

To configure the two-way integration between Kualitee and Teamwork, you need admin access on the tools. The integration is basic, with hard-coded field to field mapping.

To Configure:

• Go to Settings and select Integration from the top bar
• Go to ‘Create New’ in the external tool integration listing
• Select Teamwork tool from the drop-down menu
• Enter the details of your Teamwork account

Click ‘Save’ button to confirm a successful integration and to start syncing tasks from Teamwork to Kualitee as Defects.

Go to ‘Edit Integration’ to map the Teamwork task with Kualitee Project.

Map your projects with your Teamwork tasks by selecting the information below.

The basic mapping is a hard-coded field to field mapping between Kualitee and Teamwork. Below is a table that shows the mapping for each field.

Trello is a web-based, Kanban-style, list-making application and is developed by Trello Enterprise. Kualitee’s integration with Trello allows you to sync integrated board cards through its two-way exclusive integration. You can link your Trello board and its cards with Kualitee; you will be able to create cards on Trello and view them as defects in Kualitee, without having to switch applications for assignment or tracking.

Create Integration:

To configure the two-way integration between Kualitee and Trello, you need admin access on the tools. The integration is basic, with hard-coded field to field mapping.

To Configure:

• Go to Settings and select Integration from the top bar
• Go to ‘Create New’ in the external tool integration listing
• Select Trello tool from the drop-down menu
• Enter the Trello App Key, Trello Token, and URL of your Trello account

Click ‘Save’ button to confirm a successful integration and to start syncing tasks from Trello to Kualitee as Defects.

Go to ‘Edit Integration’ to map the Trello board with Kualitee Project.

Map your projects with your Trello board by selecting the information below.

The basic mapping is a hard-coded field to field mapping between Kualitee and Trello. Below is a table that shows the mapping for each field.

Jenkins is an open-source CI/CD tool that helps deliver apps faster by introducing automation at different software development stages. It enables developers to continuously integrate changes into the build. Jenkins’ integration with Kualitee speeds up the continuous delivery processes and consequently, the entire test management cycle. You wouldn’t have to juggle different windows, and can get updated on everything in Kualitee.

Create Integration:

To integrate Kualitee with Jenkins, you have to configure the Jenkins server such that it allows you to sync the Jenkins’ builds from within Kualitee.

• Go to Settings and select Integration from the top bar
• Go to ‘Create New’ in the external tool integration listing
• Select Jenkins tool from the drop-down menu

• Enter details of your Jenkins account

Click ‘Save’ to confirm a successful integration and to start syncing builds.

Once the integration is created, the next step is to map projects.

Under the Jenkins Builds, you will see the list of projects you have in Jenkins. While under Kualitee Project, you will see the list of projects you have on Kualitee.

Map your projects with Jenkins Builds by selecting the information below.

After creating integration and mapping the builds follow these steps to check Jenkins’ jobs and their statuses:

• Go to ‘Project Management’
• Go to ‘Build’
• Click on ‘Jenkins Job’ button
• A pop up will appear on which you can check the status of Jenkins jobs or refresh them. You can also create a new job by clicking ‘Create Job’.

ClickUp is a cloud-based collaboration and project management tool that caters to businesses of all sizes and industries. Kualitee’s integration with ClickUp allows you to sync tasks through its two-way exclusive integration. You can link multiple ClickUp Lists with Kualitee; you will be able to create tasks on ClickUp and view them as defects in Kualitee, without having to switch applications for assignment or tracking.

Create Integration:

To configure the two-way integration between Kualitee and ClickUp, you need admin access on the tools. The integration is basic, with hard-coded field to field mapping.

• Go to Settings and select Integration from the top bar
• Go to ‘Create New’ in the external tool integration listing
• Select ClickUp tool from the drop-down menu
• Enter the Personal Access Token and URL of your ClickUp account

Click ‘Save’ button to confirm a successful integration and to start syncing tasks from ClickUp to Kualitee as Defects

Go to ‘Edit Integration’ to map the ClickUp lists with Kualitee Projects.

Map your projects with ClickUp lists by selecting the information below.

The basic mapping is a hard-coded field to field mapping between Kualitee and ClickUp. Below is a table that shows the mapping for each field.

With Kualitee-Azure, you will be able to sync issues both ways between the tools. Once you have integrated your Azure and Kualitee projects, auto-sync lets you detect and cross-reference defect activity between both your projects. You can close or change the status, and assign different labels to your issues either in Azure or from Kualitee. Also, you can run your CI/CD pipelines from within Kualitee and check their statuses over here without navigating to Azure. This will help your QA and Dev teams to remain in sync. 

Creating integration: 

To integrate with Azure, you click on ‘create integration’ in settings and choose Azure from the product. Provide your email, token, and domain URL to successfully create domain-level integration. Do not forget to give access to all Azure organizations while creating token. 

Once the integration is created, the next step is to map projects. 

Under the Azure Projects, you will see the list of projects you have in Azure. While in the Kualitee project you will see the list of projects you have on Kualitee. 

The basic mapping is a hard-coded field to field mapping between Kualitee and Azure. Below is a table that shows the mapping for each field. 

GitHub is a widely used development platform. The Kualitee-GitHub two-way integration allows you to sync your issues between both tools. Each GitHub project can be linked with a Kualitee project to sync all the reported issues that exist in both projects. Since it’s a two-way integration, all updates that are made on the issue will automatically get synced, including a change in status, additional comments, and associations changed through Kualitee. 

Create Integration 

To configure the two-way integration between Kualitee and GitHub, you need admin access on the tools. The integration is basic, with hard-coded field to field mapping. 

• Go to Settings and select Integration from the top bar 
• Go to ‘Create New’ in the external tool integration listing 
• Select GitHub tool from the drop-down menu 
• Enter the Personal Access Token of your GitHub account 

Click ‘Save’ button to confirm a successful integration and to start syncing issues. 
 

You can also edit the integration, as shown below.  

The basic mapping is a hard-coded field to field mapping between Kualitee and GitHub. Below is a table that shows the mapping for each field. 

1 – API Introduction

Kualitee Tool allows the execution of the test cases within the tool as well as an API endpoint through which you can execute your own test case and have the result reflected in our Kualitee Tool. To implement this API following pre-requisites must be met:

• A Cycle Must exist in the Test Lab Navigation
• The Test Cases must be assigned to a Cycle for Execution

Once the pre-requisites are met you will have your test cases shown as below in Test Case Execution:

2 – API Implementation

The API Endpoint and the parameters are as below:

API Link:

https://apiss.kualitee.com/api/v2/test_case_execution/change_status

Parameters:

• Project ID *                                                     (* means compulsory)
• Token *
• Status *
• Test Case ID *
• Test Case Name (optional)

You can find all of this information on the Test Execution Page which is the previous image. To find out all the remaining information for the API Execution:

II – JSon ICON

You must first click on the json icon on the test case execution page. To find the json Icon, hover on any of the test case that I show and you be shown the <> icon which contains all the API data you need.

Once you click the json icon a new pop-up will open containing all the relevant information as shown below:

All the pre-requisites that are mentioned before are shown in the above json format. You can find all the information regarding the API URL to the API Parameters all except for the token

2 – API Token

You can find the API Token by clicking on your profile and selecting to generate the API Token.

After clicking on API Token Header, you will be taken to the API Token section where you can revoke or generate a new API Token:

With this the pre-requisite and the parameters that are needed are completed for implementing the api test case.

Post Body:

token=abcdefg&project_id=122333&status=Failed&tc_id[]=123&tc_name=tc_01

III – API Algorithm:

If you are implementing the API in a BDD Cucumber approach, it is recommended that you implement the API in the AFTER hook so it is called after every test case and the relevant information is passed onto the function with the API Call:

OR

You can auto-populate your Test execution result in Kualitee by following steps:

1. Go to Test lab and then Test Case Execution screen
2. Click on Upload Report button and select the type of report from the Report Type dropdown on the pop up
3. Attach the JSON file of your test case execution report
4. Click on “Save” button and it will import your report data into Kuaitee

Kualitee has integrated itself with Redmine. This exclusive two-way integration allows you to sync your issues between Kualitee and Redmine. Each Redmine project can be linked with a Kualitee project to sync all reported issues in both projects. Since its a two-way integration all updates made on the issue will automatically get synched that includes a change in status, additional comments and association changed through Kualitee.

Creating Redmine Integration

To integrate with Redmine, you click on ‘create integration’ in settings and choose Redmine from the product. Provide your email, password, and domain URL to successfully create domain level integration.

Once the integration is created, the next step is to map projects.

Under the Redmine Projects, you will see the list of projects you have in Redmine. While in the Kualitee project you will see the list of projects you have on Kualitee.

The basic mapping is a hard-coded field to field mapping between Kualitee and Redmine. Below is a table that shows the mapping for each field.

Kualitee has integrated itself with Asana. This exclusive two-way integration allows you to sync your tasks as requirements or issues between Kualitee and Asana. Each Asana project can be linked with a Kualitee project to sync all requirements and issues in both projects. Since it’s a two-way integration all updates made on the issue will automatically get synched that includes a change in status, additional comments, and association changed through Kualitee.

Creating Asana Integration

To integrate with Asana, you click on ‘create integration’ in settings and choose Asana from the product. Provide your exclusive access token generated from Asana to successfully create domain level integration.

Once the integration is created, the next step is to map projects.

Under the Asana Projects, you will see the list of projects you have in your Asana instance. While in the Kualitee project you will see the list of projects you have on Kualitee.

The basic mapping is a hard-coded field to field mapping between Kualitee and Asana. Below is a table that shows the mapping for each field.

To send tasks as requirements or issues from Asana to Kualitee, you simply add a tag of “Requirement” or “Bug” against your tasks and it will automatically be synced in the respective module inside Kualitee. You can additionally assign these tasks or issues to your team in either tool.

Kualitee has integrated with GitLab issues and branches. This exclusive two-way integration allows you to sync your issues between Kualitee and Gitlab. Each GitLab project can be linked with a Kualitee project to sync all reported issues in both projects. Since it is a two-way integration, all updates made on the issue will automatically get synced; this includes a change in status, additional comments and association changed through Kualitee. Along with issues, you can also integrate Gitlab branches with Kualitee builds to run Pipelines within Kualitee.  

Creating GitLab Integration

To integrate with GitLab, you click on ‘create integration’ in settings and choose GitLab from the product. Provide your personal access token and domain URL to successfully create domain level integration.

Once the integration is created, the next step is to map projects.

Under the GitLab Projects, you will see the list of projects you have in GitLab. While in the Kualitee project you will see the list of projects you have on Kualitee.

The basic mapping is a hard-coded field to field mapping between Kualitee and GitLab. Below is a table that shows the mapping for each field.

Users in GitLab can also follow the template below to provide additional information for the fields available in Kualitee.

To integrate Kualitee Builds with Gitlab Branches, follow these steps:  

1. Go to ‘Project Management’  

2. Click on ‘Builds’ from the top menu 

3. Hover over the Build you want to map with GitLab branch and click on the Link icon  

4. Select the branch you want to map with selected Build 

5. After mapping Branch, click on the List icon to see the Pipelines of that branch  

6. From the Pipelines pop-up, you can create a new pipeline from ‘Create Pipeline’. You can also refresh the existing pipeline by clicking on ‘Refresh’, and be able to view its name, status, date etc. 

Configurations:

For configuring Selenium, there are some pre requisites for it as under.

• Windows/Mac/linux server/system providing Public IP address to access
• Apache (For HTTP requests) normally we use xamp/wampp for it
• Download Kualitee selenium plugin

Public Ip:

Kualitee product will need a gateway to enter the environment where the scripts are going to execute. For that whatever environment you are using must have a public IP.

Apache:

You will need to have apache server setup, normally we use xampp/wampp for it.

Plugin:

Once Public Ip is ready and you have installed xampp. Go to Htdocs directory
(e.g. /var/www/html on a ubuntu machine and for windows xampp/htdocs/)

Once you are in the right directory, just download and unzip Selenium plugin in htdocs directory as:

Once all these things are done, your apche server is up, you have installed xampp/wampp and in htdocs you have unzip the plugin.

You have to try out the url to know if you are set to move a head as

e.g http://172.27.5.19/KualiteeSelenium/index.php

Syntax is [IP address]:[port if any specific]/pluginName/index.php

If you are not able to see blank page, this means you have connection issue and you need to connect with IT support team of kualitee.

Considering successful configuration,

You have to go to your kualitee application, and settings for jumping on to Integrations tab Now you have to add this url in the integration section and selenium tab as

Once you have pasted the url and saved it without any errors, you are all set with the integrations.

This means you have successfully configured the Integration.

Now lets setup one test case to perform automation

For creating your first automated test script, you will have to follow below steps

• Create a test case and set execution type to be automated on Test Management Tab

• Add your automated test case in any cycle you want to execute
• Go to Execute option and run your test case by clicking execute option

Go to Test Lab and test execution section as

Here is the sample code snippet:

Make sure the driver you are going to use is placed in the server/system configured for automation. Like “C:\\xampp\\htdocs\\kualiteeSelenium\\chromedriver.exe”

Kualitee expects Status as parameter from the user to consider the test case to pass or fail.

Kualitee has integrated itself with one of the most popular tools JIRA. This particular features allows you to stay connected with the development team while doing your planning in Kualitee and sending checked and tested feature information back to your development team. The integration allows both tools to send and receive real time updates as they happen.

For example, if updates are made to certain features and requirements in Kualitee with “Sync Integration tool” those changes are automatically made in JIRA and vice versa. However, certain items and detail components are mapped so that if the product or development team split the progress into several different statuses the other team can monitor and remain updated with the progress.

Creating JIRA Integration

To create the JIRA integration, you click on create integration and choose JIRA from the product. Provide your JIRA admin email and API token with domain URL to successfully create domain level integration.

Once the integration is created, next step is to map projects.

Under the JIRA project, you will see the list of projects you have in JIRA. While, in the Kualitee project you will see the list of projects you have on Kualitee.

You also have the option to choose whether to integrate JIRA Stories with Kualitee Requirements or JIRA Defects with Kualitee Defects, or both.

Basic Mapping

Basic Mapping with JIRA is hard-coded field to field mapping as mentioned in the table below.

Following is the mapping of defect status in Kualitee with bug status in JIRA.

Mapping of priorities is:

• JIRA “Environment” which includes information regarding Browsers/Devices will appear under “Step to Reproduce” in Kualitee.
• Once, Sync integration function is active all the changes e.g. new defects created, updated and deleted will be reflected on either sides.
• Only issues which are classified as bug in JIRA will appear in Kualitee. Issues modified as story, task or epic in JIRA will not appear in Kualitee.
• Changing project name, project type or Re-Indexing the project will affect the integration.

Custom Mapping

Custom Mapping allows you to customize your synchronization with JIRA. You will need to create similar kualitee fields inside JIRA and drop down values so field to field mapping can take place upon sync.

Before you start mapping, make sure that you have completed the following steps:

• Created Custom Fields in JIRA for each field you are trying to map.
• Confirm the Field Type as mentioned in the table below
• Any Custom Value that you have created in Kualitee, is created in JIRA

Do not forget to add the below mentioned(Priority and Environment) fields while integrating defects:

*Note:

1- Till Mapping is not configured basic JIRA Integration will be working
2- This configuration will not affect previous issues. It will only work with Issues created from this point onwards.
3- Build & Module created in JIRA will be created in Kualitee but will not have association with test scenarios and cases etc. To do that you will need to manually edit scenarios and cases or create build and module in Kualitee to maintain the association.
4- Any custom value created in JIRA will automatically be created once synced with Kualitee but any Custom value added in Kualitee will not be available inside JIRA. It will need to be created.
5- In case of Integration fail, make sure that field type and value you are mapping is available in JIRA.