Someone has an example of redux modules in this template? Because I do not really understand how to connect more than 1 module in the component.

It has come to our attention (through trial and error) that this package is no longer needed for users of Jest 24 or later. jest@24.x.x ultimately includes jsdom, of which a recent version added localStorage and sessionStorage support out of the box.

I think it would be worth calling this out somewhere in the docs of `jest

Describe the solution you'd like
Implementation of the attached logout overlay message UI based on code guidlines.

This component needs to be under Layouts which is displayed in the [ignitus-UserInte

Although the two source streams and the result stream have all a length of 5, an exception is thrown.

Reproduction:

import { cold, hot } from 'jest-marbles'
import { buffer, mergeAll } from 'rxjs/operators'

describe('test', () => {
  it('should not fail', () => {
    const source1 = cold('AB--|')
    const source2 = hot('^-A-|')
    expect(source1.pipe(buffer(source2), mergeAl

Is this a bug or feature request?

B

What is the current behavior?

Some vulnerable package deps

Which are the steps to reproduce?

see snapshot

What is the expected or desired behavior?

Package should be updated and no vulnerability repo

with a jest.config.js containing
module.exports = {
browser: false,
clearMocks: false,
globals: {
"pageContextRequestContextPath":"./"
},
runner: "jest-electron/runner",
testEnvironment: "jest-electron/environment",
verbose: true,
};

When doing console.log("test"); in my tests it doesn't print anything in the console.
When I switch to runner: "jest-runner",
and

Thanks for the demo. Really helpful for the beginners. One thing I saw while reading react-native-testing-library docs is, it states that it is a replacement for Enzyme here.

So do we really need to add Enzyme to replicate your tutorial? I haven't actually started to write my tests yet.

OpenAPI version
3

Describe the bug
I have a spec that works if I pull it down, write it to a file and then pass that file path into chaiResponseValidator(specPath).
After pulling down 0.7.0 - I was expecting that the feature in 0.6.0 to just do an HTTP get and pass the data portion of the response in would work.
However, it appears that the code is inspecting the input and looking

When attempting to override a global specified in the jest.config.js we've found it isn't overriden.

We have a set of globals which are basically stubs (in jest.config.js) e.g.

module.exports = {
    globals: {
        YJ: {
            i18n: {
                react: {}
            }
        }
    },
    ...

Then when using jest-wrap to override the i18n key in that glob

Currently new Babel supports typescript. Use it.
Also update security and deprecation varnings.

• Use babel
• Update dependencies
• Fix security issues
• Fix CI

When you search for a seed, the results can be wrapped strangely in narrow browsers:

In the regular jest .toEqual(), you see the line in the JSON that is off with all the surrounding JSON lines. In this package's .toBeDeepCloseTo() you only see the line in the JSON that doesn't match - with no context of where in the JSON it appears - not even the key.