PHPUnit VS starter-workflows

PHPUnit is the de facto standard for PHP unit testing. It provides a framework for writing and running tests, helping developers quickly discover and fix errors. PHPUnit encourages developers to write testable code and adopt a test-driven development approach, resulting in higher-quality code and reduced chances of errors in production.

Before updating Api Platform, you should make sure that your Api Platform routes are fully covered by tests. You can define integration tests with PHPUnit, Behat or Pest, depending on the tool you’re most comfortable with.

PHP popular tools for testing: PHPUnit

PHPUnit: PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit architecture for unit testing frameworks. Extensions/tools: brianium/paratest: Parallel testing for PHPUnit johnkary/phpunit-speedtrap: Reports on slow-running tests in your PHPUnit test suite. robiningelbrecht/phpunit-pretty-print: Better PHPUnit CLI output with Collision roave/no-leaks: PHPUnit Plugin for detecting Memory Leaks in code and tests

We want to start migrating to Attributes because of the announcement made here that in PHPUnit 12 support for metadata in docblocks will be removed: https://github.com/sebastianbergmann/phpunit/issues/4502

PHPUnit: PHPUnit PHPUnit is a testing framework for PHP. It enables developers to write unit tests, integration tests, and functional tests to verify the correctness of their code. It offers a wide range of assertions, test runners, and mocking capabilities. Documentation: Explore PHPUnit's capabilities and learn how to write effective tests in the official documentation: PHPUnit Repository

I really like how Pest PHP formats and outputs test results, but I still prefer to use PHPUnit. Luckily there's Collision. This package is designed to give you beautiful error reporting when interacting with your app through the command line.

Finally we install the command line version of php (no web server is needed for this project), composer which is a package management system for PHP and PHP Unit, the testing framework of PHP.

I've been developing my own symfony bundle and I would like to share with you how I'm driving continuos integration to execute my unit tests. For testing purposes I'm using phpunit and for continous integration i've choosen github actions.

PHPUnit is a unit testing framework for PHP included with Laravel and can be used to test your application's code. It provides a set of assertions and functions for testing your code and can be used to run automated tests.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).

Preevy is designed to be easily run in CI/CD workflows, such as GH Actions, Circle CI and others.

I set out to add further development and contribution tools to my ez-txt2html converter. Specifically, I wanted to introduce an initial Continuous Integration workflow. For this, I used the “Python Application” workflow template in Github Actions to create a CI testing workflow that builds a Py v3.12 environments, builds the project dependencies, runs Flake8 linting and Black formatting and then subsequently runs PyTest using the test suites I’ve written previously.

GitHub Actions

To start, I turned to the starter-workflows repository, a valuable resource housing diverse YAML files for various project types. My project being in .NET, I checked out the dotnet.yml file to get insights into the setup process. Understanding the YAML syntax and keywords like on, push, jobs, and steps is crucial for crafting an effective workflow. In my case, I wanted to the workflow to trigger "on" any "pushes" on the main branch. The job describes the specific task which can be given a name, and steps outline the necessary steps to run the job.