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

feynman

v0.0.23

Published

A screenplay pattern library for javascript

Downloads

10

Readme

Feynman

A library for helping you organise your JavaScript test automation code, inspired by the screenplay pattern.

What's lovely about screenplay, as opposed to other patterns for organising automation code like page objects, is that you're building abstractions around behaviour, rather than solution implementation. We think you're going to like it.

Copared to other screenplay implementations we've seen, what's unique about Feynman is that you can define multiple perspectives that allow you to run the same tasks against your application in different ways.

More on that later.

We're going to assume you know little or nothing about the screenplay pattern and explain this from the ground up. Let's start with an example.

A simple example

const { actor } = require('feynman')

const dave = await actor('dave')
await dave.attemptsTo(PostMessageInSlack)

What's going on here?

First, we call the actor method to get hold of an Actor who we've given the label "dave". It doesn't matter what we call our actor in this example, but you'll see why it's useful later on.

Next, we ask Dave to attempt an Action, PostMessageInSlack.

In order to make this code work, we'll need to define that action, as well as giving dave an Ability that lets our action post messages in Slack.

First we create the action:

const channel = 'YOURCHANNEL' // should look like CFCJMB2K0
const PostMessageInSlack = ({ slack }) => slack.chat.postMessage({ channel, text: "Hello world!" })

So our PostMessageInSlack action is defined as a function that takes a slack named parameter, representing the Slack web client API, and calls the API to post a message.

How do we give dave this ability?

(async () => {
  const { actor, abilities } = require('feynman')
  const { WebClient } = require('@slack/client')
  const token = process.env.SLACK_TOKEN
  const slack = new WebClient(token)

  abilities({ slack })

  const channel = 'YOURCHANNEL' // should look like CFCJMB2K0
  const PostMessageInSlack = ({ slack }) => slack.chat.postMessage({ channel, text: "Hello world!" })

  const dave = await actor('dave')
  await dave.attemptsTo(PostMessageInSlack)
})()

That's the fundamentals of using Feynman. Read on to learn more about:

  • Composing actions
  • Creating actions that take parameters
  • Giving actors memory
  • Using perspectives to run your tests at different levels of the stack
  • Using feynman with different test frameworks