Skip to content

Commit f81e707

Browse files
committed
auto updated documentation
1 parent b6b99ab commit f81e707

2 files changed

Lines changed: 1 addition & 7 deletions

File tree

docs/03-AcceptanceTests.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -792,15 +792,9 @@ Additional debugging features by Codeception:
792792

793793
### Common Cases
794794

795-
<<<<<<< HEAD
796795
Let's see how common problems of acceptance testing can be solved with Codeception.
797796

798-
#### Authorization
799-
=======
800-
Let's see how common problems of acceptance testing can be solved with Codeception. We will need to update actor class (whcih is AcceptanceTester) in our case to add a new action.
801-
802797
#### Login
803-
>>>>>>> 82997221b762bc09876379f9f30906c9d364a4f5
804798

805799
It is recommended to put widely used actions inside an Actor class. A good example is the `login` action
806800
which would probably be actively involved in acceptance or functional testing:

docs/09-Data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -217,7 +217,7 @@ modules:
217217

218218
{% endhighlight %}
219219

220-
### DataMapper
220+
### Doctrine
221221

222222
Doctrine is also a popular ORM, unlike some others it implements the DataMapper pattern and is not bound to any framework.
223223
The [Doctrine2](http://codeception.com/docs/modules/Doctrine2) module requires an `EntityManager` instance to work with.

0 commit comments

Comments
 (0)