![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
active-enzyme
Advanced tools
Boilerplate-free Enzyme testing.
$ npm install --save-dev active-enzyme
Enzyme is a great tool for performing tests on React components, especially using shallow rendering. This little library augments it with some niceties that allow you to easily lookup an element by className
and save the resulting ShallowWrapper
to a variable which is active--that is, it doesn't need to be requeried again after things change.
In a nutshell, a test such as this:
import React from 'react'
import { shallow } from 'enzyme'
import Greeting from './Greeting'
it('greets in multiple languages', () => {
const name = 'John'
const wrapper = shallow(<Greeting name={name} />)
expect(wrapper.find('.greeting').text()).toBe(`Hello, ${name}!`)
wrapper.find('.switchLanguage').simulate('click')
expect(wrapper.find('.greeting').text()).toBe(`Bonjour, ${name}!`)
wrapper.find('.switchLanguage').simulate('click')
expect(wrapper.find('.greeting').text()).toBe(`Hello, ${name}!`)
})
can instead be written like this:
import React from 'react'
import { shallow } from 'active-enzyme'
import Greeting from './Greeting'
it('greets in multiple languages', () => {
const name = 'John'
const {
greeting,
switchLanguage
} = shallow(<Greeting name={name} />).classes
expect(greeting.text()).toBe(`Hello, ${name}!`)
switchLanguage.simulate('click')
expect(greeting.text()).toBe(`Bonjour, ${name}!`)
switchLanguage.simulate('click')
expect(greeting.text()).toBe(`Hello, ${name}!`)
})
The two main features at work here are:
classes
property which allows you to query based on a class names. This is nice because it allows you to use ES2015 destructuring syntax as above to select all the rendered elements you care about for a given test.'click'
events), because the greeting
and switchLanguage
wrappers are normally immutable. This library instead returns active wrappers, which change in response to the element tree being re-rendered.Since the most common usage pattern is that you have a bunch of tests all testing the same component, there is a makeRenderer()
utility which allows the individual tests to simply vary the props they're going to render it with:
import { makeRenderer } from 'active-enzyme'
import Greeting from './Greeting'
const render = makeRenderer(Greeting)
it('greets in multiple languages', () => {
const name = 'John'
const { greeting, switchLanguage } = render({ name }).classes
expect(greeting.text()).toBe(`Hello, ${name}!`)
switchLanguage.simulate('click')
expect(greeting.text()).toBe(`Bonjour, ${name}!`)
switchLanguage.simulate('click')
expect(greeting.text()).toBe(`Hello, ${name}!`)
})
This has the nice added bonus that you no longer need to import React in your test suites!
FAQs
Boilerplate-free Enzyme testing
The npm package active-enzyme receives a total of 2 weekly downloads. As such, active-enzyme popularity was classified as not popular.
We found that active-enzyme demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.