Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

NanoAdblocker/NanoTest

Repository files navigation

Nano Test Engine Dependencies

But does it even work?

Note: This is very out of date, and I no longer control the jspenguin.com domain. Be careful if you want to play around with it.

The automated testing framework for Nano Adblocker, requires latest current branch of Node.js.

One time setup

npm install

Start

node init

Advanced

--debug-mode
Open the developer tool for every window
Defaults to only open developer tool for the extension background page
A debugger breakpoint will be triggered on failed test, this option can be useful to trace down failed tests

--override-extension-path=<path>
Change the path to the extension to load
Defaults to "../NanoBuild/dist/nano_adblocker_chromium/"

--override-user-data-dir=<path>
Change the path to the user data directory
Defaults to "./userdata/data/"

--skip-auto-config
Skip automated configuration which does the following:
- Enter "chrome://extensions/"
- Enable "Developer mode"
- Select "Allow in incognito"
- Select "Collect errors"
- Unselect "Allow access to file URLs"
- Enter the extension dashboard
- Unselect all filters
- Load test filter
- Update the test filter
- Close "chrome://extensions/" and the extension dashboard

About

But does it even work?

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •