DB Schema per Test Runner: an immutable schema, used only for reading, is replicated for each runner.
PHP SANDBOX TEST CODE
Kept on local machines together with code or on a shared server for simplicity. Dedicated Database Sandbox: lightweight databases, one for each developer/machine.PDO and Doctrine 1/2 can subtitute it along with each self-respecting ORM. the only problem is speed or number of licenses if you use a proprietary db, but if you use in-memory Sqlite you won't get problems. Substitute lightweight db created on the fly is very powerful: no shared objects, the most updated schema for your code. Most of these variations are rendered obsolete by the first. You'll still have to test somewhere with the real database: Sqlite does not give me the confidence to go in production. The issue of SQLite is the lack of functionalities like foreign keys or other advanced aggregate functions. The schema is built at the start of test run, and kept in-memory it is destroyed after the test run ends.
I use Sqlite for the majority of tests, via PDO it's very simple to subtitute it and the Doctrine Database Abstraction Layer (DBAL) it's capable of generating the right syntax for CREATE TABLE and INSERT queries, dependeing on the type of database you're connected to.Įven the walls in a PHP-based shop now knows that Sqlite is the way to go for test suites: free, fast, and satisfying most of the functional requirements of web applications. I'm also assuming we are talking about relational database: these patterns have been extracted from this kind of applications.Īlternatively, you can make the fixture setup phase build a new database for each test run (which involve a database, of course). If you intend to use a real database in test suite, you must provide the possibility of configuration for the database used by developers locally.
PHP SANDBOX TEST FREE
However, no worries for a developer with a Database Sandbox: he's free to modify its database and work on his copy of the source code.
PHP SANDBOX TEST HOW TO
We'll see later how to reset the situation so that the tests start always from the same fixture. Without a sandbox, you'll experience intermittent failures due to concurrency, or tests that cannot start because of a wrong schema deployed on the common database, or where wrong fixtures have been loaded. If you as a developer run two test suites simultaneously, or in the same day (maybe different subsets of tests or the same tests from two machines) you'll hit different databases. Ideally, for every instance of the test suite a separate database will be available. But then our test suites cannot run concurrently (nothing worse than having to tell your colleagues that you have to run the suite, and they should not touch it.)Īnd what should be the schema of that database? Taken from which branch and release of the application?Ī Database Sandbox fosters test isolation by providing a separate database for each person running the tests. We may start to use our shared database on the development server for doing tests. We may test some logic independently, but we're bound to touch the database in end-to-end tests or in operations which involve SQL operators, like a SUM(). We set out for doing TDD and testing everything, but then we come across an SQL query and we are puzzled.
0 kommentar(er)
