Testcontainers VS Codeception

• Isolation
  Testcontainers provides a high level of isolation for tests by using Docker containers, ensuring that each test runs in a clean environment without interference from the previous tests.
• Realistic Testing
  By using actual instances of services like databases or message brokers, Testcontainers allow for more realistic integration and end-to-end testing scenarios.
• Ease of Use
  Testcontainers simplifies the setup of complex environments, allowing developers to quickly specify the containers they need without extensive configuration.
• Cross-Platform
  As Testcontainers rely on Docker, they are inherently cross-platform and can be used on any system that supports Docker, such as Windows, Mac, and Linux.
• Compatibility with CI/CD
  Testcontainers can be seamlessly integrated into CI/CD pipelines, enabling automated testing with consistent environments on every build.

Possible disadvantages

• Docker Dependency
  Testcontainers requires Docker to be installed and running on the host machine, which may be an additional dependency that some environments do not support.
• Performance Overhead
  Running tests in Docker containers can introduce additional resource overhead, which may slow down test execution compared to running tests natively.
• Complex Debugging
  Debugging issues in a containerized environment can be more complex due to the additional layer of abstraction, requiring familiarity with Docker commands and tools.
• Limited UI Testing
  Testcontainers are more suited to backend and integration testing rather than UI testing, as graphical applications can be challenging to run in a headless container.

• Unified Testing Framework
  Codeception allows you to write tests for unit, functional, and acceptance testing in one framework, offering a consistent interface and reducing the need to switch between tools.
• BDD Support
  Codeception supports Behavior Driven Development (BDD) which enables writing human-readable test scenarios, making it easier for non-developers to understand test cases.
• Modular Architecture
  Codeception’s modular architecture makes it highly extensible and customizable, allowing the reuse of modules and integration with popular frameworks like Symfony, Laravel, and Yii.
• Comprehensive Suite of Helpers
  It offers a wide range of helper modules for various tasks and integrations, such as interacting with web pages and SOAP/REST APIs, which simplifies the setup of tests.
• Active Community and Documentation
  Codeception has an active community and comprehensive documentation, which provides support and examples for most use cases.

Possible disadvantages

• Complex Setup for Beginners
  The flexibility and feature set of Codeception might be overwhelming for newcomers, requiring more time to understand and correctly set up the environment.
• Steep Learning Curve
  Codeception’s comprehensive range of functionalities and modularity may result in a steeper learning curve compared to simpler testing frameworks.
• Overhead for Small Projects
  For small projects, Codeception might be an overkill due to its complex configuration and multitude of features, which might not all be needed.
• Heavy Dependency on PHP
  As Codeception is a PHP-based testing framework, teams using multiple languages or technologies might require separate solutions for non-PHP environments.
• Performance Overhead
  Running complete acceptance tests through browsers can lead to performance overhead, especially for large test suites, possibly requiring more infrastructure and time.

Testcontainers – From Zero to Hero

More videos

Our First Acceptance Test [6/24] Codeception & Symfony2

More videos

• Floci: Locally emulating any cloud service

  Been using it for a while to run integration tests with Testcontainers [1]. It's very good and much more lightweight than Localstack. [1]: https://testcontainers.com/. - Source: Hacker News / 10 days ago

• Diagnosing and Fixing Flaky Microservice Tests

  Sources: Flaky Tests at Google and How We Mitigate Them - Google Testing Blog; statistics and mitigation patterns used at scale (re-runs, quarantine, quarantining thresholds). An empirical analysis of flaky tests (FSE 2014) - ACM... - Source: dev.to / 16 days ago

• PostgreSQL for Everything

  > Anyway, it is a basic practice of keeping test and dev environment as close as feasible to production, to avoid missing issues and wrong assumptions. Containers are great for this during development. Testcontainers are great for this... - Source: Hacker News / about 2 months ago

View more

• Any pro-tips for writing automated tests with Selenium PHP?

  Personal experience: - don’t use Behat unless you really needed a “story telling”, it has a intermediate layer Gherkin that you’ll need to code. You can write “Given/When/Then” steps but you’ll also need to write “php code” that will... Source: over 3 years ago

• PHPUnit, do i need to learn it?

  Codeception: https://codeception.com/. Source: over 3 years ago

• Advice for an older symfony 4.4 project

  I would say to check out Codeception. Codeceptions has modules for Symfony and database generally. Long and short of it is that if you want you can run api tests that go into the controllers and rollback the database afterwards. Source: about 4 years ago

View more