WordPress / WordPress/sqlite-database-integration
Improve the new driver test suite
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 363
- Forks
- 67
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
The test suite for the new SQLite driver originates from the old driver tests being duplicated. As the test suite was growing over time, it would make sense to better categorize the tests, and check them against a real MySQL instance to make sure our assertions are correct. In doing so, we may consider always running them against both the SQLite driver and a MySQL container, and removing the hardcoded assertions.
Contributor guide
No contributing guide indexed for this repository
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 locating the duplicated new SQLite driver tests and the older driver test suite, then compare how they run against SQLite and a real MySQL instance or container. Done means the tests are better categorized, exercise both drivers, and no longer rely on hardcoded assertions where the issue identifies that concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php, sqlite
- Domain
- databases, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100