npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

morphonent-test

v0.4.3

Published

testkit for morphonent applications

Downloads

12

Readme

morphonent-test

Build Status Coveralls github npm npm bundle size npm npm GitHub issues GitHub pull requests

morphonent-test is a testing library for verifying components written with morphonent.

  • Easy. Bundled with sensible defaults.
  • Fast. Runs entirely without mounting components in the DOM, for fast and easy checking.
  • Async by default. Designed to work with asynchronous components as easy as with synchronous components.

Installation

morphonent-test is a simple npm package that you can install with yarn:

$> yarn add -D morphonent-test

or npm:

$> npm install --save-dev morphonent-test

Getting Started

morphonent-test exposes a component wrapper entirely made for introspecting and interacting with real components with a fluent API. We've also designed the library to be TDD friendly, so it's easy to change and mold to your needs.

Let's see an example test, using jest as the test runner.

import { testing, click } from 'morphonent-test';

describe('Counter component', () => {
  describe('counting upwards', () => {
    it('should count +1 when the button is clicked', async () => {
      const counter = (count) => element('button', { id: 'add-1', onclick: () => counter(count + 1) }, count);
      const driver = testing(counter(0));

      const currentCount = await driver.findById('add-1').trigger(click()).textContent();
      expect(currentCount).toBe('1');
    });
  })
})

You can also mock more concrete behaviour if you extract your event handlers.

import { testing, click } from 'morphonent-test';

describe('Counter component', () => {
  describe('counting upwards', () => {
     it('should count +1 when the button is clicked', async () => {
      const counter = (count, next) => element('button', { id: 'add-1', onclick: () => next(count + 1, next) }, count);
      const fakeCounter = jest.fn(count => count)
      const driver = testing(counter(0, fakeCounter));

      const currentCount = await driver.findById('add-1').trigger(click()).textContent();
      expect(fakeCounter.mock.calls[0][0]).toBe(1);
      expect(currentCount).toBe(1);
    });
  })
})

API

testing

Builds a test component based on a root component. This is the main entrypoint to the testing library.

TestComponent.findWhere

Allows you to find a component given a condition. This is a low-level function and should be used only when strictly needed. Finding a component based on arbitrary conditions can be a hot-spot of bugs and expensive tests.

const blueGreen = testing(() => element('div', {}, element('div', { class: 'blue' }, 'Blue'), element('div', { class: 'green' }, 'Green')))

const green = blueGreen.findWhere(el => el.props && el.props.get('class') === 'green')
expect(await green.textContent()).toBe('Green')

TestComponent.findById

Allows you to find a component given it's ID.

const blueGreen = testing(() => element('div', {}, element('div', { id: 'blue' }, 'Blue'), element('div', { id: 'green' }, 'Green')))

const green = blueGreen.findById('green')
expect(await green.textContent()).toBe('Green')

TestComponent.findByClass

Allows you to find a component given it's class name.

const blueGreen = testing(() => element('div', {}, element('div', { class: 'blue' }, 'Blue'), element('div', { class: 'green' }, 'Green')))

const green = blueGreen.findByClass('green')
expect(await green.textContent()).toBe('Green')

TestComponent.findChildren

Allows you to find the children elements of a component, if any.

const blueGreen = testing(() => element('div', {}, 'Blue', 'Green'))

const all = await blueGreen.findChildren().textContent()
expect(all).toStrictEqual(['Blue', 'Green'])

TestComponent.findFirst

Allows you to find the first element of a children tree.

const blueGreen = testing(() => element('div', {}, 'Blue', 'Green'))

const blue = await blueGreen.findChildren().findFirst().textContent()
expect(blue).toBe('Blue')

TestComponent.findNth

Allows you to find the Nth element of a children tree, starting from 0.

const blueGreen = testing(() => element('div', {}, 'Blue', 'Green'))

const green = await blueGreen.findChildren().findNth(1).textContent()
expect(green).toBe('Green')

TestComponent.unfinishedTransition

Allows you to navigate through the first step of a transition.

const firstStep = () => 'Hello'
const secondStep = async () => 'Bye'

const all = testing(() => transition(firstStep, secondStep))
const result = await all.unfinishedTransition().textContent()

expect(result).toBe('Hello')

TestComponent.finishedTransition

Allows you to navigate through the second step of a transition.

const firstStep = () => 'Hello'
const secondStep = async () => 'Bye'

const all = testing(() => transition(firstStep, secondStep))
const result = await all.finishedTransition().textContent()

expect(result).toBe('Bye')

TestComponent.write

Simulates a set of events for writing text using the keyboard on the current selected component. By default, it triggers the onkeypress event, but you can define any event that might suit your test.

const text = faker.internet.userName()
const input = (value) => element('input', { type: 'text', onkeypress: (ev) => input(ev.currentTarget.value.toUpperCase()), value })

const result = await testing(input('')).write(text).textContent()
expect(result).toBe(text.toUpperCase())

Changing the type of event to be triggered:

import { keyup } from 'morphonent-test'

const text = faker.internet.userName()
const input = (value) => element('input', { type: 'text', onkeyup: (ev) => input(ev.currentTarget.value.toUpperCase()), value })

const result = await testing(input('')).write(text, keyup).textContent()
expect(result).toBe(text.toUpperCase())

TestComponent.trigger

Simulates an event on the current selected component and switches the pointer to the root component that returns the event handler. Right now, there are four default event types:

  • click()
  • keypress(keyCode)
  • keydown(keyCode)
  • keyup(keyCode)

But you can trigger other events using the event(name, props) function. For example, the keypress event is implemented as:

export function keypress (keyCode) {
  return event('onkeypress', { keyCode })
}

An example test that clicks on a button that shows a message would be:

const hello = (clicked) => element('div', {},
  element('button', { id: 'button', onclick: () => hello(true) }, 'Click me!'),
  element('span', { id: 'log' }, clicked ? 'Yes!' : 'No!')
)

const test = testing(hello(false))
const clickedTest = test.findById('button').trigger(click())
const content = await clickedTest.findById('log').textContent()
expect(content).toBe('Yes!')

TestComponent.attribute

Returns a promise with the value of the specified attribute on an element.

const myComponent = element('div', { awesome: 'yes' })
const awesome = await testing(myComponent).attribute('awesome')

expect(awesome).toBe('yes')

TestComponent.textContent

Returns a promise with the text content of an element. If the component has a value attribute, it will return it's value instead (for inputs, for example).

const myComponent = element('div', { awesome: 'yes' }, 'Hello World!')
const awesome = await testing(myComponent).textContent()

expect(awesome).toBe('Hello World!')

TestComponent.count

Returns the number of elements matched.

const list = () => element('p', {}, 1, 2, 3)

const result = await testing(list).findChildren().count()
expect(result).toBe(3)