-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add automated browser testing #377
Conversation
- Moved automated-testing to browser-extension - Added requirements.txt to reduce setup steps - Updated slur detection scripts for chrome, firefox - Added slur detection scripts for brave, chromium, edge - Updated gitignore
is there substantial difference in the chromium based browsers to warrant distinct test files? I'm thinking that an extension that we test on chrome works just fine in brave. So would automating chrome tests be good enough? |
- Updated firefox automated testing
- Fixed firefox automation - Added workaround for unknown bug for all browsers
I have not read up on specific differences in chromium based browsers. However, there is a |
* Add automated browser testing - Moved automated-testing to browser-extension - Added requirements.txt to reduce setup steps - Updated slur detection scripts for chrome, firefox - Added slur detection scripts for brave, chromium, edge - Updated gitignore * - Updated readme - Updated firefox automated testing * - Migrated to testing wiki pages than tweets - Fixed firefox automation - Added workaround for unknown bug for all browsers * - Fixed sonarlint suggestion in firefox test
Moved
automated-testing
tobrowser-extension
Added
requirements.txt
to reduce setup stepsUpdated slur detection scripts for chrome, firefox
Added slur detection scripts for brave, chromium, edge
Updated gitignore
This addresses issue Automate testing of Uli #374
Edit 1:
requirements.txt
has pinned versions for reproducibility