chenx221/yii2-netdisk
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity
539a6f0c59
yii2-netdisk/tests
History
Alexander Makarov 539a6f0c59 Codeceoption adjustments 
- Removed hacks since these are no longer required: 71db233985
- Removed unused helper classes
- Added 2.0 style "actor" to config

Thanks to @Ragazzo and @DavertMik for helping with it.
2014-07-11 19:30:45 +04:00
..
_data Added acceptance tests for the basic app. 2013-06-22 20:26:22 -04:00
_log Added acceptance tests for the basic app. 2013-06-22 20:26:22 -04:00
_pages Reformat code te be PSR-2 compatible 2014-03-16 10:46:21 +06:00
acceptance Add wait() to login test with wrong credentials to fix WebDriver test 2014-04-04 12:16:17 +02:00
functional Reformat code te be PSR-2 compatible 2014-03-16 10:46:21 +06:00
unit Fixes #4071: mail component renamed to mailer, yii\log\EmailTarget::$mail renamed to yii\log\EmailTarget::$mailer 2014-06-26 18:28:28 +04:00
_bootstrap.php added server name, for creating url rules 2014-02-27 18:37:34 +04:00
_config.php Missing files for #4071 2014-06-26 18:28:57 +04:00
_console_bootstrap.php added yii console command to tests 2014-02-09 19:04:26 +04:00
.gitignore removed auto generated files from repo 2013-12-17 00:45:25 +01:00
acceptance.suite.yml Codeceoption adjustments 2014-07-11 19:30:45 +04:00
functional.suite.yml Codeceoption adjustments 2014-07-11 19:30:45 +04:00
README.md Switched to Codeception 2.0.* for application template tests 2014-07-02 14:44:31 +03:00
unit.suite.yml Codeceoption adjustments 2014-07-11 19:30:45 +04:00

README.md

This folder contains various tests for the basic application. These tests are developed with Codeception PHP Testing Framework.

After creating the basic application, follow these steps to prepare for the tests:

  1. Install additional composer packages:

    php composer.phar require --dev "codeception/codeception: 2.0.*" "codeception/specify: *" "codeception/verify: *"

  2. In the file _bootstrap.php, modify the definition of the constant TEST_ENTRY_URL so that it points to the correct entry script URL.

  3. Go to the application base directory and build the test suites:

    vendor/bin/codecept build

Now you can run the tests with the following commands:

# run all available tests
vendor/bin/codecept run
# run acceptance tests
vendor/bin/codecept run acceptance
# run functional tests
vendor/bin/codecept run functional
# run unit tests
vendor/bin/codecept run unit

Please refer to Codeception tutorial for more details about writing and running acceptance, functional and unit tests.