Scaffolded code quality was not being validated - only file existence was checked. This adds Behat scenarios that run phpcs on generated code to ensure it meets WordPress coding standards.

Changes

• New test file: features/scaffold-lint.feature with 6 scenarios covering:

  • Plugin scaffolding (main file and test files)
  • Post-type and taxonomy scaffolding
  • Child theme scaffolding
  • Block scaffolding

• Background section: Installs phpcs once via helper plugin for all scenarios:

  Background:
    Given a WP install
    And I run `wp plugin path`
    And save STDOUT as {PLUGIN_DIR}
    When I run `wp scaffold plugin phpcs-helper --skip-tests`
    When I run `composer config --working-dir={PLUGIN_DIR}/phpcs-helper allow-plugins...`
    When I run `composer require --dev --working-dir={PLUGIN_DIR}/phpcs-helper ... wpcs`

• Each scenario: Scaffolds code, runs phpcs with WordPress standard, asserts exit code 0

Example scenario

Scenario: Scaffold plugin and lint it
  When I run `wp scaffold plugin test-plugin`
  Then STDOUT should not be empty
  When I run `{PLUGIN_DIR}/phpcs-helper/vendor/bin/phpcs --standard=WordPress {PLUGIN_DIR}/test-plugin/test-plugin.php`
  Then the return code should be 0

The tests will catch any coding standard violations in scaffolded output before they reach users.

• Fixes Lint scaffolding results in Behat #113

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.