---
source_url: "https://www.deviqa.com/case-studies/weheartit/"
title: "QA for image-based social network | DeviQA case study"
mirrored_at: 2026-08-09T03:33:54.418Z
host: www.deviqa.com
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/www.deviqa.com/case-studies/weheartit/index"
---

> **Original source:** https://www.deviqa.com/case-studies/weheartit/

Our key task was to cover 95% of the application with automated tests to quickly and reliably answer the question: 'Can we deploy?'

Firstly, we had to design a test suite architecture that would allow us to run tests in dozens of threads on 6 different browsers. At the same time, we developed atomic scenarios to avoid collisions during the execution of parallel tests. We considered using an API to speed up duplicated activities and the creation of entities before testing through the database.

As there was no formal QA process on the project, we needed to design and set it up, as well as familiarize the rest of the team with it.

We developed quite a complex environment to run automated tests for this project. We were provided with a 64GB RAM dedicated server, on which we set up and ran 15 virtual machines. Three browsers were running in parallel on each VM. In general, our tests were run on 40-45 browsers in parallel. Due to multi-threading, we reduced the time needed to run all 2000 scenarios from 12 hours to 2 hours. As a result, the team was able to answer the ‘Can we deploy?’ question more quickly.

Tests were run on 6 different browsers and their different versions. We also integrated our web automation tests with bug tracking and team management systems. So, on test completion, detected bugs were automatically logged on the BTS side, and the corresponding test cases were marked as failed/passed for a specific test run.

The statistics about all test runs were stored on the CI side, so we could always see the history of our builds. At the end of each test run, a test report with detailed information about passed/failed scenarios was sent out.