Write isolated Magento 2 PHPUnit unit tests with mocked dependencies.
npx skills add https://github.com/caravanglory/magehub --skill testing-phpunit
Please help me install this Agent Skill. Skill: testing-phpunit Source: https://github.com/caravanglory/magehub/tree/main/skills/testing/testing-phpunit Command: npx skills add https://github.com/caravanglory/magehub --skill testing-phpunit
This Skill removes the guesswork from writing isolated Magento 2 unit tests by showing how to test real classes with mocked dependencies, precise assertions, and clear exception handling.
Ask the skill to write or update a Magento 2 PHPUnit unit test for a specific class, its dependencies, and the behaviors or exceptions you want covered.
High-intent search queries and answers about installing and using this skill.
Magento 2 PHPUnit unit tests run without framework bootstrap by building subjects in setUp with mocked constructor dependencies. You configure mocks for direct collaborators and assert behavior, return values, and state changes without invoking the full application.
Data providers in PHPUnit supply repeated input and output combinations to a single test method. You define a provider method returning datasets, then validate logic across valid inputs, invalid inputs, and boundary conditions without duplicating test code.
Asserting exceptions in Magento 2 unit tests involves verifying that specific PHP or Magento exception classes are thrown with expected messages. You configure the test expectation to match the exception type and assert the message content matches the triggered error.
Mocking dependencies in setUp requires creating mock objects for direct constructor collaborators using the test framework. You instantiate the subject class with these mocks to isolate behavior, avoiding over-mocking by only replacing direct dependencies the subject interacts with.
Magento PHPUnit unit testing applies to Test/Unit coverage for services, helpers, and models. It validates service logic, return values, state changes, and collaborator side effects through mock-based setup and behavior-focused verification without full framework bootstrap.
Over-mocking in Magento 2 unit tests obscures real behavior by replacing too many collaborators with stubs. Behavior-focused verification requires mocking only direct constructor dependencies, ensuring the subject's actual logic and state changes are genuinely exercised.
nashgaoConfigure PHP projects for unit testing with hyperf/testing and co-phpunit.
furan917Generate Magento 2 PHPUnit unit and integration tests with typed mocks.
furan917Create Magento 2 before, after, and around plugins with di.xml configuration.
v4lheruDesign and implement comprehensive testing strategies for the PACT framework.
