- Client
- Workflo
- Industry
- SaaS · Project management & collaboration
- Engagement
- 2022 – 2024 · 2 years
- QA team
- 3 full-stack QA engineers + 10+ on-demand QA engineers
- Platforms
- Websites · Mobile Web · Chat Platform · API · Database
- Manual Testing
- Integration Testing
- Usability Testing
- UI/UX Testing
- Cross-browser Testing
- SaaS Product Testing
- Performance Testing
- VAPT
Trello
Google
PostgreSQL
Postman
JMeter
About the project
Workflo is a lightweight, all-in-one project management and team collaboration platform, launched to end the chaos of switching between separate tools for tasks, chat and files. Teams plan projects, assign and track work, discuss it in real-time chat and keep everything in one workspace, on desktop and mobile browsers.
All-in-one means everything is connected. A task update must appear in the right channel, a mention must notify the right person, and permissions must hold across workspaces, projects and conversations. Real-time chat adds concurrency, delivery and ordering problems that ordinary web testing rarely touches.
QAonTOP supported Workflo from 2022 to 2024 with three full-stack QA engineers as the core team, plus 10+ on-demand QA engineers brought in for release crunches, exploratory sprints and large-scale usability rounds.
What made this hard
A collaboration tool earns trust by being reliably unremarkable. Messages have to arrive, tasks have to stay in sync and private work has to stay private — for every team, at every size.
- CHALLENGE 01
Real-time chat at scale
Messages, reactions, threads and mentions had to arrive instantly, in order and exactly once, even with many people typing in the same channel.
- CHALLENGE 02
Everything linked to everything
Tasks, projects, chat and notifications share one data model. A change in one area regularly surfaced as a bug in another.
- CHALLENGE 03
Permissions across workspaces
Guests, members and admins across workspaces, projects and private channels — every combination had to show exactly the right data and nothing more.
- CHALLENGE 04
Fast growth, fast releases
Frequent releases and new features meant regression grew faster than a small team could run it by hand before launch days.
How QAonTOP tested Workflo
- 01
Build a feature map and risk plan
Mapped every module — workspaces, projects, tasks, chat, notifications, files and settings — tracked coverage and defects in Trello, and shared test plans and release reports through Google Workspace.
Tools Trello · Google
- 02
Test the connections, not just the features
Integration scenarios followed data across modules: a task created from chat, a status change notifying followers, a mention in a thread opening the right item. Postman checked the APIs behind each step and PostgreSQL confirmed the stored result.
Tools Postman · PostgreSQL
- 03
Scale up with on-demand testers
Before major releases, 10+ on-demand QA engineers joined the core team for structured exploratory sessions, cross-browser sweeps and usability rounds, with every finding merged into one Trello board.
Tools Trello
- 04
Security and permissions (VAPT)
Vulnerability assessment and penetration testing of authentication, session handling, workspace isolation and role permissions, with database checks confirming no data crossed workspaces.
Tools PostgreSQL · Postman
- 05
Load the chat, measure the app
JMeter tests for concurrent users, message bursts and busy boards, plus response-time baselines for the APIs behind task lists and chat history.
Tools JMeter
The engagement in numbers
Engagement from build to scale
QA engineers at peak: 3 core, 10+ on demand
Test cases across tasks, chat, projects and admin
Defects found and verified before release
Shorter pre-release regression window
Platforms covered, from web and chat to API
Before and after the engagement
| Area | Before QAonTOP | With QAonTOP |
|---|---|---|
| Release testing | A small team re-running everything by hand before each launch. | The core team plus on-demand testers covering full regression and exploratory sessions in parallel. |
| Cross-module bugs | Found by users when a change in tasks broke chat or notifications. | Integration scenarios that follow data across modules on every release. |
| Chat reliability | Message order and delivery checked by a couple of people chatting. | Scripted concurrency tests and JMeter message bursts with delivery and ordering checks. |
| Permissions & security | Role and workspace rules assumed from the UI. | VAPT and permission matrices, with database checks for workspace isolation. |
| Performance | Slowdowns reported by large teams. | JMeter baselines for concurrent users, busy boards and chat history. |
| Defect tracking | Bugs spread across chats and documents. | One Trello board with severity, reproduction steps and an owner for every finding. |
What we covered
Manual Testing
Exploratory and scripted testing of workspaces, projects, tasks, chat and settings.
Integration Testing
Scenarios that follow data between tasks, chat, notifications and the API.
Usability Testing
Large-scale usability rounds with on-demand testers who were new to the product.
UI/UX Testing
Screen and interaction checks across boards, task views and chat against design.
Cross-browser Testing
Desktop and mobile browser sweeps for every major release.
SaaS Product Testing
Workspace setup, plans, roles and account lifecycle across the SaaS platform.
Performance Testing
JMeter load tests for concurrent users, message bursts and busy boards.
VAPT
Security testing of authentication, sessions, roles and workspace isolation.