Test Core Laravel Package

Product Decisions This Supports

• Accelerating QA and CI/CD pipelines for Ibexa DXP-based projects by standardizing test automation frameworks, reducing manual testing effort, and improving test coverage.
• Enabling "shift-left" testing by integrating test utilities early in the development lifecycle (e.g., for custom Ibexa modules or integrations).
• Roadmap decision for Ibexa DXP adopters: Justify investment in Ibexa DXP by leveraging its native testing tools to reduce long-term maintenance costs.
• Build vs. Buy: Avoid reinventing test infrastructure for Ibexa-specific scenarios (e.g., content repository validation, workflow testing) when this package offers a foundation.
• Use cases:
  • Validating custom content types, field types, or business logic layers.
  • Testing Ibexa DXP integrations (e.g., with third-party APIs or services).
  • Automating regression tests for Ibexa DXP upgrades or migrations.

When to Consider This Package

• Adopt if:

  • Your team is actively developing or maintaining Ibexa DXP-based applications (not the open-source eZ Platform).
  • You need specialized test utilities for Ibexa’s content repository, workflows, or API layers (e.g., testing content structure, permissions, or search functionality).
  • You’re evaluating Ibexa DXP and want to assess its ecosystem before committing to a subscription.
  • Your CI/CD pipeline lacks Ibexa-specific test helpers (e.g., for database seeding, content state transitions).

• Look elsewhere if:

  • You’re using eZ Platform (open-source) instead of Ibexa DXP (this package is DXP-only).
  • Your testing needs are generic PHP/Laravel (e.g., unit testing business logic) and don’t involve Ibexa’s core features.
  • You require mature, production-ready tools (this is experimental/internal).
  • Your team lacks Ibexa DXP expertise to configure or extend the package.
  • You’re constrained by the Ibexa BUL license (requires a paid subscription for business use).

How to Pitch It (Stakeholders)

For Executives: "This package lets us standardize and automate testing for our Ibexa DXP projects, reducing bugs in production and speeding up releases. By leveraging Ibexa’s native tools, we avoid reinventing the wheel for content repository validation, workflow testing, and integrations—saving development time and lowering long-term costs. It’s a strategic fit if we’re committed to Ibexa DXP, as it aligns with their ecosystem and could justify our subscription investment."

For Engineering/DevOps: "The ibexa/test-core package provides Ibexa-specific test utilities (e.g., for content creation, state transitions, and API validation) to streamline our QA process. It’s experimental but could cut manual testing effort by 30–50% for DXP-related scenarios. We’d need to evaluate it alongside our CI/CD pipeline to see how it integrates with tools like PHPUnit or Laravel’s testing helpers. Warning: It’s DXP-only and requires a subscription for business use, so we should confirm alignment with our tech stack first."

For Developers: *"This is a lightweight way to add Ibexa DXP test helpers to your project—think of it as a ‘testing DSL’ for content, workflows, and repositories. For example, you could write a test like:

$content = IbexaTest::createContent('article', ['title' => 'Test']);
$content->publish();
assertTrue($content->isPublished());

It’s early-stage, so expect some trial-and-error, but it could save time if you’re deep in Ibexa DXP development."*