RestQA Introduction
RestQA automation framework enables the simplest way for database microservice testing. The uniqueness of this particular design is in gamification of the process with a more entertaining user experience, a lesser work fatigue, a very reduced learning curve and increased QA productivity.
Pain points - hindrances of various categories in the whole software testing process experienced by the QA department. The primary pain points compiled here prioritize the areas of interaction with the test framework that have been identified as the most impairing the QA team productivity.
Team Dynamics - pain points related to the interaction between the QA with development and management departments.
Framework optimization - pain points experienced due to the work volume when using the current QA platform.
Time Management - considerations pertaining organization of the QA department so that to accelerate the test process.
Workflow Optimization - considerations besides the framework design that would make the QA process more efficient.
Empathy Map - inferences based on the interviewing data representing a snapshot of the user's thoughts and feelings.
User Journey - we visualized the hypothetical events that would motivate to seek a gamified test framework and lead to the discovery of Rest QA.
Prioritizing for MVP - the posted interview findings have been reduced to the scale of a minimal viable product and grouped by precedence.
Improvement Kata - we produced this as a guide with the short and long term goals in the incremental design process of each major release.
Backlog - we maintained this as a more detailed guidance list of features or technical tasks that were necessary to complete the design phase.
User Flow - we produced these artifacts to determine the minimal viable product flow for the BA and QA user type.
UI Prototype - initially we designed the minimal set of MVP features necessary for its basic mode of operation. The basic mode of operation allows the user to operate this application without the low level script.
UI Prototype - secondarily we designed the minimal set of MVP features necessary for its advanced mode of operation. The advanced mode of operation allows the user to operate this application through the low level script.
