• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

safe-global / safe-client-gateway / 18381154395
89%

Build:
DEFAULT BRANCH: main
Ran 09 Oct 2025 03:49PM UTC
Jobs 2
Files 952
Run time 3min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 Oct 2025 03:18PM UTC coverage: 89.917% (+0.8%) from 89.16%
18381154395

push

github

web-flow
Tests: Separate unit and integration tests into parallel CI jobs (#2740)

* Separate unit and integration tests into parallel CI jobs

This change improves CI reliability and speed by separating unit tests from integration tests.

Changes:
- Created jest-unit.json config for unit tests (329 tests, excludes .integration.spec.ts and .e2e-spec.ts)
- Created jest-integration.json config for integration tests (16 tests, includes .integration.spec.ts and .e2e-spec.ts)
- Added npm scripts: test:unit, test:unit:cov, test:integration, test:integration:cov
- Split CI workflow into two parallel jobs:
  - unit-tests: Fast feedback (~2 min), no external services
  - integration-tests: Full validation (~5-10 min), with Postgres, Redis, RabbitMQ
- Added TESTING.md documentation with patterns and best practices

Benefits:
- Faster CI feedback: Unit tests complete in ~2 min instead of ~10 min
- Better failure isolation: Immediately know if failure is code or infrastructure
- Cost optimization: Unit tests don't require expensive service containers
- Improved reliability: Flaky integration tests don't block unit test results
- Parallel execution: Both test suites run simultaneously

All tests remain co-located with their code - no file moves required.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: Apply prettier formatting

* fix: Add e2e-setup to integration tests config

Integration tests need the e2e-setup.ts file to set required environment
variables like JWT_ISSUER, JWT_SECRET, and database connection details.

* fix: Add database services to unit-tests job

Some .spec.ts files use real database connections (not true unit tests).
Adding services to unit-tests job to match main branch behavior and prevent
AggregateError failures.

The separation still provides value:
- unit-tests: Runs 329 .spec.ts files (most are mocked, some use DB)
- integration-tests: Runs 16 .integration.spec.ts and .e2e-s... (continued)

3861 of 4759 branches covered (81.13%)

Branch coverage included in aggregate %.

12966 of 13955 relevant lines covered (92.91%)

521.67 hits per line

Uncovered Existing Lines

Lines Coverage ∆ File
3
0.0
-17.65% src/__tests__/util/retry.ts
Jobs
ID Job ID Ran Files Coverage
1 run-unit-tests - 18381154395.1 09 Oct 2025 03:53PM UTC 1872
88.64
GitHub Action Run
2 run-integration-tests - 18381154395.2 09 Oct 2025 03:49PM UTC 267
84.14
GitHub Action Run
Source Files on build 18381154395
  • Tree
  • List 952
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #18381154395
  • 822f35d0 on github
  • Prev Build on main (#18370876006)
  • Next Build on main (#18460303827)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc