The KeyTrust test system was developed to modernize and streamline the company's manual testing capabilities by transitioning from Excel sheets to a bespoke online web application. This platform enabled the test team to efficiently and scalably manage test cases and runs for the company's current and future products.
Software development company, KeyTrust had been working on releasing their most comprehensive version of HealthSphere, a telehealth video conferencing platform that facilitated services between rural Australia and city based specialists. Their next release required more complex workflows their current manual test system couldn't keep up with.
Initially the test lead wrote and maintained test cases in a single Excel spread sheet. At the start of each new test run, a fresh sheet containing the cases would be shared with all testers. During the test run any reported defects would be noted within the sheet. This solution had become overwhelmingly tedious and had poor scalability.
Subsequently the team tried Lean Testing, an online web application that was used for 6 months. This solution was deemed unfit when the system started experiencing outages unexpectedly. Shortly after, Lean Testing announced it could no longer afford its server costs and stopped offering the system. The test team were suddenly left with no suitable platform in the middle of the software development cycle.
Working closely with the test lead and development team, we determined a bespoke in-house solution was the best path forward. An internal web application would protect against the system becoming unexpectedly unavailable again and address existing usability pain points affecting test run efficiency. I began the design of the new web application.
With the introduction of synchronous data, team members can seamlessly follow test run progress and see changes to case statuses by relying on automatic push updates.
The test team no longer has to switch between the test system and project management software when conducting a test. By using the Report Bug function, any team member can submit a bug and create a task within the PMS at the same time. Additional data such as comments, file uploads and even bespoke system fields, such as the task assignee, priority and task status can be populated by using PMS APIs.
At the request of the test team, a dark user interface was used alongside a brand appropriate colour palette. Early on in the projects research phase, many of the test team complained that they found starting at the previous light and bright UI's taxing. This overhaul in UI aims to reduce headaches and tiredness that come with eye strain during long test runs.
The KeyTrust Test System transformed the testing process, reducing test run times from up to five days to just two or three. Features like integrated bug reporting and real-time updates kept the team synchronized, eliminating inefficiencies that had plagued previous tools. Testers could now add or edit test cases in just 10 seconds - a dramatic improvement from the 30-60 seconds required in Excel or LeanTesting. Bug reporting became faster and easier, taking only 30-45 seconds compared to the lengthy, tool-switching process of the past. The result? A 100% satisfaction rate from the test team, who praised the system's reliability, seamless workflow, and freedom from the frustrations of outdated tools.
The system was adopted immediately by the test team and has been in active use since deployment. A future version is planned to support automated test runs.
This case study includes a full walkthrough of the research, design and prototyping process.
Interviews were conducted with the relevant stakeholders from within the company. As the primary users of the existing solution, data was predominantly collected from the test lead & other members of the test team. Key data points obtained:
A cursory competitive analysis was conducted to ensure there was no suitable existing market solution. Upon completion it remained clear that a bespoke in-house solution was the most appropriate way forward.
User personas were created as reference points for evaluating ideas and decisions during the design process and stakeholder conversations. This was particularly helpful when creating the product map, as each persona represented real team member needs when prioritizing features.
To kickstart the Ideate phase, I created a Release Feature Map for the solution to determine the initial feature set. To better understand the overall system structure needed for desired functionality, I developed a sitemap and a system-wide task flow diagram that outlined the entire solution.
The basic structure and layout of the new test system began to come together as I created the low-fidelity wireframes. By adding user flow data to the designs I was able to conduct initial usability testing. Each member of the test team was asked to perform the basic functions using the wireflow. Most task flows were completed without difficulty and only minor adjustments were required.
Prior to the high fidelity wireframes, I put together a UI kit containing reusable elements. These components helped create consistent, visually appealing interfaces.
Using Adobe XD, I transformed the basic structure and workflow of the low-fidelity wireframes into high-fidelity designs of the product. Once complete, a design review meeting was held with the relevant stakeholders. Any agreed-upon amendments were then incorporated into the designs in an iterative process.
During the design process, several critical iterations were completed based on usability testing and stakeholder feedback. These iterations addressed key challenges and enhanced the functionality of the test system, ensuring it met the needs of both testers and test leads. Below is a summary of the most impactful changes.
Before the development phase began, the solution was presented to the development team. This gave the engineers an opportunity to request clarifications before coding began. To mark an end to the design process, a full set of wireframes and design notes were made available. As the development phase commenced, my role in the project transitioned to front-end developer. I worked alongside the software team building out the front-end of the web application. A benefit of working alongside the developers was the opportunity to readily provide clarification on the product design and workflow.
