summaryrefslogtreecommitdiffstats
path: root/composer.json
Commit message (Collapse)AuthorAgeFilesLines
* Add Psalm as dev dependencyHarald Eilertsen2021-05-081-1/+3
|
* Fix composer test command.Harald Eilertsen2021-04-221-1/+1
| | | | | | | Since running the bash script on windows was a bit troublesome, make the `composer test` command a first class citizen. Still don't know how to run a specific test case using the composer command, but at least it should be easy to run the full test suite.
* Add test script to composer.jsonHarald Eilertsen2021-04-161-0/+3
| | | | | | | | | | | This makes it easier to run the test script directly from the editor it your editor supports composer. Otherwise run it from the command line: composer run test Or like before: ./run-tests
* Fix test setup for wp-env.Harald Eilertsen2021-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | After much reading I finally found the magic incantations, so now we can run tests with real database access. This means we no longer need the primitive $wpdb_stub. The setup as now _requires_ wp-env, or an environment set up sufficiently similar. Running in wp-env is the easiest, so aim for that. I've added a `run-tests` script that will invoke the magic incantation without having to remember it every time. To set up for testing: 1. make sure you have composer[1] installed. 2. run `composer install` 3. make sure you have wp-env[2] installed 4. start the wordpress env: `wp-env start` 5. run the tests: `./run-tests` Let the thousand tests bloom! [1]: https://github.com/wp-phpunit/wp-phpunit [2]: https://www.npmjs.com/package/@wordpress/env
* Install phpunit with composer.Harald Eilertsen2021-04-101-1/+3
|
* Add composer.json to manage dependencies.Harald Eilertsen2021-04-101-0/+17
See https://getcomposer.org/ for intro, why and usage. For now this is mostly to handle dev dependencies, i.e phpunit.