@@ -12,28 +12,28 @@ provides a few that you may use directly:
1212* ` CodeIgniter\Test\CIUnitTestCase ` - for basic tests with no other service needs
1313* ` CodeIgniter\Test\CIDatabaseTestCase ` - for tests that need database access
1414
15- ** ModuleTests ** also provides some examples:
16- * ` ModuleTests \Support\DatabaseTestCase` - for database tests, pre-configured for migrations, seeds, and models from ** tests/_ support**
17- * ` ModuleTests \Support\SessionTestCase` - for session tests, pre-configured with a mock session driver
15+ ** ProjectTests ** also provides some examples:
16+ * ` ProjectTests \Support\DatabaseTestCase` - for database tests, pre-configured for migrations, seeds, and models from ** tests/_ support**
17+ * ` ProjectTests \Support\SessionTestCase` - for session tests, pre-configured with a mock session driver
1818
1919Most of the time you will want to write your own test cases to hold functions and services
2020common to your test suites.
2121
2222## Tests
2323
24- All tests go in the ** tests/** directory. ** ModuleTests ** provides two generic
25- subfolders for you, ** unit** and ** database** - but feel free to make your own. Each test file
26- is a class that extends a ** Test Case** (see above) and contains methods for the individual
27- tests. These method names must start with the word "test" and should have descriptive names
28- for precisely what they are testing: ` testUserCanModifyFile() ` ` testOutputColorMatchesInput() `
29- ` testIsLoggedInFailsWithInvalidUser() `
24+ All tests go in the ** tests/** directory. ** ProjectTests ** provides some generic
25+ subfolders for you ( ** unit** , ** session ** , and ** database** ) - but feel free to make your
26+ own. Each test file is a class that extends a ** Test Case** (see above) and contains methods
27+ for the individual tests. These method names must start with the word "test" and should
28+ have descriptive names for precisely what they are testing:
29+ ` testUserCanModifyFile() ` ` testOutputColorMatchesInput() ` ` testIsLoggedInFailsWithInvalidUser() `
3030
3131Writing tests is an art, and there are many resources available to help learn how. Review
3232the links above and always pay attention to your [ Code Coverage] ( docs/COVERAGE.md ) .
3333
3434### Database Tests
3535
36- ** ModuleTests ** provides examples for migrating, seeding, and testing against a mock
36+ ** ProjectTests ** provides examples for migrating, seeding, and testing against a mock
3737or live<sup >1</sup > database. The example files can be modified or replaced with your own:
3838* ** tests/_ support/Database/Migrations/create_test_tables.php**
3939* ** tests/_ support/Database/Seeds/ExampleSeeder.php**
@@ -50,7 +50,7 @@ repo by adding it to **.gitignore**.
5050
5151### Session Tests
5252
53- Similar to database testing, ** ModuleTests ** provides a test case pre-configured
53+ Similar to database testing, ** ProjectTests ** provides a test case pre-configured
5454with the [ mock session class] ( https://codeigniter4.github.io/userguide/testing/overview.html#mocking-services )
5555to make testing sessions easier:
5656* ** tests/_ support/SessionTestCase.php**
0 commit comments