LumeWeb
/
webextension-polyfill
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
webextension-polyfill/test/run-browsers-smoketests.sh

21 lines
559 B
Bash
Raw Normal View History

chore: Fix the `\n` character preceding `echo` output in shell scripts (#136)
2018-06-19 22:33:12 +00:00
#!/bin/bash
chore: Stop swallowing errors in .sh tests The Bash shell scripts ignored errors in all but the last line. This commit adds `set -eo pipefail` to fix the issue: `set -e` causes the script to exit as soon as any command exits with a non-zero exit code. When pipes are used, this flag only applies to the last command in a pipe. The `set -o pipefail` option ensures that the script is also exited with a non-zero exit code when any command in the pipe fails.
2018-06-19 22:35:04 +00:00
set -eo pipefail
chore: Fix the `\n` character preceding `echo` output in shell scripts (#136)
2018-06-19 22:33:12 +00:00
echo ""
echo "Test webextension-polyfill on real browsers"
echo "==========================================="
test(browsers-smoketests): Run a set of smoke tests on both Chrome and Firefox This commit introduces tape as the test framework used to define the tests in the test extension contexts and send them to the nodejs script that orchestrate the test run. The nodejs script has also been migrated from mocha to tape, it uses the custom test helpers provided to setup the test environment (e.g. create a temporary dir for the test extension, copy the last polyfill build, bundle tape to be used in the test extension, start the browser which run the test extension and finally collect the results of the test extension) and then it merges all the tap logs collected from every test extension into a single "per browser" test suite. - updated travis nodejs environment to nodejs 8 - uses tape to collect test results from inside the test extension - added test case to check polyfill 'existing browser API object' detection - added test for expected rejection on tabs.sendMessage with an invalid tabId - added test with multiple listeners which resolves to undefined and null - optionally run chrome smoketests with --enable-features=NativeCrxBindings
2018-05-10 21:55:05 +00:00
export PATH=$PATH:./node_modules/.bin/
## HEADLESS=1 Enable the headless mode (currently used only on Firefox
## because Chrome doesn't currently support the extensions in headless mode)
export HEADLESS=1
chore: Fix the `\n` character preceding `echo` output in shell scripts (#136)
2018-06-19 22:33:12 +00:00
echo ""
echo "Run smoketests on Chrome"
test(browsers-smoketests): Run a set of smoke tests on both Chrome and Firefox This commit introduces tape as the test framework used to define the tests in the test extension contexts and send them to the nodejs script that orchestrate the test run. The nodejs script has also been migrated from mocha to tape, it uses the custom test helpers provided to setup the test environment (e.g. create a temporary dir for the test extension, copy the last polyfill build, bundle tape to be used in the test extension, start the browser which run the test extension and finally collect the results of the test extension) and then it merges all the tap logs collected from every test extension into a single "per browser" test suite. - updated travis nodejs environment to nodejs 8 - uses tape to collect test results from inside the test extension - added test case to check polyfill 'existing browser API object' detection - added test for expected rejection on tabs.sendMessage with an invalid tabId - added test with multiple listeners which resolves to undefined and null - optionally run chrome smoketests with --enable-features=NativeCrxBindings
2018-05-10 21:55:05 +00:00
TEST_BROWSER_TYPE=chrome npm run test-integration | tap-nirvana
chore: Fix the `\n` character preceding `echo` output in shell scripts (#136)
2018-06-19 22:33:12 +00:00
echo ""
echo "Run smoketests on Firefox"
TEST_BROWSER_TYPE=firefox npm run test-integration | tap-nirvana