Skip to content

Commit 48079b9

Browse files
Update Introduction.md: Some rewordings
Page: https://codeception.com/docs/Introduction
1 parent 381d13b commit 48079b9

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

docs/Introduction.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,29 +13,28 @@ Having your application covered with tests gives you more trust in the stability
1313

1414
In most cases tests don't guarantee that the application works 100% as it is supposed to.
1515
You can't predict all possible scenarios and exceptional situations for complex apps,
16-
but with tests you can cover the most important parts of your app and at least be sure they work as predicted.
16+
but with tests you can cover the most important parts of your app.
1717

1818
There are plenty of ways to test your application.
1919
The most popular paradigm is [Unit Testing](https://en.wikipedia.org/wiki/Unit_testing).
20-
For web applications, testing just the controller and/or the model doesn't prove that your application is working.
21-
To test the behavior of your application as a whole, you should write functional or acceptance tests.
22-
23-
Codeception supports all three testing types.
24-
Out of the box you have tools for writing unit, functional, and acceptance tests in a unified framework.
20+
But for web applications, testing just the controller and/or the model doesn't prove that your application is working.
21+
To test the behavior of your application as a whole, you should also write functional or acceptance tests.
2522

2623
| | Unit Tests | Functional Tests | Acceptance Tests
2724
| --- | --- | --- | --- |
2825
| Scope of the test | Single PHP class | PHP Framework (Routing, Database, etc.) | Page in browser (Chrome, Firefox, or [PhpBrowser](https://codeception.com/docs/03-AcceptanceTests#PhpBrowser)) |
2926
| Testing computer needs access to project's PHP files | Yes | Yes | No |
3027
| Webserver required | No | No | Yes |
3128
| JavaScript | No | No | Yes |
32-
| Additional software required | None | None | Drivers for Firefox/Chrome |
29+
| Additional software required | None | None | chromedriver / geckodriver |
3330
| Test execution speed | Very fast | Fast | Slow |
3431
| Configuration file | `Unit.suite.yml` | `Functional.suite.yml` | `Acceptance.suite.yml` |
3532

36-
One of the main advantages of Codeception is that you don't have to decide on just *one* type of testing. You should have all three!
33+
One of the main advantages of Codeception is that you don't have to decide on just *one* type of testing. You can have all three!
3734
And chances are, that you will (sooner or later) need all three. That's why Codeception consists of three so-called "suites":
38-
A "Unit suite" for all unit tests, a "functional suite" for all functional tests, and an "Acceptance suite" for all acceptance tests.
35+
* A "Unit suite" for all unit tests,
36+
* a "Functional suite" for all functional tests,
37+
* and an "Acceptance suite" for all acceptance tests.
3938

4039
Let's review those three test types in reverse order.
4140

0 commit comments

Comments
 (0)