Closed dingo-d closed 4 years ago
Ok I think I found the issue. If I have capitalized name of the folder then both my suite name and the codeception command have to be capitalized.
So if the folder is tests/Integration
then it has to be Integration.suite.yml
and the command must be /vendor/bin/codecept run Integration
.
My favourite kind of issue: the self-resolving one.
Happy coding and thanks for following up!
Environment OS (Local): MacOs 10.15.4 OS (CI): Ubuntu 18.04.4 LTS, running Docker with
wordpress:5.4.1-php7.2
image PHP version: 7.2 Installed Codeception version: 4.1.4 Installed wp-browser version: 2.5.3 WordPress version: 5.4.1 Local development environment: Valet+ and VVV WordPress structure and management: defaultCan you perform the test manually?
While setting up my GitHub Actions for running test I've noticed that if my integration folder is capitalised (
tests/Integration
) the test run will fail withWhen I changed the name of the folder to
tests/integration
the test run finally passedhttps://github.com/dingo-d/woo-solo-api/pull/19/checks?check_run_id=693764144
The issue is that that way of naming isn't
psr-4
compliant and I'm getting deprecation errors from the composer likeCodeception configuration file
https://github.com/dingo-d/woo-solo-api/blob/feature/2.0.0-update/codeception.dist.ym
Suite configuration file
https://github.com/dingo-d/woo-solo-api/tree/feature/2.0.0-update/tests
Describe the bug
I know that MacOS and Windows have case insensitive filesystem whereas Linux does not. And since I'm running the tests in a Linux based container my hunch is that this is the cause of the issue.
I'm not sure if this is codeception issue or wp-browser issue.
Can I define the paths of the tests in each separate configuration? Like I have in the
codeception.dist.yml
:Can I specify in the
integration.suite.yml
:?