The example code for my automated testing workshop
Oliver Davies
f0f93912ee
Using a data provider, multiple arguments can be passed into the test, such as different combinations of created dates and expected results. This test also requires mocking the `Time` object as it’s now a dependency of the article wrapper. The `getCreatedTime` method on the article also needs to be set to return a specific value. |
||
|---|---|---|
| .github/workflows | ||
| .idea | ||
| config/default | ||
| web | ||
| .gitignore | ||
| composer.json | ||
| composer.lock | ||
| docker-compose.yaml | ||
| php.ini | ||
| phpunit.xml.dist | ||
| README.md | ||
Drupal Automated Testing Workshop: Example Code
Updates
If we need to update any of the commits, the changes should be rebased into the existing commits so that they continue to be in a linear order as per the workshop document.
As we want GitHub Actions to run for each commit, we can’t just push the latest commit as that would only trigger a build on the final commit. To do this, we can loop over each of the commit SHAs and push each one separately:
for sha1 in $(git rev-list HEAD --reverse) ; do
git push origin $sha1:master --force
done