acquia/orca

A tool for testing a company's software packages together in the context of a realistic, functioning, best practices Drupal build

v4.14.0 2024-08-12 14:43 UTC

Requires

• php: ^8.1
• ext-dom: *
• ext-json: *
• ext-sqlite3: *
• acquia/coding-standards: ^1.1.0
• composer/composer: ^2.5.5
• cweagans/composer-patches: ^1.7.3
• dealerdirect/phpcodesniffer-composer-installer: ^1.0.0
• ergebnis/composer-normalize: ^2.30.2
• hassankhan/config: ^3.1
• mglaman/drupal-check: ^1.4
• myclabs/php-enum: ^1.8.4
• oscarotero/env: ^2.1
• php-parallel-lint/php-console-highlighter: ^1.0
• php-parallel-lint/php-parallel-lint: ^1.3.2
• phpmd/phpmd: ^2.13
• symfony/config: ^6.2.7
• symfony/console: ^5.4.22
• symfony/dependency-injection: ^6.0.20
• symfony/event-dispatcher: ^6.3
• symfony/expression-language: ^6.3.0
• symfony/filesystem: ^6.4.0
• symfony/finder: ^6.2.7
• symfony/http-client: ^6.2.10
• symfony/options-resolver: ^6.3.0
• symfony/phpunit-bridge: ^7.0.1
• symfony/process: ^6.4.2
• symfony/yaml: ^6.3.0
• weitzman/drupal-test-traits: ^2.1

Requires (Dev)

• brainmaestro/composer-git-hooks: ^2.8.5
• phpspec/prophecy-phpunit: ^2.0.2
• phpstan/phpstan: ^1.10.14
• phpunit/php-code-coverage: ^10
• phpunit/php-file-iterator: ^4.0
• phpunit/phpunit: ^10

Conflicts

• symfony/symfony: *

GPL-2.0-or-later

• Acquia Engineering
• Travis Carden

• cli
• testing
• console
• ci
• drupal

README

ORCA (Official Representative Customer Application) is a tool for testing a company's Drupal-adjacent software packages. It ensures their cross compatibility and correct functioning by installing all of them together into a realistic, functioning, best practices Drupal build and running automated tests and static code analysis on them. Its guiding design principle is to use company packages as a customer would. It installs the latest recommended versions via Composer and performs no manual setup or configuration.

Who is it for?

ORCA is for anyone who has an interest in one or more Drupal extensions or platforms continuing to work together and wants to run automated tests in a continuous integration (CI) workflow to ensure that they do, e.g.:

• Product companies that want to ensure that their own modules continue to work together or on their platforms
• Professional services organizations that want to know ahead of time if the contrib modules they commonly use together are going to have conflicts
• Contributors that want to test together one or more modules they maintain

See Continuous integration for exact details.

Compatibility Matrix

Documentation

• Understanding ORCA
• Getting Started
• CLI Commands
• Advanced Usage
• Project Glossary
• FAQ
• Contribution Guide