-
Most of the tests right now are doing remote requests against a custom server running on Heroku: https://requests-php-tests.herokuapp.com.
These remote requests are flaky as they tend to fail every…
-
something, anything
-
To help us handle PR review, I'd like to start a discussion on CI infrastructure and testing requirements to help us merge in contributions. To kick this off, here's a few suggestions on what we need …
-
- [ ] Integrate a testing framework (something like travis)
- [ ] Implement some basic tests that must run when new commits are pushed to master
- [ ] Document how to create new tests and keep site te…
-
We need to have tests run on every pull request.
Also want build versions to be automatically updated, so they are consistent and increasing.
-
We need to take a broad look at the tests currently implemented for the crate and determine whether they meet our standards, and if not, identify what needs to change to get to a point where we're sat…
-
I noticed we run a lot of expensive tests of the examples for infrastructure changes. IIRC we can restrict runs of the `examples` job to cases where something in `glass` has changed.
-
### Description
- When something inside the cake script fails it just gets reported out as a general exit code "Bash exited with code '1'.". Ideally we can surface the actual exception which will l…
-
1. Create our own libray/schema to hold test tables, procedures, etc
2. No longer use QIWS.QCUSTCDT for insert tests (Use our own test tables)
3. Add after/afterEach hooks to delete data inserted by…
-
We have some issues with our current testing infrastructure:
- [ ] All tests require all definitions to be loaded and a world to be generated. Even the most basic tests that _don't_ need definition…