How To Automate: Understanding Screenplay – Refactoring to Screenplay

Reading Time: 4 minutes

Welcome to our latest series of How To articles on EuroSTAR Huddle. This three part series is on Understanding Screenplay and is brought to you by Matt Wynne, one of the world’s leading BDD practitioners and co-founder of Cucumber.

Part 3

In the previous post in this series, we explored the need for a new kind of pattern for organising our test automation code.

Now we’re going to work with this little codebase to refactor it towards the Screenplay pattern. By taking the existing code and shifting it, step-by-step, towards the pattern, my hope is that you’ll see how you could do this to your own code, should the fancy take you.

If you want to follow along, you can start from this commit in the example code.

Where do we start?

When refactoring to Screenplay, I’ve found it’s best to start with the smallest elements of behaviour first. The leaf-nodes, if you will. So we need to look for a helper method that just does one thing.

Let’s pick the createAccount helper method in the DomainDriver:

  createAccount({ name }) {
    this.app.accounts[name] = new Account({ name })
  }

We call this method twice from our steps. First, we use it for creating accounts:

Given('{word} has created an account', function (name) {
  this.createAccount({ name })
})

Then, later, we use it as part of signing up:

Given('{word} has signed up', function (name) {
  this.createAccount({ name })
  this.activateAccount({ name })
})

We’ll work with the first instance to turn this into a Screenplay interaction. We’ll come back to the second one later.

Let’s inline the first instance so that…​

Given('{word} has created an account', function (name) {
  this.createAccount({ name })
})

becomes…​

Given('{word} has created an account', function (name) {
  this.app.accounts[name] = new Account({ name })
})

Now we have the code back up in the step definition, we can re-shape it into a Screenplay style.

Info

Extract Interaction

We’ll put the code that does this work into an arrow function expression which will become our first Interaction. The interaction takes all the dependencies and information it will need to do its work. In this case, it needs a reference to the app it will use to fetch the accounts, and the name of the actor.

To complete this first refactoring, we call the interaction function, passing the name from the step definition and a reference to the app.

Given('{word} has created an account', function (name) {
  const interaction = ({ name, app }) => app.accounts[name] = new Account({ name })
  interaction({ name, app: this.app })
})

Now the code does the same as it did before. We can run npm test at this point to check all our scenarios are still passing.

Actors perform Interactions using Abilities

Back in the first part of this series, we talked about the metaphor for Screenplay being actors on a stage.

In the metaphor, the actor is said to have abilities: the things it needs to be able to perform the actions it’s given. In practice, these are the dependencies that the interaction functions will expect to be passed, like a browser or a database connection. We’ll take these as we construct the Actor.

We’ll add a method that attempts to perform an interaction, by simply passing these abilities to the interaction and calling it:

class Actor {
  constructor(abilities) {
    this.abilities = abilities
  }

  attemptsTo(interaction) {
    interaction(this.abilities)
  }
}

Perfect. Now, the actor has everything it needs to be able to attempt to perform an action.

Here’s how we use the shiny new Actor in our step definition:

Given('{word} has created an account', function (name) {
  const interaction = ({ name, app }) => app.accounts[name] = new Account({ name })
  const actor = new Actor({ name, app: this.app })
  actor.attemptsTo(interaction)
})

To construct the actor, we’re creating a bare JavaScript object representing the actor’s abilities to pass to the constructor; in this case their name and whatever attributes are on this.

Then we call attemptsTo on the actor, passing it our interaction.

Again, we can run npm test at this point to check all our scenarios are still passing.

Using a custom parameter type

Since the Screenplay pattern centres around these Actors, we don’t want to have to keep constructing them in our step definitions. Fortunately, Cucumber gives us custom parameter types that allows us to transform the text Sue, Tanya or Bob into an instance of Actor that represents them.

Here’s how we do that:

const { defineParameterType } = require('cucumber')

defineParameterType({
  name: 'actor',
  regexp: /(Sue|Tanya|Bob)/,
  transformer: function(name) {
    return new Actor({ name, app: this.app })
  }
})

Now we can ask for an instance of Actor in our step definition, by using the new custom parameter type:

Given('{actor} has created an account', function (actor) {
  const interaction = ({ name, app }) => app.accounts[name] = new Account({ name })
  actor.attemptsTo(interaction)
})

Our code is getting neater, but we’re not done yet.

Info

Naming our Interaction

An idiom that Screenplay’s original authors used was to adopt a fluent interface for creating interactions. Let’s rename our interaction in this style, calling it CreateAccount.forThemselves. We do this by creating a plain JavaScript object, CreateAccount, with a property forThemselves that returns the interaction function expression:

const CreateAccount = {
  forThemselves:
    ({ name, app }) => app.accounts[name] = new Account({ name })
}

Now we can use that in our step definition:

Given('{actor} has created an account', function (actor) {
  actor.attemptsTo(CreateAccount.forThemselves)
})

In fact, since we’re no longer using this, we can now use an arrow function for our step definition:

Given('{actor} has created an account',
  actor => actor.attemptsTo(CreateAccount.forThemselves)
)

Wrapping up

Hopefully you can see things starting to fall into place. We’re delegating the work in our step definitions off to actors and interactions. The actors have abilities that enable them to perform the interactions, but they’re completely decoupled from those interactions themselves. Each interaction is a separate JavaScript function that takes the abilities and does something to the system.

This decoupling enables this pattern to scale really well. We can add new interactions easily, without creating extra dependencies or bloated helper classes.

All of this leaves us with step definitions that are much more readable than before, with a clear mapping from the plain English in our Gherkin steps to the code that carries out the step.

The real beauty of the actor-interactions model is that interactions are composable: we can build up more interesting actions out of fine-grained interactions, like putting lego pieces together.

In the Understanding Screenplay series:

Part 1: Myths & Fundamentals

Part 2: Help! Maybe my helpers aren’t so helpful after all?

Part 3: Refactoring to Screenplay

See other Test Automation Resources on EuroSTAR Huddle.

About the Author

Matt Wynne

In 2008 Matt joined the Cucumber open source project as a developer. In 2011 The Cucumber Book was published which he co-authored with Aslak Hellesøy. In 2013 he co-founded Cucumber Ltd, dedicated to inspiring meaningful and effective collaboration in every software organisation. Cucumber Ltd was acquired by SmartBear in June 2019, and Matt now works as a BDD Advocate, working to spread good software development and agile testing practices around the world.
Find out more about @mattwynne

Leave a Reply