Skip to content

Commit

Permalink
Fix misprint: 'vendir' -> 'vendor'
Browse files Browse the repository at this point in the history
  • Loading branch information
bocharsky-bw committed Oct 9, 2017
1 parent 3045e08 commit d32ddba
Show file tree
Hide file tree
Showing 5 changed files with 10 additions and 10 deletions.
4 changes: 2 additions & 2 deletions knpu/episode1/debugging-tests.rst
Expand Up @@ -26,7 +26,7 @@ Now run the test again:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Not surprisingly, we're getting a 500 error instead of 200. But we can't
really see what's going on because we can't see the big error page!
Expand Down Expand Up @@ -70,7 +70,7 @@ Now just re-run the test:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
It may be ugly, but the entire response of the last request our test made
is printed out, including all the header information on top. Once you've
Expand Down
2 changes: 1 addition & 1 deletion knpu/episode1/different-representations.rst
Expand Up @@ -75,7 +75,7 @@ Now run the test:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Perfect! We've decided just to ignore these "extra" properties. You could
also decide to return an error response instead. It just depends on your
Expand Down
4 changes: 2 additions & 2 deletions knpu/episode1/put-editing.rst
Expand Up @@ -77,7 +77,7 @@ We haven't actually coded this yet, so when we run the test, it fails:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
The test reports that the status code isn't 200, it's 405. 405 means "method
not allowed", and our framework is doing this for us. It's a way of saying
Expand Down Expand Up @@ -163,7 +163,7 @@ Time to run the test!

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Woot! It passes! And we can even run it over and over again.

Expand Down
2 changes: 1 addition & 1 deletion knpu/episode1/put-improvements.rst
Expand Up @@ -53,7 +53,7 @@ Re-run the tests to see if we broke anything:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Cool! I'm going to change how this code is written *just* a little bit so
that it's even more dynamic::
Expand Down
8 changes: 4 additions & 4 deletions knpu/episode1/testing-data.rst
Expand Up @@ -5,7 +5,7 @@ Let's run our test a second time:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
It fails! The nickname of a programmer is unique in the database, and if
you look closely, this fails because the API tries to insert another ``ObjectOrienter``
Expand Down Expand Up @@ -46,7 +46,7 @@ Try the test again:

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Dang, it failed again. Ah, remember how we're relating all programmers to
the ``weaverryan`` user? Well, when we empty the tables before the scenario,
Expand All @@ -70,7 +70,7 @@ are executed before each ``Scenario``. Ok, try it one more time!

.. code-block:: bash
$ php vendir/bin/behat
$ php vendor/bin/behat
Success! When you test, it's critical to make sure that your database is
in a predictable state before each test. Don't assume that a user exists
Expand Down Expand Up @@ -116,7 +116,7 @@ is important, just like in the previous scenario.

Run it!

$ php vendir/bin/behat
$ php vendor/bin/behat

Success!

Expand Down

0 comments on commit d32ddba

Please sign in to comment.