Fix failing Scrutinizer CI tests
Open
Nobody has claimed this yet.
bug
help wanted
unit tests / CI
- Dominant language
- PHP
- Stars
- 2.7k
- Forks
- 579
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Since a few months Scrutinizer CI keeps failing. Here are latest results: https://scrutinizer-ci.com/g/smalot/pdfparser/inspections
It seems to complain about the PHPUnit config file we use. I don't really have time to look into that further, but if anyone wants to bring the issue forward (in form of a pull request), I am happy to assist.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Scrutinizer inspection results and the PHPUnit configuration file mentioned in the issue. Reproduce the CI failure and identify the configuration problem; the work is done when the PHPUnit tests pass in Scrutinizer CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100