-
# Creating initial development environment
This issue main objective is to define the project's `setup` and initial environment decisions.
Definition of done:
- [x] Settings of Linter and Edito…
-
## Missing imports
We've received reports on our GitHub issue tracker (e.g., issue #17207) about missing code imports after upgrading to CKEditor 5 version 42.0.0 or higher. These issues mainly affe…
-
# Description
In several occasion (e.g. https://github.com/rancher/dashboard/issues/8999 and https://github.com/rancher/dashboard/issues/10000) it's required to test DOM/rendered elements for unit …
cnotv updated
3 weeks ago
-
**Describe the feature:**
Right now, the flaky test runner tool only supports functional test suites. However, Jest tests can also be flaky and sometimes these issues can be difficult to reproduce lo…
-
Uncovered in https://github.com/mozilla/addons-frontend/pull/11593#discussion_r899031000.
Some server-specific tests run w/ Jest's `testEnvironment: 'jsdom'`, which is the project's Jest config defaul…
-
## Steps to Reproduce
```
cd circuits
npm install
npx jest __tests__/TallyVotes.test.ts
```
## Failure Logs
```
/mnt/sdd1/sbw/circom/ZKAP_docker/sbwTest/benchmarks/maci-4892ada0dc7bcc2…
-
#### What's the problem this feature will solve?
Jest and Vitest JUnit Reporters do this, they include: `jest tests` and `vitest tests` as the value of the `testsuites` element's `name` property.
…
-
The jest tests are failing in commitlint because the "load" plugin is not working correctly and is throwing an error "139". It needs to be investigated.
-
[Timer mocks](https://facebook.github.io/jest/docs/en/timer-mocks.html#content) would be useful for [fixing some of our tests](https://github.com/alphagov/accessible-typeahead/pull/108/files#diff-ec01…
-
A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jes…