Add checks for tools in test suite#699
Conversation
|
I don't think the test script should normalize environments, e.g. finding out which I have to admit I could live with a note in the test directory's README that notes that Docker and Docker compose are required. As for
|
|
I understand, no problem. I'll refactor this at some point to a README update. I really don't want to fiddle with my path just to be able to run the test suite on an open source project. I feel like this could have better DX. I haven't quite had the time to really look into how the test-suite works, but is there maybe a better alternative than a shell script which expects a bunch of tools to be installed? |
|
What I don't understand: the internet tells me |
|
Good point, I was not good at documenting. find is installed on macOS by default, but the version that is installed does not support the flags used in the test script. Sorry I’m on my phone, I believe it’s something like “max-depth” and another one. Either both or one of them is not recognized |
|
Would you want to find out if it's possible to do what is currently done in a way that works with both BSD and GNU versions then? I would think that's the proper fix here. |
I agree, thanks for pushing back! |
|
Closed in favor of #702 |
This PR aims to make the test suite easier to use.
gfindsupport for macos users