Home

Case studies

Platform for interface design and prototyping

Software testing services for web design tool

The way we leveled up the quality of an innovative app for design and prototyping.

>700

Regression test cases created

>300

Test cases created for new features

>150

Bug reports created

~400

Feature/bug tickets processed

About project

Framer is an industry-leading platform for interface design and prototyping. With powerful tools and an intuitive interface, Framer simplifies and streamlines the process of creating interfaces and animations. It provides a wide range of features, including the ability to work with visual elements, dynamic animations, and, for more experienced users, the option to work with code to create more complex and customizable components and animations. Additionally, it supports integration with popular design systems like Sketch and Figma, enabling easy import of graphical resources.

Before DeviQA

There were no dedicated QA engineers, and testing was executed by developers
Many bugs were overlooked during testing, which affected the user experience
Bug reports were uninformative
There was a lack of test documentation
There was poor communication within the team

With DeviQA

A professional QA engineer took under their control the testing of existing and upcoming features
~50% reduction in the number of post-release bugs was achieved
Informative and well-structured bug reports were created, helping to simplify and speed up bug fixing
Regression and smoke test suites were written from scratch
~70% of the functionality was covered with regression tests
~90% of the new features were covered with test cases
Efficient communication was established between the development/PO team and the QA engineer

Our contribution

Team

1 manual QA engineer

Project length

1 year

Technologies and tools

GitHub

TestRail

DevTools

CircleCI

Figma

Sentry

Our engagement

Before the DeviQA engineer came on board, there was no dedicated QA team; developers handled all testing. Our engineer began by reviewing the available project documentation and the existing development process. After that, they compiled a list of recommended changes to establish an efficient QA process and discussed it with the client. Also, our QA engineer defined key priorities: testing new features, creating test documentation, and covering both new and existing functionality with test cases.

A comprehensive test documentation was written. Initially, we created a smoke test suite and then a regression test suite. This allowed us to cover over 70% of the existing features and 90% of the new features with test cases. These test suites were regularly updated and expanded.

Additionally, we refined the approach to bug reporting. By creating detailed and clear bug reports, we empowered developers to understand issues better and address them more efficiently. Overall, it facilitated a faster bug-fixing process.

The efficient QA process that we established allowed Framer to significantly improve the quality of the application. The number of post-release issues was reduced by approximately 50%, reflecting the effectiveness of our QA efforts.

Services provided

Web testing

The DeviQA engineer wrote detailed regression test cases, covering over 70% of the web application. By regularly executing tests and promptly documenting any identified bugs, our QA engineer played a pivotal role in improving release quality, reducing the number of client-reported issues, streamlining a bug-fixing process, and boosting the overall productivity of the development team.

Mobile testing

The DeviQA engineer developed a comprehensive test suite, encompassing key areas of the application across all platforms. This proactive approach allowed them to identify and address potential regression issues, ensuring consistent product quality.

Dedicated QA team

Our QA engineer created extensive test suites covering all application areas and platforms, ensuring early issue detection and maintaining top-notch product quality while minimizing post-release bugs. Additionally, our QA engineer participated in various meetings, establishing efficient communication with the rest of the team.