-
Notifications
You must be signed in to change notification settings - Fork 108
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
Test runner for web browsers #219
Comments
I would like to run tests on as many browsers as possible in the latest versions in accordance with #1 (comment) i.e. Operating system: Windows
Operating system: macOS
Mobile: Operating system Android
Mobile Operating system iOs:
A major update of the iOs system is planned for the summer 2020. Maybe this will be delayed by the current situation. |
After #298 we've came with @budnix and @swistach to a conclusion that maintaining three testing frameworks and mocking Jest with Jasmine may not be the best idea. There are some compatibility issues and mocking the differences breaks the stability of the tests.
|
* #219 - Adds the initial configuration to run tests in browser * #219 - A tiny cleanup in test:browser changes * #219 - Adds missing entry in a eslintignore file * #219 - Adjustments in 140+ specs to be able to run tests in browsers * #219 - Adds missing matcher toMatchObject * #219 - Removes unnecessary devDep * #219 - Solves 'jest.spyOn/jest.fn' problems by using SinonJS. Adds a new devDependency: sinon * #219 - Removes unnecessary dependencies * #219 - Adjusts test to run them in browsers * #219 - Adds Karma's configuration for FF and Chrome. Adds experimental CI action * #219 - Adds xvfb to the action * #219 - Reverts experimental changes for catching license's console.warn * #219 - Adds additional reporter to the karma's configuration * 1 test * 2nd error * regexps * regexp 2 * #219 - Adds config generator for karma. Uses headless browsers as a default on CI. * #219 - Missing adjustments to the linter's config * proper init testing * removed faulty test * smarter validation * #219 - Removes jest and jest-related configuration, sinon 😢 and uses jasmine instead * #219 - revert jasmine-related files into .js * #219 - Changes default spy strategy for jasmine * #219 - Corrects gh's action name * #219 - Sets karma.browsers configuration * #219 - Adjusts changes before CR * #219 - Adds custom matcher to be compatible with jest implementation (more or less) * #219 - Removes unnecessary code from a test's bootstrap file * #219 - Removes unnecessary code from a custom matcher's file * #219 - Removes unnecessary indent from a custom matcher's file * #219 - Adjusts most recent changes in config's test file to the new - jasmine-based env * #219 - Adjusts custom matchers and *.MD files Co-authored-by: Przemek <przemek@navalgo.com>
Done |
Description
Currently, all tests are run or Node and we don't know if all V8 features ale supported in the web browsers and which ones. We need a way to run tests in the desktop and mobile web browsers: Chrome, Firefox, Safari, Opera, Edge etc.
The text was updated successfully, but these errors were encountered: