Testing PHP Code with Atoum - an Alternative to PHPUnit
Atoum: A Fluent Alternative to PHPUnit for PHP Testing
Atoum stands as a contemporary PHP testing framework, presenting a compelling alternative to PHPUnit. Its fluent interface prioritizes readability and simplifies test creation. This tutorial explores Atoum's installation, configuration, and core functionalities, highlighting its advantages for modern PHP development.
Key Features:
- Fluent Interface: Atoum's syntax enhances readability and reduces the boilerplate code often associated with testing.
- Easy Installation: Leveraging Composer for seamless installation and integration.
-
IDE Support: Enhanced IDE interaction through the
atoum/stubs
package, facilitating code completion and debugging. -
Flexible Test Styles: Supports both BDD/Gherkin-style (
given
,when
,then
) and a more direct approach, catering to diverse preferences. - Built-in Code Coverage: Includes robust code coverage tools with HTML output for clear visualization.
- CI Integration: Seamlessly integrates with continuous integration systems.
- Advanced Features: Supports annotations for specifying PHP versions and required extensions, ensuring test compatibility across different environments.
Beyond PHPUnit: Why Choose Atoum?
While PHPUnit holds a dominant position in the PHP testing landscape, Atoum offers a refreshing approach. Its modern design and intuitive interface streamline the testing process, particularly beneficial for developers seeking enhanced readability and ease of use.
Installation and Setup:
Install Atoum and the essential atoum/stubs
package using Composer:
composer require atoum/atoum composer require atoum/stubs
For optimal PhpStorm integration (or similar IDEs), the atoum/stubs
package is crucial for improved code completion.
Configuration (.atoum.php):
Customize reporting and code coverage output by creating a .atoum.php
file in your project's root directory:
<?php use mageekguy\atoum; $stdout = new atoum\writers\std\out; $report = new atoum\reports\realtime\santa; // Or cli, phing, tap, NyanCat $script->addReport( $report->addWriter($stdout) );
Configure HTML code coverage by creating a /coverage/html
directory and adapting vendor/atoum/resources/configurations/runner/coverage.php.dist
(rename to coverage.php
):
<?php // ... (Update paths and URLs as needed) ...
Writing Your First Test:
Atoum recommends creating a tests/units
directory mirroring your application's source structure. For example, a test for an src/App/Entity/Journal.php
entity would reside in tests/units/Entity/Journal.php
.
Example test using BDD style:
composer require atoum/atoum composer require atoum/stubs
Running Tests and Code Coverage:
Execute tests with code coverage using:
<?php use mageekguy\atoum; $stdout = new atoum\writers\std\out; $report = new atoum\reports\realtime\santa; // Or cli, phing, tap, NyanCat $script->addReport( $report->addWriter($stdout) );
The HTML code coverage report will be generated in the /coverage/html
directory.
Debugging with dump()
:
For debugging, use the dump()
method (requires running with -d
or --debug
):
<?php // ... (Update paths and URLs as needed) ...
Annotations: @php and @extensions:
Atoum leverages annotations for advanced test control:
-
@php <version></version>
: Specifies the required PHP version for a test method or class. -
@extensions <extension1> <extension2> ...</extension2></extension1>
: Specifies required PHP extensions.
Conclusion:
Atoum provides a powerful and user-friendly alternative to PHPUnit. Its fluent interface, built-in features, and support for advanced testing scenarios make it a strong contender for modern PHP development. While the initial learning curve might be slightly steeper than PHPUnit, the long-term benefits in terms of readability and maintainability are significant. Explore its extensive documentation and extensions to unlock its full potential.
The above is the detailed content of Testing PHP Code with Atoum - an Alternative to PHPUnit. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...

Article discusses essential security features in frameworks to protect against vulnerabilities, including input validation, authentication, and regular updates.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

The enumeration function in PHP8.1 enhances the clarity and type safety of the code by defining named constants. 1) Enumerations can be integers, strings or objects, improving code readability and type safety. 2) Enumeration is based on class and supports object-oriented features such as traversal and reflection. 3) Enumeration can be used for comparison and assignment to ensure type safety. 4) Enumeration supports adding methods to implement complex logic. 5) Strict type checking and error handling can avoid common errors. 6) Enumeration reduces magic value and improves maintainability, but pay attention to performance optimization.
