Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Small typo in testing/overview.rst #8927

Merged
merged 1 commit into from
May 31, 2024
Merged

docs: Small typo in testing/overview.rst #8927

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions user_guide_src/source/testing/overview.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,14 @@ There are no rules for how test files must be placed. However, we recommend that
you establish placement rules in advance so that you can quickly understand where
the test files are located.

In this document, we will place the test files corresponding to the classes in
the **app** directory in the **tests/app** directory. To test a new library,
In this document, the test files corresponding to the classes in the **app** directory
will be placed in the **tests/app** directory. To test a new library,
**app/Libraries/Foo.php**, you would create a new file at
**tests/app/Libraries/FooTest.php**:

.. literalinclude:: overview/001.php

To test one of your models, **app/Models/UserMode.php**, you might end up with
To test one of your models, **app/Models/UserModel.php**, you might end up with
something like this in **tests/app/Models/UserModelTest.php**:

.. literalinclude:: overview/002.php
Expand Down Expand Up @@ -121,7 +121,7 @@ parent as well so extended test cases do not interfere with staging:
Traits
------

A common way to enhance your tests is by using traits to consolidate staging across different
A common way to enhance your tests is using traits to consolidate staging across different
test cases. ``CIUnitTestCase`` will detect any class traits and look for staging methods
to run named for the trait itself (i.e. `setUp{NameOfTrait}()` and `tearDown{NameOfTrait}()`).

Expand Down