Automation Testing (SaaS).
Take your testing to the next level.
Our team collaborated with a scriptless and automated testing software company to revamp their product and make it more user-friendly.
Type
Web App - SaaS
Our Services
Design & Development
Industry
Script-less automation testing
Duration
6 Months
Established nearly 8 years ago, our client has efficiently launched several software testing services and capabilities, all rolled into one web app. The software helps its users (Testors & Testing managers) create, record, and execute test cases in various environments and devices.
Simplify the testing process: We did a thorough audit to find pain points in user experience throughout the product.
The app architecture was a maze. Things were not easy to find.
Unclear features & functionalities created a lot of anxiety in users if they would do something that could go wrong and jeopardize the whole team project.
User flows could have been shorter. Users needed to take needless steps before achieving any objective.
Introducing a design system
The product did not have a design system. The components and UI were built at random and lacked consistency.
Our aim in introducing a design system was not only to bring consistency & user-friendliness into the product. But also to build the product with better coding practices. We wanted to implement better architecture in code, use of reusable components, and code for scalability.
To design the right thing
We defined problems and their roots.
Solutions, change over time. It is not a good approach if you come up with features and solutions directly without defining a problem. We often consulted our clients the same.
From a bird’s point of view - We designed holistically.
When a solution was pitched, we brought in a holistic view. We carefully considered each platform user (Reviewers, managers, testers, admins, etc.), different use cases, and how they might be affected.
We tried to eliminate noise from the screen to keep users in the zone.
A bunch of information and action items present at once fought for attention. We needed to master information delivery. A practice I followed to minimize information overload was to group information into 2 parts.
Information that must be present at all times
Information that can be given to users once they request it by performing an action.
Kept users, domain experts, and product teams of our client involved in the process.
Before revamping any feature/module/section of our tool, we would first meet with the domain experts to understand the value proposition and its importance in the product. We would then audit the flows and observe the users to find pain points. We would scope things we can solve now and things that should be kept aside to solve later. Get feedback, design, and deliver.
sm fdjelkflkm dklfl