Bring your user and service stories to life through your test automation.
Storyplayer is DataSift’s in-house tool for automating the testing of our user and service stories. Storyplayer makes it easy to test both your front-end website and your back-office services. Storyplayer can test both functional and non-functional requirements. It sits between unit testing tools such as PHPUnit (used by your developers) and acceptance testing tools such as Behat (used by your product team).
Written in PHP, Storyplayer is highly modular, and can be easily extended to support your own custom needs.
What Can You Test With Storyplayer?
Storyplayer was initially designed and built to test DataSift’s real-time firehose-filtering product. This is a service-oriented architecture consisting of:
- Data piplines (using ZeroMQ and HTTP)
- Supporting services (using HTTP and sometimes ZeroMQ)
- Internal and public-facing APIs (using JSON over HTTP)
- Front end interfaces (using HTML)
Storyplayer can test software written in any language, because Storyplayer is designed to interact with your software just like a user would.
Built For Developers And Testers Alike
From the very beginning, Storyplayer has been designed as a testing tool for software engineers (who want to write code using the language they already know, not learn yet another DSL) and testers (who want a toolkit that allows them to focus on creating sophisticated tests with the minimum of code).
User And Service Stories
The skeleton of a strong development process is the story.
- Each user story is a simple description of one feature or benefit that your product or service provides.
- They are written in plain English, and they include clear acceptance tests and a place to record the ‘why’ behind anything that your product or service provides.
- They can be shared between your product teams, your project management, your architects, your engineers and your testers.
- Service stories are exactly like user stories, but for internal services and APIs.
Storyplayer is designed from the outset to automate the testing of all of your stories - to fill that gap between unit testing and product acceptance testing.
All stories are written in the PHP that you already know using a style that we call Prose (so-called because we like the whole story telling theme). Prose is a way of writing PHP code that makes it not only natural to read, but also to think about stories. There’s no DSL to learn!
At the heart of Prose is the $st dynamic module loader, which makes it hard not to share code between your tests. We’ve already published over 15 re-usable modules - you can get started with your testing right away - and it’s very easy to create your own Prose modules when you need to do something that we haven’t already covered.
For those larger and more complicated apps (like the DataSift platform), Storyplayer can provision and destroy whole test environments to run your tests against. Today, Storyplayer ships with fully-working support for Vagrant and EC2.
Storyplayer works with a large variety of web browser and platform combinations. You can test using the web browsers running on your desktop or laptop. We’ve integrated with SauceLabs for automated cross-browser testing of your apps. And, for advanced users, we support remote WebDriver instances too.
You’re reading the front-page of Storyplayer’s online manual, over 50,000 words covering:
- installation and configuration of Storyplayer
- what stories are, and their test phases
- how to write tests for your stories, and how to create your own Storyplayer modules
- how to create test environments to test your apps in
- a comprehensive reference to every module that ships with Storyplayer
The documentation is still a work in progress, with regular updates as we get everything thoroughly documented for you.
Storyplayer is open source software.