Bugs found in Knack SaaS
Knack is an innovative online platform streamlining database software and business application development.
Its user-friendly environment makes it particularly accessible to those without extensive coding experience, allowing them to develop solutions for CRM, project management, and more. With a range of tools to manage data, automate workflows, and integrate third-party services, Knack helps businesses operate more efficiently.
Our QAwerk team performed an in-depth Bug Crawl on Knack to identify any issues that could compromise performance or user satisfaction. Below are the main bugs discovered, along with recommendations to enhance reliability and ensure a smooth experience for all users.
Invalid Password is not validated in “Edit Record” modal for Sales Reps table
Severity:
Major
Precondition:
A record exists in the Sales Reps table (e.g., [email protected]) with a weak password.
Steps to Reproduce:
- Go to the “Data” tab.
- Select the “Sales Reps” table.
- Click on the “Password” field for the [email protected] record.
- Press “Submit” and note the error about a weak password.
- Click the “Edit” (pencil) icon for the same record.
- Observe that the weak password is still displayed in the modal.
- Press “Submit” in the modal.
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
The modal closes without showing a weak password error.
Expected Result:
The password should be validated, and an error message should appear if it does not meet strength requirements.
Default value for numeric field allows textual input
Severity:
Major
Precondition:
The user is logged in and has access to the “Data” section.
Steps to Reproduce:
- Navigate to the “Data” tab.
- Select the “Contacts” table.
- Click “Add Field.”
- Choose “Number” as the field type.
- Enter “test text” in the “Default Value” field.
- Click “Add Field.”
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
A numeric field is created with a textual default value.
Expected Result:
The field type should be strictly validated, rejecting non-numeric inputs in the default value field.
Uploading .JFIF format image results in “Not a valid image” error upon saving
Severity:
Major
Precondition:
The user is logged in and on the Profile Settings page.
Steps to Reproduce:
- Go to the Profile Settings page.
- Click “Upload” in the Profile Photo section.
- Choose a .jfif image.
- Verify that the .jfif image appears in the preview.
- Click “Save.”
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
An error message appears: “Not a valid image, only PNG and JPEG are allowed.”
Expected Result:
The system should either block .jfif files from being uploaded initially or display the error before the upload completes.
Alternatively, .jfif files could be recognized if the format is deemed acceptable.
No error message for unsupported .gif file format during drag-and-drop
Severity:
Minor
Precondition:
The user has logged in and is on the Profile Settings page.
Steps to Reproduce:
- Go to the Profile Settings page.
- Drag and drop a .gif file onto the Profile Photo upload section.
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
No error message is displayed, and the file fails to upload.
Expected Result:
The system should notify the user that .gif files are not supported.
No error message when selecting unsupported .gif file from dialog
Severity:
Minor
Precondition:
The user is logged in and on the Profile Settings page.
Steps to Reproduce:
- Go to the Profile Settings page.
- Click “Upload Image” in the Profile Photo section.
- Select a .gif file using the file dialog.
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
The system provides no feedback, and the file is not uploaded.
Expected Result:
An immediate error message should inform the user that the .gif format is unsupported.
“Sign Up” button incorrectly displays as “Sign in as [Google account name]” on registration page
Severity:
Minor
Precondition:
The user has a Google account that is not registered on Knack.
Steps to Reproduce:
- Log into a Google account that is not registered with Knack.
- Go to the Knack login page.
- Attempt to sign in with the unregistered Google account.
- Notice the error stating the account is not registered.
- Proceed to the registration page.
Environment:
OS: Windows 10
Browsers: Chrome 127.0.6533.89, Firefox 128.0.3, Edge 127.0.2651.86
Actual Result:
The registration page displays the button text “Sign in as [Google account name],” which can be confusing.
Expected Result:
The button should say “Sign up” or similar phrasing, prompting new users to register.
![“Sign Up” button incorrectly displays as “Sign in as [Google account name]” on registration page](https://bugcrawl.qawerk.com/wp-content/uploads/2025/01/1_firefox.png)
I identified multiple UI and validation issues across various sections of the Knack platform. Tightening these validation checks and performing thorough regression testing after each update would significantly improve user satisfaction and trust in the application.
