-
Example project: https://github.com/tongrhj/karma-test/tree/cf4d63f6c91bd573adf224b626d2b96fce28488a
Steps to reproduce:
1. Start server
```
./node_modules/karma/bin/karma start
```
2. Run tes…
-
I have configured the headless chrome in my project getting rid of Phantom. When I run the tests on my OSX machine, all the tests get executed with the test runner on the headless chrome. But the same…
-
I had the use case of a test being properly implemented but the feature code being incomplete and failing. When running the tests with the QUnit web interface, the test is not erroring out and is prop…
-
I've been doing some work with Ember + WebComponents lately and support, in the latest version, is actually pretty good. I would love to get this reflected in your site! I can look into making a PR th…
-
I am currently working on an app using Angular 8 with the okta-auth-js library version 4.5.
Previously, in the 3.x and earlier, I was easily able to mock the okta library, however, with this one I …
-
When running the tests in Chrome or Firefox, the browsers open briefly, but no actual tests get executed. The same tests work just fine in PhantomJS.
Here's a small repo demonstrating the issue: ht…
-
I checked already the troubleshooting guide. We recently upgraded from angular 12 to angular 14 and since then our pipline gets stuck on testing inside the gitlab pipline after executing all tests, bu…
-
Starting with Chrome 109, WebGL contexts can no longer be created in my Karma tests, meaning I can no longer run my tests locally. It appears to be because Chrome no longer supports software rendering…
-
https://github.com/mike-goodwin/owasp-threat-dragon
-
Hey,
It appears that the package does not work with ES modules using the `` syntax. Take this test file for instance:
```ts
// tests/my-component-tests.ts
import chai from '../node_modules/@b…