BPCEBPCEDevOps and testing

BPCE: automated mobile and API tests at the heart of daily deployment

Our team automated the testing of internal mobile apps and APIs at BPCE, and built it into Jenkins to secure a daily deployment.

DevOpsTestingBanking
Discuss my project
Jenkins pipeline with mobile tests, API tests, report and daily deployment
Dailyautomated deployment, secured by tests
Mobile and APIinternal apps and APIs tested automatically
In productionautomated tests running every day

The context

A large bank's internal mobile apps and APIs change constantly. To ship often without taking risks, every version must go through the same checks, every time.

The goal: replace part of the manual acceptance testing with reliable tests that run automatically in the deployment pipeline.

What we delivered

Automated tests built into the existing deployment pipeline.

  • Mobile testsThe key flows of internal apps tested automatically on iOS and Android.
  • API testsResponses and contracts of internal APIs checked on every release.
  • Jenkins integrationTests run automatically in the pipeline, before the daily deployment.
  • Automatic reportsA readable report is generated after each run, so a regression can be spotted at a glance.

How we worked

We started with the most critical flows, then widened coverage release after release. Each test is designed to be stable and fast, so it stays useful day to day instead of being bypassed.

The results

The automated tests run in production and support every daily deployment. Regressions are caught by the pipeline before they reach users.

Technologies

JenkinsAppiumPostmanNewmaniOSAndroid

Frequently asked questions

The key answers about this project.

By automating the most critical flows on iOS and Android first, then widening coverage release after release. At BPCE, our team used Appium for internal mobile apps along with automatically run API tests.

The tests are added as a step in the Jenkins pipeline: they run on every release, before deployment, and a report is generated at the end of each run. At BPCE, this setup supports a daily deployment.

Because an API that changes behavior can break several applications at once. Automatically checking API responses and contracts on every release catches regressions before they reach users.

Free quote