From 0018cd588e515f9f808df1ed8d2a077ab2550459 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Tue, 3 Jan 2017 16:56:50 -0800 Subject: [PATCH] docs: Clean up testing with casper selectors discussion. --- docs/testing-with-casper.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/testing-with-casper.md b/docs/testing-with-casper.md index 268ecb1709..46b860c972 100644 --- a/docs/testing-with-casper.md +++ b/docs/testing-with-casper.md @@ -100,13 +100,13 @@ for writing Casper tests in addition to the debugging notes below: casper.waitForSelector('tag 2'); }); -- Casper uses CSS3 selectors; you can often save time by testing and - debugging your selectors on the relevant page of the Zulip - development app in the Chrome JavaScript console by using e.g. - `$$("#settings-dropdown")`. - - Please note `$$` isn't jQuery, it's a CSS selector equivalent to - `querySelectorAll()`, only available in the browser's JavaScript console. +- The selectors appearing in Casper tests are CSS3 selectors, which is + a slightly different syntax from jQuery selectors. You can often + save time by testing and debugging your selectors on the relevant + page of the Zulip development app in the Chrome JavaScript console + by using e.g. `$$("#settings-dropdown")` (this syntax is the CSS + selector equivalent to `querySelectorAll()`, only available in the + browser's JavaScript console). You can learn more about these selectors and other JavaScript console tools [here](https://developers.google.com/web/tools/chrome-devtools/console/command-line-reference).