![]() With symfony/phpunit-bridge comes vendor/bin/simple-phpunit which uses its own PHPUnit version. To your project: $ composer require -dev 'symfony/phpunit-bridge:*' All you need to do is to create a customīootstrap file to ensure the Pimcore startup process has everything it needs. PHPUnitĪs Pimcore is a standard Symfony application, you can use Symfony's PHPUnit testing setup exactly as described in You can find examples how to use those modules by looking through Pimcore's test setup. by bootstrapping your application yourself or by just running tests without any DB/data initialization logic. As the DB initialization is configurable, you should be able to use the module as you need it (e.g. You can also make Codeception an executable and it put it into your PATH, for instance: wget chmod +x codecept.phar sudo mv codecept. The Pimcore module is able to drop and re-create the database and addtional modules like the ClassManager provide helper code to create Pimcore classes from JSON exports. Download codecept.phar Copy it into your project. In addition to Codeception's general features, Pimcore's Codeception modules provide a set of helpers to bootstrap a Pimcore installation from an empty installation. ![]() You could prepare test data in your bootstrap file or run some script before you start the test suite. The following sections include sample code snippets to test your web app’s File Upload functionality in an Automate session. how to make sure you are always testing with the same reproducible data set), so that's up to you. ![]() Note, however, that the PHPUnit setup does not include any out-of-the-box solution how to prepare your application for tests (e.g. In general it's recommended to start with the first approach as it is simpler to set up and to get started with testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |