Bugs found in Qlerify SaaS

Qlerify

Qlerify is an AI-powered business process modeling tool that enables digital transformation teams to map, analyze, and optimize enterprise workflows quickly. By combining process discovery, compliance checks, and real-time collaboration in a single platform, Qlerify reduces the complexity of modernization efforts and offers clear insights for every stakeholder.

With Qlerify, organizations can swiftly identify bottlenecks, automate routine tasks, and maintain regulatory alignment throughout their transformation journey. The result is a more efficient, adaptable operation that supports continuous improvement and empowers teams to meet evolving business demands.

The QAwerk team performed a meticulous Bug Crawl on this SaaS application, identifying several issues that may impact performance and user satisfaction. Below are the results of our thorough investigation, complete with detailed steps to reproduce each bug.

Incorrect behavior observed during lane deletion in workflow with start point

Severity:

Critical

Precondition:

An empty Workflow has been created.

Steps to Reproduce:
  1. Add four lanes: lane1, lane2, lane3, and lane4.
  2. Insert a start point in lane1.
  3. Insert a start point in lane3.
  4. Click the delete button for lane2.
  5. Click the delete button for lane3.
Environment:
  • OS: Windows 10
  • Browser: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
  • Lane3 is not deleted.
  • Buttons from the bottom panel move upward into lane4.
  • Delete buttons on lanes become invisible when hovered over.
  • Adding a new lane unexpectedly renames lane1 to lane3.
Expected Result:
  • Lane3 should be deleted without issues.
  • The buttons in the bottom panel should maintain their position in lane4.
  • Delete buttons remain visible and functional on hover.
  • Adding a new lane does not cause existing lanes to be renamed.

Erratic scroll behavior while dragging start point across lanes in Workflow

Severity:

Major

Precondition:
  1. A new Workflow is created.
  2. Enough lanes have been added to activate a scrollbar.
Steps to Reproduce:
  1. Click “Add Start Point.”
  2. Press and hold the left mouse button on the added card.
  3. Attempt to scroll with the mouse wheel while dragging the card.
Environment:
  • OS: Windows 10
  • Browser: Chrome 127.0.6533.89
Actual Result:

The page scroll behaves erratically, often snapping back to its original position.

Expected Result:

The page should either scroll smoothly when the mouse wheel is pressed while dragging the card or disable scrolling entirely during the drag.

Incorrect workflow count displayed on project card after creating new workflows

Severity:

Major

Precondition:

The user is logged into their account.

Steps to Reproduce:
  1. Create a new project.
  2. Open the recently created project.
  3. Create multiple workflows in this project.
  4. Click on the home icon to return to the main page.
Environment:
  • OS: Windows 10
  • Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:

The project card in the Recent Projects section shows an incorrect number of workflows.

Expected Result:

The project card should display the correctly updated number of workflows.

“Delete Group” button in Workflow overlapped by scrollbar

Severity:

Major

Precondition:

Any Workflow is open.

Steps to Reproduce:
  1. Click the “Add Group” button.
  2. Click “Add Group” again to create a second group.
  3. Locate the “Delete” button for Group 2.
Environment:
  • OS: Windows 10
  • Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:

The scrollbar obscures the “Delete” button for Group 2 at the end of the group column header.

Expected Result:

The “Delete” button for Group 2 should be fully visible and not overlapped by the scrollbar.

Interface text wrongly underlined as misspelled on clicking “Add Start Point” button

Severity:

Minor

Precondition:

A Workflow interface is open.

Steps to Reproduce:

Click the “Add Start Point” button.

Environment:
  • OS: Windows 10
  • Browser: Firefox 128.0.3
Actual Result:

All interface text appears underlined in red, akin to a spell-check highlight.

Expected Result:

No spell-check or red underlining should appear on interface text.

Reset of fefault Workflow name after page reload

Severity:

Minor

Precondition:

The main page is accessible.

Steps to Reproduce:
  1. Click “New Workflow.” The default name “Workflow 1” appears.
  2. Click “Add.”
  3. Click “New Workflow” again. The default name “Workflow 2” appears.
  4. Click “Add.”
  5. Click “New Workflow” again. The default name “Workflow 3” appears.
  6. Click “Add.”
  7. Reload the page.
  8. Click “New Workflow.”
Environment:
  • OS: Windows 10
  • Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:

The default workflow name reverts to “Workflow 1” after a page reload.

Expected Result:

The naming should continue from the last created workflow (e.g., “Workflow 4” after three prior workflows).

I uncovered multiple UI and functional issues that could hinder the workflow management experience in Qlerify. Streamlined testing across various browsers and proper handling of user interactions can significantly improve stability and user satisfaction.
Stanislav, QA engineer

Stanislav, QA engineer

Need a reliable QA partner?

Hire us