1. Home
    2. /
  2. Case studies
    3. /
  3. Agorapulse

QA services for social media management platform

Implementing scalable test automation for a SaaS platform.

QA services for social media management platform

Technologies and tools

Shortcut

Testmo

TypeScript

Playwright

GitHub Actions

Team

2 automation QA engineers (1 automation QA engineer from April 2026)

Project length

Since 2025

1.6k+

Automation test scripts created

~4

Hours regression run duration

90%

Automation coverage for regression testing

About project

Agorapulse is an all-in-one social media management platform. With its help, businesses, marketers, and digital agencies can easily manage multiple social media accounts from a single dashboard without switching between different platforms. Users can schedule posts, respond to messages, monitor brand mentions, and analyze performance across Facebook, Instagram, LinkedIn, X (Twitter), and other networks.

Focusing on automation, collaboration, and data-driven decision-making, the platform offers such features as a unified social inbox, content publishing calendar, social listening tools, and advanced analytics reports.

Agorapulse is designed to help businesses build a stronger online presence, improve customer communication, and make smarter marketing decisions based on real data.

Without DeviQA

  • Inefficient Cypress-based automation solution with unmaintained and outdated tests

  • Time-consuming manual regression testing

  • Only 15% of tests were automated

  • Manual regression testing was executed before releases

With DeviQA

  • Modern Playwright-based automation solution with reliable tests

  • Automated regression testing, which runs in 3 hours only

  • 90-95% of tests are automated

  • Release validation is based on objective results of automated testing

Our engagement

When we joined the project, there was only one AQA engineer on the team who couldn’t address all QA activities properly because of the lack of bandwidth.

Regression testing was executed manually, though there was a small set of automated tests implemented in Cypress. As those test scripts were not maintained, they were unstable and unreliable. CI pipelines were not configured for the automation framework. All in all, there was no proper automation strategy in place.

Our goal was to refine the whole QA process, and we achieved this in several phases.

Phase 1
Setting the foundation for process rebuild

We started by reassessing the existing automation approach and quickly identified that maintaining the legacy tests would be inefficient. Instead, we made a strategic decision to rebuild the automation suite from scratch.

A new automation solution based on Playwright and TypeScript was created. It focused on scalability, readability, and long-term maintainability.

At this stage:

  • The basic automation architecture was designed and implemented.

  • Key testing standards and practices were introduced.

  • An additional AQA engineer joined the team to support faster development of the new suite.

Phase 2
Stabilizing foundational QA

With a new test automation solution in place, we could focus on stabilizing AQA processes and ensuring reliable coverage of the most critical system parts.

At this phase:

  • A test management system was introduced to ensure structured storage and maintainability of test cases and provide a dedicated board to streamline tracking and prioritization of AQA activities.

  • Critical user flows were fully automated.

  • Flaky and outdated tests were eliminated.

  • The automation suite became stable enough for routine use in internal validation cycles.

This way, we significantly reduced the team's dependency on manual verification of high-priority scenarios.

Phase 3
Scaling automation

Once the foundation was stable, we moved on to increasing test automation coverage.

In this phase:

  • The automation suite was significantly extended as more high-risk and edge-case scenarios were added.

  • 630+ automated tests were created in total.

  • Automated tests were fully integrated into CI pipelines.

  • Test execution became faster and more reliable and supported frequent releases.

  • Automatic failure informing in the corresponding Slack channels was implemented.

As a result, a regression run now takes just about 4 hours and is executed every morning without impacting working hours, so by the start of the day, the entire team knows whether the product is release-ready.

Automation has evolved from a supporting tool into a core component of the QA strategy.

Phase 4
Adaptation and optimization

As automation became mature and covered around 95% of regression tests, we went into optimization mode. The QA process was further streamlined to maximize efficiency.

Key improvements:

  • Automated tests are run before every release.

  • Release validation is based on objective automation results rather than manual checks.

  • AQA efforts have switched from execution to monitoring, maintenance, and targeted improvements.

This helps maintain high quality with minimum manual work.

Outcomes

In less than a year, our AQA engineers did a huge amount of work, as a result of which the client received:

  • •

    Faster, more predictable, and less resource-intensive QA processes

  • •

    Automated regression testing suite covering about 95% of tests

  • •

    A highly stable product and more hassle-free and confident releases

Eventually, the project reached the stage where two AQA engineers were no longer required. The automation coverage and process maturity allowed the Agorapulse team to scale down to a single AQA engineer while maintaining high automation coverage, top product quality, and proper release speed.

Facing similar challenges to Agorapulse?

Schedule a call to see how we can help you