No Bugs Found in Dashlane SaaS
Dashlane
Dashlane is a robust, user-friendly platform designed to secure and simplify digital life. It masterfully combines critical online security tools with a range of convenience-focused features.
This application intuitively manages passwords, secures personal data, and streamlines online transactions. Its digital wallet feature also allows effortless auto-filling of online forms, which is both convenient and time-saving.
As the QAwerk team, we conducted a comprehensive Bug Crawl on Dashlane and found no issues affecting its performance and user experience. Our testing confirmed the platform’s reliability, data integrity, and efficiency in various scenarios.
3
browsers used
24
hours spent testing
>100
test cases run
0
bugs found
No bugs found when detecting breached emails and providing recommendations
Precondition:
- The user has at least one monitored email added.
- External service is available for checking breaches.
Steps to Reproduce:
- Add an email known to be leaked in a past breach.
- Verify if Dashlane detects compromised email.
- Check if relevant recommendations appear for securing the account.
- Remove the email and add it again to check if detection remains consistent.
- Attempt to add the same email multiple times and verify if duplicates are handled correctly.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
Dashlane detects breached emails and provides appropriate recommendations.
Duplicate entries are prevented.
Actual Result:
Bug not found.
Dashlane detects breached emails and provides appropriate recommendations. Duplicate entries are prevented.
Precondition:
The user is logged in and has no monitored emails added.
Steps to Reproduce:
- Add emails one by one until the system reaches the limit.
- Attempt to add one more email beyond the limit.
- Observe system response.
- Check if already monitored emails can be removed and replaced smoothly.
- Try adding the same email under different capitalization formats (e.g., [email protected] vs. [email protected]) and verify uniqueness constraints.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
The system enforces the maximum limit.
Duplicate email variations are prevented.
Overflow is handled properly.
Actual Result:
Bug not found.
No bugs found when verifying persistence of collections and stored items
Precondition:
The user is logged in and has at least one collection created.
Steps to Reproduce:
- Create a new collection and add multiple test items.
- Log out and log back in.
- Verify that the created collection and stored items are still present.
- Refresh the page while editing a collection and confirm data consistency.
- Delete a collection, log out, and check if deletion remains effective after re-login.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
Data persists correctly after logout/login and refresh actions.
Deletions remain effective.
Actual Result:
Bug not found.
No bugs found when attempting to add payment method
Precondition:
The user is logged in on the platform.
Steps to Reproduce:
- Navigate to the Payments setup page.
- Click the “Add new” button.
- Fill in all input fields.
- Click the “Save” button.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
The payment method is successfully created.
Actual Result:
Bug not found.
The payment method is successfully created.
Precondition:
The user has stored at least five login credentials in Dashlane.
Steps to Reproduce:
- Add five strong, unique passwords and observe the score.
- Change one password to weak and observe the impact on the score.
- Modify all passwords to be identical and check the detection of reuse.
- Delete stored passwords and verify if the score resets correctly.
- Try adding a very long but simple password (e.g., aaaaaaaaaaaaaaaaaaaaa) and check classification.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
Password health score dynamically reflects strength, reuse, and deletion correctly.
Actual Result:
Bug not found.
No bugs found when testing secure data export functionality
Precondition:
The user has stored multiple credentials, notes, and monitored emails.
Steps to Reproduce:
- Navigate to “Settings” → “Export Data.”
- Export data in different formats.
- Select Export to CSV.
- Enter Master Password.
- Open the exported file and verify data accuracy.
- Modify exported data and attempt to re-import it.
- Check if Dashlane prevents importing tampered files.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
Exported data is accurate, and modifications are detected on re-import.
Actual Result:
Bug not found.
BUG EXAMPLE:
No bugs found when verifying VPN upgrade flow
Precondition:
The user has a free Dashlane account without VPN enabled.
Steps to Reproduce:
- Click the “Upgrade” button under VPN.
- Complete upgrade/payment process.
- Verify if the system correctly upgrades the user’s account.
- Attempt to downgrade and confirm refund policies/downgrade options.
- Check if the VPN connection is functional post-upgrade.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
VPN upgrade is processed correctly.
Downgrade/refund policies are properly handled.
Actual Result:
Bug not found.
No bugs found when testing import function with malformed credential files
Precondition:
The user has access to the import logins feature.
Steps to Reproduce:
- Prepare a CSV or JSON file with valid credentials.
- Import file and verify successful parsing.
- Modify the file by introducing syntax errors/malformed data.
- Attempt to re-import and check if the system properly handles errors.
- Observe if misleading data results in incorrect imports (e.g., swapped username/password fields).
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
The system rejects malformed data.
Incorrect logins are prevented from being imported.
Actual Result:
Bug not found.
No bugs found when validating session management on multiple devices
Precondition:
The user has access to multiple browsers or devices.
Steps to Reproduce:
- Log in to Dashlane on Browser A.
- Log in again on Browser B and observe if the first session remains active.
- Manually log out from Browser A and check if Browser B is affected.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
Sessions are handled properly.
Logout behavior is consistent.
Actual Result:
Bug not found.
Sessions are handled properly. Logout behavior is consistent.
Precondition:
The user has access to the Dark Web Monitoring feature.
Steps to Reproduce:
- Rapidly add/remove multiple emails in quick succession.
- Check if the UI updates correctly without delay.
- Observe if API requests fail or rate-limiting mechanisms trigger.
- Verify that the removed emails do not appear after refreshing.
- Attempt to re-add a previously deleted email and check for inconsistencies.
Environment:
Chrome 131.0.6778.264
Safari 18.1.1
Firefox 130.0.1
Expected Result:
The system handles rapid modifications efficiently.
Inconsistencies are prevented.
Actual Result:
Bug not found.
I tested Dashlane's security, performance, usability, and load handling under various conditions. The system performed well in most cases, but optimizing mass operations and UI update speed during rapid modifications would make the experience even smoother.
No Bugs Found!
We tried to find bugs in this product but failed to spot any. While we still believe no software is 100% free of bugs, this app contains no critical or apparent defects that could negatively impact the user experience. 
