Skip to content

fix an error that may cause confusion #57

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

Merged
stof merged 2 commits into from
Jun 26, 2015
Merged

fix an error that may cause confusion #57

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
08c78c8
fix an error that may cause confusion
Jun 23, 2015
86a2142
fix a similar confusion between browser and brower emulator
Jun 23, 2015
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
4 changes: 2 additions & 2 deletions at-a-glance.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ there is actually 2 completely different types of browser emulators out there:
* Headless browser emulators
* Browser controllers

First type browsers are simple pure HTTP specification implementations, like
First type browser emulators are simple pure HTTP specification implementations, like
`Goutte`_. Those browser emulators send a real HTTP requests against an application
and parse the response content. They are very simple to run and configure,
because this type of emulators can be written in any available programming
Expand All @@ -29,7 +29,7 @@ is that such browser emulators require the installed browser, extra configuratio
and are usually much slower than headless counterparts.

So, the easy answer is to choose the best emulator for your project and use
its API for testing. But as we've already seen, both browser types have both
its API for testing. But as we've already seen, both browser emulator types have both
advantages and disadvantages. If you choose headless browser emulator, you
will not be able to test your JS/AJAX pages. And if you choose browser controller,
your overall test suite will become very slow at some point. So, in real
Expand Down