La Vitrina Digital
ENES

Test automation · Release quality · Playwright

Catch regressions before your customers do.

I help software teams and web agencies protect critical user journeys with reliable Playwright automation and CI/CD quality gates — without hiring a full-time QA engineer.

Discuss your release processSee an example quality gate

Independent quality engineering · Working remotely from Spain

Is this for your team?

When this is a good fit

Practical test automation for teams that already build and ship software, but need more confidence in their release process.

Your team releases regularly but still relies heavily on manual regression testing.

Important user journeys occasionally break after changes or deployments.

You have developers but no dedicated test automation specialist.

Your agency wants to offer QA automation without hiring a permanent specialist.

Services

Three ways to work together

Clearly scoped engagements, agreed around your application and release process. Prices exclude VAT.

Start with a diagnosis

Release Reliability Assessment

€350 + VAT
Fixed fee · approximately 3–4 hours
  • Review of your application and existing test setup
  • Mapping of up to five critical user journeys
  • Review of your CI/CD pipeline and release checks
  • Prioritised written recommendations
  • Implementation proposal and scope discussion

Repository access and any required environment access are agreed in advance. The assessment does not include implementation.

Discuss an assessment
Core engagement

Automated Release Protection

From €1,500 + VAT
Typically 20–25 hours · final quote after scoping
  • Playwright automation for agreed critical journeys
  • Test architecture aligned with your application
  • GitHub Actions workflow for pull requests
  • Configurable merge protection when required checks fail
  • Failure diagnostics, traces and screenshots
  • Documentation, walkthrough and code handover

Scope depends on application complexity, test environments, authentication, integrations and CI/CD requirements.

Discuss your project
Ongoing support

Quality Maintenance

€300 / month + VAT
Up to 4 hours per month · monthly agreement
  • Updates to tests when agreed interfaces change
  • Investigation and repair of flaky tests
  • Playwright and test dependency updates
  • Small improvements to existing test coverage

Unused hours do not roll over. Requests are acknowledged within one business day; investigation and delivery are scheduled within the monthly allowance. Urgent incident response and out-of-scope work are excluded unless separately agreed.

Ask about maintenance

A straightforward process

From assessment to a pipeline your team can trust

Work happens in your repository and around your existing delivery workflow. The aim is to leave your team with something it can understand, run and maintain.

  1. Assess

    We review the application, existing tests and pipeline. You receive prioritised findings and a scoped proposal.

  2. Agree the scope

    We confirm the journeys, environments, integrations, acceptance criteria, timeline and price before implementation starts.

  3. Build and integrate

    Automation and quality gates are implemented in your repository, using your existing tools where practical.

  4. Handover

    You receive the code, documentation and a walkthrough. Ongoing maintenance is optional.

For software agencies

Add test automation capability without hiring a full-time specialist.

I work as an external QA automation partner on your client projects — integrated into your team's workflow and, where appropriate, under your agency's brand.

How I can support your team

  • Playwright test automation for client applications
  • CI/CD quality gates and release checks
  • Test strategy and automation architecture
  • Flaky-test investigation and stabilisation

Typical engagement

  • Work within your existing repository and process
  • Coordinate directly with your developers
  • Client-facing collaboration by prior agreement
  • Access, confidentiality and ownership agreed in writing
Explore agency partnershipsDiscuss a partnership

Reference demonstration

What a failing quality gate looks like

When a critical journey breaks, the pipeline reports the failing test and blocks the merge until the problem is fixed. Failure reports include traces and screenshots to show exactly what happened.

$ npx playwright test
✓ auth › user can log in
✓ checkout › completes test purchase
✗ billing › invoice PDF downloads

1 failed, 2 passed
Required check failed: merge blocked

Example output for illustration only. Not a recorded test run or a client result.

Interactive estimate

Explore the potential value of reducing manual regression work

Enter your own figures to estimate the engineering time that automation might free up. Figures are used only in your browser. The result is indicative, not a guaranteed saving or ROI forecast.

Whole team; use your own estimate.
Use a conservative estimate. Not all testing is automatable.
Bugs found by customers or monitoring.
Investigation, fix, release and communication.
Only include defects the automated journeys could detect.
Include salary, employer costs and overhead.
Enter your figures to see an estimate

Indicative calculation: testing hours potentially freed = weekly manual testing hours × automatable share × 48 working weeks. Bug-related hours potentially avoided = monthly production bugs × hours per bug × preventable share × 12 months. The model does not subtract implementation or maintenance costs. Actual outcomes depend on architecture, coverage, test reliability and maintenance effort.

Contact

Tell me about your release process.

Share a little about your application, stack and testing challenges. I'll review it and reply by email.

Required fields