Skip to content

Commit 9319585

Browse files
committed
Update test running instructions for new test/ dir
1 parent c75c37c commit 9319585

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,17 @@ Get the packages you need and install a git hook to run tests before push:
88

99
bash install-dev-dependencies.sh
1010

11-
Run the tests for the Firefox version:
11+
Run all the tests:
1212

1313
bash test.sh
1414

1515
Run the latest code and rulesets in a standalone Firefox profile:
1616

17-
bash test.sh --justrun
17+
bash test/firefox.sh --justrun
1818

1919
Run the latest code and rulesets in a standalone Chromium profile:
2020

21-
bash test-chromium.sh --justrun
21+
bash test/chromium.sh --justrun
2222

2323
Build the Firefox extension as a .xpi package:
2424

@@ -56,6 +56,8 @@ Important directories you might want to know about
5656

5757
src/chrome/content/rules The rulesets live here
5858

59+
test/ The tests live here
60+
5961
Hacking on the Source Code
6062
--------------------------
6163

@@ -95,7 +97,7 @@ We have two publicly-archived mailing lists: the https-everywhere list (https://
9597
Tests
9698
-------------
9799

98-
There are some very basic unittests under https-everywhere-tests/. These are run with
100+
There are some very basic unittests under test/. These are run with
99101

100102
bash test.sh
101103

@@ -106,7 +108,7 @@ loading URLs in a browser and watching for Mixed Content Blocking to fire.
106108
The easiest way to run ruleset tests is to load a standalone Firefox instance
107109
with the tests enabled:
108110

109-
bash test.sh --justrun
111+
bash test/firefox.sh --justrun
110112

111113
Then click the HTTPS Everywhere icon on the toolbar, and click "Run HTTPS
112114
Everywhere Ruleset Tests." When you run the tests, be prepared to let your

0 commit comments

Comments
 (0)