From 17b5c3f6dc13d3222e300bf7251d48616f26cde0 Mon Sep 17 00:00:00 2001 From: kenjis Date: Mon, 18 Jul 2022 08:42:12 +0900 Subject: [PATCH 1/4] docs: remove spaces at the end of the lines --- admin/module/tests/README.md | 38 +++++++++++++++--------------- admin/starter/tests/README.md | 42 ++++++++++++++++----------------- tests/README.md | 44 +++++++++++++++++------------------ 3 files changed, 62 insertions(+), 62 deletions(-) diff --git a/admin/module/tests/README.md b/admin/module/tests/README.md index 3c05eeae92e7..a56c5f04420f 100644 --- a/admin/module/tests/README.md +++ b/admin/module/tests/README.md @@ -1,8 +1,8 @@ # Running Module Tests -This is the quick-start to CodeIgniter testing. Its intent is to describe what -it takes to set up your module and get it ready to run unit tests. -It is not intended to be a full description of the test features that you can +This is the quick-start to CodeIgniter testing. Its intent is to describe what +it takes to set up your module and get it ready to run unit tests. +It is not intended to be a full description of the test features that you can use to test your module. Those details can be found in the documentation. ## Resources @@ -11,9 +11,9 @@ use to test your module. Those details can be found in the documentation. ## Requirements -It is recommended to use the latest version of PHPUnit. At the time of this -writing we are running version 8.5.13. Support for this has been built into the -**composer.json** file that ships with CodeIgniter and can easily be installed +It is recommended to use the latest version of PHPUnit. At the time of this +writing we are running version 8.5.13. Support for this has been built into the +**composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. > composer install @@ -27,10 +27,10 @@ for code coverage to be calculated successfully. ## Setting Up -A number of the tests use a running database. -In order to set up the database edit the details for the `tests` group in +A number of the tests use a running database. +In order to set up the database edit the details for the `tests` group in **phpunit.xml**. Make sure that you provide a database engine that is currently running -on your machine. More details on a test database setup are in the +on your machine. More details on a test database setup are in the *Docs>>Testing>>Testing Your Database* section of the documentation. ## Running the tests @@ -39,24 +39,24 @@ The entire test suite can be run by simply typing one command-line command from > ./phpunit -You can limit tests to those within a single test directory by specifying the -directory name after phpunit. +You can limit tests to those within a single test directory by specifying the +directory name after phpunit. > ./phpunit app/Models ## Generating Code Coverage -To generate coverage information, including HTML reports you can view in your browser, -you can use the following command: +To generate coverage information, including HTML reports you can view in your browser, +you can use the following command: > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m -This runs all of the tests again collecting information about how many lines, -functions, and files are tested. It also reports the percentage of the code that is covered by tests. -It is collected in two formats: a simple text file that provides an overview as well -as a comprehensive collection of HTML files that show the status of every line of code in the project. +This runs all of the tests again collecting information about how many lines, +functions, and files are tested. It also reports the percentage of the code that is covered by tests. +It is collected in two formats: a simple text file that provides an overview as well +as a comprehensive collection of HTML files that show the status of every line of code in the project. -The text file can be found at **tests/coverage.txt**. +The text file can be found at **tests/coverage.txt**. The HTML files can be viewed by opening **tests/coverage/index.html** in your favorite browser. ## PHPUnit XML Configuration @@ -67,7 +67,7 @@ do not have your own configuration file in the project root. The normal practice would be to copy ``phpunit.xml.dist`` to ``phpunit.xml`` (which is git ignored), and to tailor it as you see fit. -For instance, you might wish to exclude database tests, or automatically generate +For instance, you might wish to exclude database tests, or automatically generate HTML code coverage reports. ## Test Cases diff --git a/admin/starter/tests/README.md b/admin/starter/tests/README.md index 9d20661afecd..8ef6b2ac80f7 100644 --- a/admin/starter/tests/README.md +++ b/admin/starter/tests/README.md @@ -1,8 +1,8 @@ # Running Application Tests -This is the quick-start to CodeIgniter testing. Its intent is to describe what -it takes to set up your application and get it ready to run unit tests. -It is not intended to be a full description of the test features that you can +This is the quick-start to CodeIgniter testing. Its intent is to describe what +it takes to set up your application and get it ready to run unit tests. +It is not intended to be a full description of the test features that you can use to test your application. Those details can be found in the documentation. ## Resources @@ -12,9 +12,9 @@ use to test your application. Those details can be found in the documentation. ## Requirements -It is recommended to use the latest version of PHPUnit. At the time of this -writing we are running version 9.x. Support for this has been built into the -**composer.json** file that ships with CodeIgniter and can easily be installed +It is recommended to use the latest version of PHPUnit. At the time of this +writing we are running version 9.x. Support for this has been built into the +**composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. > composer install @@ -28,14 +28,14 @@ for code coverage to be calculated successfully. ## Setting Up -A number of the tests use a running database. -In order to set up the database edit the details for the `tests` group in -**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine +A number of the tests use a running database. +In order to set up the database edit the details for the `tests` group in +**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine that is currently running on your machine. More details on a test database setup are in the [Testing Your Database](https://codeigniter4.github.io/userguide/testing/database.html) section of the documentation. -If you want to run the tests without using live database you can -exclude @DatabaseLive group. Or make a copy of **phpunit.dist.xml** - +If you want to run the tests without using live database you can +exclude @DatabaseLive group. Or make a copy of **phpunit.dist.xml** - call it **phpunit.xml** - and comment out the named "database". This will make the tests run quite a bit faster. @@ -49,24 +49,24 @@ If you are using Windows, use the following command. > vendor\bin\phpunit -You can limit tests to those within a single test directory by specifying the -directory name after phpunit. +You can limit tests to those within a single test directory by specifying the +directory name after phpunit. > ./phpunit app/Models ## Generating Code Coverage -To generate coverage information, including HTML reports you can view in your browser, -you can use the following command: +To generate coverage information, including HTML reports you can view in your browser, +you can use the following command: > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m -This runs all of the tests again collecting information about how many lines, -functions, and files are tested. It also reports the percentage of the code that is covered by tests. -It is collected in two formats: a simple text file that provides an overview as well -as a comprehensive collection of HTML files that show the status of every line of code in the project. +This runs all of the tests again collecting information about how many lines, +functions, and files are tested. It also reports the percentage of the code that is covered by tests. +It is collected in two formats: a simple text file that provides an overview as well +as a comprehensive collection of HTML files that show the status of every line of code in the project. -The text file can be found at **tests/coverage.txt**. +The text file can be found at **tests/coverage.txt**. The HTML files can be viewed by opening **tests/coverage/index.html** in your favorite browser. ## PHPUnit XML Configuration @@ -77,7 +77,7 @@ do not have your own configuration file in the project root. The normal practice would be to copy ``phpunit.xml.dist`` to ``phpunit.xml`` (which is git ignored), and to tailor it as you see fit. -For instance, you might wish to exclude database tests, or automatically generate +For instance, you might wish to exclude database tests, or automatically generate HTML code coverage reports. ## Test Cases diff --git a/tests/README.md b/tests/README.md index 40755f1b65c6..d13679915593 100644 --- a/tests/README.md +++ b/tests/README.md @@ -1,15 +1,15 @@ # Running System Tests -This is the quick-start to CodeIgniter testing. Its intent is to describe what -it takes to set up your system and get it ready to run unit tests. -It is not intended to be a full description of the test features that you can -use to test your application. Those details can be found in the documentation. +This is the quick-start to CodeIgniter testing. Its intent is to describe what +it takes to set up your system and get it ready to run unit tests. +It is not intended to be a full description of the test features that you can +use to test your application. Those details can be found in the documentation. ## Requirements -It is recommended to use the latest version of PHPUnit. At the time of this -writing we are running version 9.x. Support for this has been built into the -**composer.json** file that ships with CodeIgniter and can easily be installed +It is recommended to use the latest version of PHPUnit. At the time of this +writing we are running version 9.x. Support for this has been built into the +**composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. > composer install @@ -23,14 +23,14 @@ for code coverage to be calculated successfully. After installing `XDebug`, you ## Setting Up -A number of the tests use a running database. -In order to set up the database edit the details for the `tests` group in -**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine -that is currently running on your machine. More details on a test database setup are in the +A number of the tests use a running database. +In order to set up the database edit the details for the `tests` group in +**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine +that is currently running on your machine. More details on a test database setup are in the [Testing Your Database](https://codeigniter4.github.io/CodeIgniter4/testing/database.html) section of the documentation. -If you want to run the tests without using live database you can -exclude `@DatabaseLive` group. Or make a copy of **phpunit.dist.xml** - +If you want to run the tests without using live database you can +exclude `@DatabaseLive` group. Or make a copy of **phpunit.dist.xml** - call it **phpunit.xml** - and comment out the `` named `Database`. This will make the tests run quite a bit faster. @@ -44,7 +44,7 @@ If you are using Windows, use the following command. > vendor\bin\phpunit -You can limit tests to those within a single test directory by specifying the +You can limit tests to those within a single test directory by specifying the directory name after phpunit. All core tests are stored under **tests/system**. > ./phpunit tests/system/HTTP/ @@ -59,17 +59,17 @@ You can run the tests without running the live database and the live cache tests ## Generating Code Coverage -To generate coverage information, including HTML reports you can view in your browser, -you can use the following command: +To generate coverage information, including HTML reports you can view in your browser, +you can use the following command: > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m -This runs all of the tests again collecting information about how many lines, -functions, and files are tested. It also reports the percentage of the code that is covered by tests. -It is collected in two formats: a simple text file that provides an overview as well -as a comprehensive collection of HTML files that show the status of every line of code in the project. +This runs all of the tests again collecting information about how many lines, +functions, and files are tested. It also reports the percentage of the code that is covered by tests. +It is collected in two formats: a simple text file that provides an overview as well +as a comprehensive collection of HTML files that show the status of every line of code in the project. -The text file can be found at **tests/coverage.txt**. +The text file can be found at **tests/coverage.txt**. The HTML files can be viewed by opening **tests/coverage/index.html** in your favorite browser. ## PHPUnit XML Configuration @@ -80,5 +80,5 @@ do not have your own configuration file in the project root. The normal practice would be to copy ``phpunit.xml.dist`` to ``phpunit.xml`` (which is git ignored), and to tailor it as you see fit. -For instance, you might wish to exclude database tests, or automatically generate +For instance, you might wish to exclude database tests, or automatically generate HTML code coverage reports. From d19912336e32bc34d0a727f648da06d995728b9b Mon Sep 17 00:00:00 2001 From: kenjis Date: Mon, 18 Jul 2022 08:37:18 +0900 Subject: [PATCH 2/4] docs: update command style --- admin/module/tests/README.md | 19 +++++++++++++++---- admin/starter/tests/README.md | 24 ++++++++++++++++++------ tests/README.md | 32 ++++++++++++++++++++++++-------- 3 files changed, 57 insertions(+), 18 deletions(-) diff --git a/admin/module/tests/README.md b/admin/module/tests/README.md index a56c5f04420f..0a1512c01317 100644 --- a/admin/module/tests/README.md +++ b/admin/module/tests/README.md @@ -16,11 +16,15 @@ writing we are running version 8.5.13. Support for this has been built into the **composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. - > composer install +```console +> composer install +``` If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. - > ln -s ./vendor/bin/phpunit ./phpunit +```console +> ln -s ./vendor/bin/phpunit ./phpunit +``` You also need to install [XDebug](https://xdebug.org/index.php) in order for code coverage to be calculated successfully. @@ -37,12 +41,16 @@ on your machine. More details on a test database setup are in the The entire test suite can be run by simply typing one command-line command from the main directory. - > ./phpunit +```console +> ./phpunit +``` You can limit tests to those within a single test directory by specifying the directory name after phpunit. - > ./phpunit app/Models +```console +> ./phpunit app/Models +``` ## Generating Code Coverage @@ -50,6 +58,9 @@ To generate coverage information, including HTML reports you can view in your br you can use the following command: > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +```console +> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +``` This runs all of the tests again collecting information about how many lines, functions, and files are tested. It also reports the percentage of the code that is covered by tests. diff --git a/admin/starter/tests/README.md b/admin/starter/tests/README.md index 8ef6b2ac80f7..f6a1f665e6ac 100644 --- a/admin/starter/tests/README.md +++ b/admin/starter/tests/README.md @@ -17,11 +17,15 @@ writing we are running version 9.x. Support for this has been built into the **composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. - > composer install +```console +> composer install +``` If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. - > ln -s ./vendor/bin/phpunit ./phpunit +```console +> ln -s ./vendor/bin/phpunit ./phpunit +``` You also need to install [XDebug](https://xdebug.org/index.php) in order for code coverage to be calculated successfully. @@ -43,23 +47,31 @@ the tests run quite a bit faster. The entire test suite can be run by simply typing one command-line command from the main directory. - > ./phpunit +```console +> ./phpunit +``` If you are using Windows, use the following command. - > vendor\bin\phpunit +```console +> vendor\bin\phpunit +``` You can limit tests to those within a single test directory by specifying the directory name after phpunit. - > ./phpunit app/Models +```console +> ./phpunit app/Models +``` ## Generating Code Coverage To generate coverage information, including HTML reports you can view in your browser, you can use the following command: - > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +```console +> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +``` This runs all of the tests again collecting information about how many lines, functions, and files are tested. It also reports the percentage of the code that is covered by tests. diff --git a/tests/README.md b/tests/README.md index d13679915593..b64c2e9ed712 100644 --- a/tests/README.md +++ b/tests/README.md @@ -12,11 +12,15 @@ writing we are running version 9.x. Support for this has been built into the **composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. - > composer install +```console +> composer install +``` If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. - > ln -s ./vendor/bin/phpunit ./phpunit +```console +> ln -s ./vendor/bin/phpunit ./phpunit +``` You also need to install [XDebug](https://xdebug.org/docs/install) in order for code coverage to be calculated successfully. After installing `XDebug`, you must add `xdebug.mode=coverage` in the **php.ini** file to enable code coverage. @@ -38,31 +42,43 @@ the tests run quite a bit faster. The entire test suite can be run by simply typing one command-line command from the main directory. - > ./phpunit +```console +> ./phpunit +``` If you are using Windows, use the following command. - > vendor\bin\phpunit +```console +> vendor\bin\phpunit +``` You can limit tests to those within a single test directory by specifying the directory name after phpunit. All core tests are stored under **tests/system**. - > ./phpunit tests/system/HTTP/ +```console +> ./phpunit tests/system/HTTP/ +``` Individual tests can be run by including the relative path to the test file. - > ./phpunit tests/system/HTTP/RequestTest.php +```console +> ./phpunit tests/system/HTTP/RequestTest.php +``` You can run the tests without running the live database and the live cache tests. - > ./phpunit --exclude-group DatabaseLive,CacheLive +```console +> ./phpunit --exclude-group DatabaseLive,CacheLive +``` ## Generating Code Coverage To generate coverage information, including HTML reports you can view in your browser, you can use the following command: - > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +```console +> ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m +``` This runs all of the tests again collecting information about how many lines, functions, and files are tested. It also reports the percentage of the code that is covered by tests. From 8fe0acad8f8eaf8ffdbd67b176ea818422842397 Mon Sep 17 00:00:00 2001 From: kenjis Date: Mon, 18 Jul 2022 08:46:38 +0900 Subject: [PATCH 3/4] docs: update test/README --- admin/module/tests/README.md | 26 +++++++++++++++++--------- admin/starter/tests/README.md | 17 +++++++---------- tests/README.md | 13 ++++++++++--- 3 files changed, 34 insertions(+), 22 deletions(-) diff --git a/admin/module/tests/README.md b/admin/module/tests/README.md index 0a1512c01317..5645f7828e01 100644 --- a/admin/module/tests/README.md +++ b/admin/module/tests/README.md @@ -6,13 +6,15 @@ It is not intended to be a full description of the test features that you can use to test your module. Those details can be found in the documentation. ## Resources + * [CodeIgniter 4 User Guide on Testing](https://codeigniter4.github.io/userguide/testing/index.html) -* [PHPUnit docs](https://phpunit.readthedocs.io/en/8.5/index.html) +* [PHPUnit docs](https://phpunit.de/documentation.html) +* [Any tutorials on Unit testing in CI4?](https://forum.codeigniter.com/showthread.php?tid=81830) ## Requirements It is recommended to use the latest version of PHPUnit. At the time of this -writing we are running version 8.5.13. Support for this has been built into the +writing we are running version 9.x. Support for this has been built into the **composer.json** file that ships with CodeIgniter and can easily be installed via [Composer](https://getcomposer.org/) if you don't already have it installed globally. @@ -20,22 +22,23 @@ via [Composer](https://getcomposer.org/) if you don't already have it installed > composer install ``` -If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. +If running under macOS or Linux, you can create a symbolic link to make running tests a touch nicer. ```console > ln -s ./vendor/bin/phpunit ./phpunit ``` -You also need to install [XDebug](https://xdebug.org/index.php) in order -for code coverage to be calculated successfully. +You also need to install [XDebug](https://xdebug.org/docs/install) in order +for code coverage to be calculated successfully. After installing `XDebug`, you must add `xdebug.mode=coverage` in the **php.ini** file to enable code coverage. ## Setting Up A number of the tests use a running database. In order to set up the database edit the details for the `tests` group in -**phpunit.xml**. Make sure that you provide a database engine that is currently running -on your machine. More details on a test database setup are in the -*Docs>>Testing>>Testing Your Database* section of the documentation. +**phpunit.xml**. +Make sure that you provide a database engine that is currently running on your machine. +More details on a test database setup are in the +[Testing Your Database](https://codeigniter4.github.io/userguide/testing/database.html) section of the documentation. ## Running the tests @@ -45,6 +48,12 @@ The entire test suite can be run by simply typing one command-line command from > ./phpunit ``` +If you are using Windows, use the following command. + +```console +> vendor\bin\phpunit +``` + You can limit tests to those within a single test directory by specifying the directory name after phpunit. @@ -57,7 +66,6 @@ directory name after phpunit. To generate coverage information, including HTML reports you can view in your browser, you can use the following command: - > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m ```console > ./phpunit --colors --coverage-text=tests/coverage.txt --coverage-html=tests/coverage/ -d memory_limit=1024m ``` diff --git a/admin/starter/tests/README.md b/admin/starter/tests/README.md index f6a1f665e6ac..473d0f8c140e 100644 --- a/admin/starter/tests/README.md +++ b/admin/starter/tests/README.md @@ -9,6 +9,7 @@ use to test your application. Those details can be found in the documentation. * [CodeIgniter 4 User Guide on Testing](https://codeigniter4.github.io/userguide/testing/index.html) * [PHPUnit docs](https://phpunit.de/documentation.html) +* [Any tutorials on Unit testing in CI4?](https://forum.codeigniter.com/showthread.php?tid=81830) ## Requirements @@ -21,28 +22,24 @@ via [Composer](https://getcomposer.org/) if you don't already have it installed > composer install ``` -If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. +If running under macOS or Linux, you can create a symbolic link to make running tests a touch nicer. ```console > ln -s ./vendor/bin/phpunit ./phpunit ``` -You also need to install [XDebug](https://xdebug.org/index.php) in order -for code coverage to be calculated successfully. +You also need to install [XDebug](https://xdebug.org/docs/install) in order +for code coverage to be calculated successfully. After installing `XDebug`, you must add `xdebug.mode=coverage` in the **php.ini** file to enable code coverage. ## Setting Up A number of the tests use a running database. In order to set up the database edit the details for the `tests` group in -**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine -that is currently running on your machine. More details on a test database setup are in the +**app/Config/Database.php** or **phpunit.xml**. +Make sure that you provide a database engine that is currently running on your machine. +More details on a test database setup are in the [Testing Your Database](https://codeigniter4.github.io/userguide/testing/database.html) section of the documentation. -If you want to run the tests without using live database you can -exclude @DatabaseLive group. Or make a copy of **phpunit.dist.xml** - -call it **phpunit.xml** - and comment out the named "database". This will make -the tests run quite a bit faster. - ## Running the tests The entire test suite can be run by simply typing one command-line command from the main directory. diff --git a/tests/README.md b/tests/README.md index b64c2e9ed712..5a7ddbbbed72 100644 --- a/tests/README.md +++ b/tests/README.md @@ -5,6 +5,12 @@ it takes to set up your system and get it ready to run unit tests. It is not intended to be a full description of the test features that you can use to test your application. Those details can be found in the documentation. +## Resources + +* [CodeIgniter 4 User Guide on Testing](https://codeigniter4.github.io/userguide/testing/index.html) +* [PHPUnit docs](https://phpunit.de/documentation.html) +* [Any tutorials on Unit testing in CI4?](https://forum.codeigniter.com/showthread.php?tid=81830) + ## Requirements It is recommended to use the latest version of PHPUnit. At the time of this @@ -16,7 +22,7 @@ via [Composer](https://getcomposer.org/) if you don't already have it installed > composer install ``` -If running under OS X or Linux, you can create a symbolic link to make running tests a touch nicer. +If running under macOS or Linux, you can create a symbolic link to make running tests a touch nicer. ```console > ln -s ./vendor/bin/phpunit ./phpunit @@ -29,8 +35,9 @@ for code coverage to be calculated successfully. After installing `XDebug`, you A number of the tests use a running database. In order to set up the database edit the details for the `tests` group in -**app/Config/Database.php** or **phpunit.xml**. Make sure that you provide a database engine -that is currently running on your machine. More details on a test database setup are in the +**app/Config/Database.php** or **phpunit.xml**. +Make sure that you provide a database engine that is currently running on your machine. +More details on a test database setup are in the [Testing Your Database](https://codeigniter4.github.io/CodeIgniter4/testing/database.html) section of the documentation. If you want to run the tests without using live database you can From c8fda0f091741fba4a183da5f34b9df54143fa45 Mon Sep 17 00:00:00 2001 From: kenjis Date: Mon, 18 Jul 2022 20:08:47 +0900 Subject: [PATCH 4/4] docs: fix wrong dir Co-authored-by: MGatner --- admin/module/tests/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin/module/tests/README.md b/admin/module/tests/README.md index 5645f7828e01..be12d4c954c4 100644 --- a/admin/module/tests/README.md +++ b/admin/module/tests/README.md @@ -58,7 +58,7 @@ You can limit tests to those within a single test directory by specifying the directory name after phpunit. ```console -> ./phpunit app/Models +> ./phpunit tests/Models ``` ## Generating Code Coverage