Skip to content

test(integrations): write unit tests for integration provider classes (bunnynet, cloudways, enhance, laravel-forge, plesk, rocket, serverpilot, wpengine, wpmudev) #697

Description

@superdav42

Context

The inc/integrations/providers/ directory contains 15 provider integration classes. Only 5 have domain-mapping tests (closte, gridpane, hestia, runcloud, cpanel). The remaining 9 providers have 0% test coverage.

Uncovered providers

  • bunnynet/ — BunnyNet CDN/DNS integration
  • cloudways/ — Cloudways hosting provider
  • enhance/ — Enhance control panel
  • laravel-forge/ — Laravel Forge server management
  • plesk/ — Plesk control panel
  • rocket/ — Rocket.net hosting
  • serverpilot/ — ServerPilot hosting
  • wpengine/ — WP Engine hosting
  • wpmudev/ — WPMU DEV hosting

What

Write unit tests for each uncovered provider covering:

  • Provider ID, title, and capability declarations
  • Domain mapping capability (if implemented)
  • Node management capability (if implemented)
  • Error handling for API failures

How

Follow the pattern in tests/WP_Ultimo/Integrations/Providers/ and tests/WP_Ultimo/Integrations/Host_Providers/. Run composer test to verify.

Acceptance Criteria

  • Unit tests for all 9 uncovered providers
  • Each test covers at minimum: ID, title, capabilities declared
  • All existing tests still pass
  • CI green

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions