Storyplayer v2
Goto:
All Sections:

This Section

  1. Test Your Code
  2. Why Component Testing?
  3. What Are You Testing?
  4. Sample Layout For Source Code Repo
  5. Designing Your Test Environment
  6. Defining Your System Under Test
  7. Recommended First Tests
  8. Designing Component Tests
  9. Writing Component Tests
  10. Final Thoughts

Guide To Testing Your Code With Storyplayer

Storyplayer is commonly used for two types of testing:

  • Component testing: these tests are designed to thoroughly test a single app or service. They’ll use the app’s documented interfaces, and they’ll also check log files, databases, and anything else where the app makes changes. These stories normally live in the same code repository as the source code for what they are testing. You’ll normally deploy your code into a one-off virtual machine to run this test, to prove that your app or service works as intended.
  • End-to-end tests: these tests will your platform by automating the actions that your end-users can do. They’ll only use the same APIs and interfaces that your end-users can use, and they’ll never attempt to access anything that your end-user isn’t allowed to access. These stories normally live in their own code repository. You’ll normally run these stories against your test, staging and production platforms, to prove that your product or service works in that environment.

In this guide, you’ll learn how to use Storyplayer to test a single app or service.

In This Guide

This guide contains a step-by-step process to testing a single app or service using Storyplayer: