docs: Update many references to Casper.

This commit is contained in:
Tim Abbott 2020-08-30 15:10:57 -07:00
parent 2d22d88700
commit 992c6126a8
9 changed files with 8 additions and 18 deletions

View File

@ -198,8 +198,7 @@ number without any explicit conversion.
### JavaScript `const` and `let`
Always declare JavaScript variables using `const` or `let` rather than
`var`, except in the Casper tests (since Casper does not support
`const` and `let`).
`var`.
### JavaScript and TypeScript `for (i in myArray)`

View File

@ -78,7 +78,7 @@ templating systems.
* `frontend_tests/node_tests/` Node Frontend unit tests.
* `frontend_tests/casper_tests/` Casper frontend tests.
* `frontend_tests/puppeteer_tests/` Puppeteer frontend integration tests.
* `tools/test-*` Developer-facing test runner scripts.

View File

@ -211,7 +211,7 @@ time when debugging, since developers don't need to think about things
like whether some test changed Hamlet's email address and that's why
login is broken.
More full-stack test suites like `test-js-with-casper` or `test-api`
More full-stack test suites like `test-js-with-puppeteer` or `test-api`
use a similar strategy (set a random `KEY_PREFIX` at the start of the
test run).

View File

@ -84,5 +84,5 @@ lookup should still work even if you disable proxy for
127.0.0.1 testsubdomain.zulipdev.com
```
These records are also useful if you want to e.g. run the casper tests
These records are also useful if you want to e.g. run the Puppeteer tests
when you are not connected to the Internet.

View File

@ -96,7 +96,7 @@ additionally:
`zproject/settings.py` and `zproject/test_extra_settings.py`.
* `zproject/test_extra_settings.py` has the (default) settings used
for the Zulip tests (both backend and Casper), which are applied on
for the Zulip tests (both backend and Puppeteer), which are applied on
top of the development environment settings.
When adding a new server setting to Zulip, you will typically add it

View File

@ -56,7 +56,7 @@ organization in Zulip). The following files are involved in the process:
zerver/lib/events.py implementation.
**Frontend testing**
- `frontend_tests/casper_tests/10-admin.js`: end-to-end tests for the organization
- `frontend_tests/puppeteer_tests/08-admin.js`: end-to-end tests for the organization
admin settings pages.
- `frontend_tests/node_tests/dispatch.js`

View File

@ -38,13 +38,8 @@ def check_our_files(modified_only: bool, all_dups: bool, fix: bool, targets: Lis
def check_html_templates(templates: Iterable[str], all_dups: bool, fix: bool) -> None:
# Our files with .html extensions are usually for Django, but we also
# have a few static .html files.
#
# We also have .html files that we vendored from Casper.
# The casperjs files use HTML5 (whereas Zulip prefers XHTML), and
# there are also cases where Casper deliberately uses invalid HTML,
# so we exclude them from our linter.
logging.basicConfig(format='%(levelname)s:%(message)s')
templates = sorted(fn for fn in templates if 'casperjs' not in fn)
templates = sorted(fn for fn in templates)
# Use of lodash templates <%= %>.
if 'templates/zerver/team.html' in templates:
templates.remove('templates/zerver/team.html')

View File

@ -12,7 +12,7 @@ from zerver.views.auth import create_preregistration_user
from zerver.views.registration import accounts_register
# This is used only by the casper test in 00-realm-creation.js.
# This is used only by the puppeteer test in 00-realm-creation.js.
def confirmation_key(request: HttpRequest) -> HttpResponse:
return json_success(request.session.get('confirmation_key'))

View File

@ -28,10 +28,6 @@ urls = [
serve, {'document_root':
os.path.join(settings.DEPLOY_ROOT, 'var/node-coverage/lcov-report'),
'show_indexes': True}),
path('casper/<path:path>',
serve, {'document_root':
os.path.join(settings.DEPLOY_ROOT, 'var/casper'),
'show_indexes': True}),
path('docs/<path:path>',
serve, {'document_root':
os.path.join(settings.DEPLOY_ROOT, 'docs/_build/html')}),