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

docs(readme): fix typos #32

Merged
merged 1 commit into from
Nov 24, 2023
Merged

docs(readme): fix typos #32

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
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ end program tester
```

Every test is defined in a separate module using a ``collect`` function, which is exported and added to the ``testsuites`` array in the test runner.
All test have a simple interface with just an allocatable ``error_type`` as output to provide the test results.
All tests have a simple interface with just an allocatable ``error_type`` as output to provide the test results.

```fortran
module test_suite1
Expand Down Expand Up @@ -90,7 +90,7 @@ end module test_suite1

### Checking test conditions

The procedures defining the tests can contain any Fortran code required for the checking the correctness of the project.
The procedures defining the tests can contain any Fortran code required for checking the correctness of the project.
An easy way to do so is provided by the generic ``check`` function.

```f90
Expand Down Expand Up @@ -154,7 +154,7 @@ An uncaught skipped test will fail regardless, therefore make sure to not run an

### Integration in build systems

Finally, for usage with *fpm* it is benefical to have a single test driver which can run all tests.
Finally, for usage with *fpm* it is beneficial to have a single test driver which can run all tests.
While this brings the disadvantage of always having to run the complete testsuite, the main driver can provide the flexibility to select the suite and also the unit test using the boilerplate code shown here:

```f90
Expand Down
Loading