---
title: User Stories Should Be Testable | Crosstide
description: Learn why making user stories testable is crucial for effective software development and how to refine them to ensure clear, measurable outcomes.
---

[Insights | Crosstide ](https://crosstideconsulting.com/insights)

# [User Stories Should Be Testable | Crosstide](https://crosstideconsulting.com/insights/blog/user-stories-should-be-testable/)

 Written by [Crosstide Consulting Editorial Team](https://crosstideconsulting.com/insights/author/editorial-team) | Sep 3, 2024 11:00:00 PM

The *T* in the the ‘Invest’ acronym (a way to remember and assess what makes a good User Story) stands for Testable.

The most common forms of User Story that are not testable are big User Stories, known as [Epics](https://www.101ways.com/thats-not-a-user-story-thats-an-epic/), or non-functional User Stories…

An Epic can be a User Story that really comprises multiple User Stories. Or perhaps an Epic can also be a User Story that is very complex.

An example from my previous job might be something like: “As a user, I want to calculate the cost of repairing a crashed car”. This is really an Epic and is not really Testable.

Non-functional stories are things like “As a user, I want the system to be fast”, “As a user, I want the system to be secure”, “As a user, I want the system to be easy to use”. None of these things are well written from a Test perspective. Perhaps they could be re-phrased to make more Testable? For instance, “web pages should generally load within 2 or 3 seconds”, “the system should comply with OWASP security standards”…

Let’s take my recent Example of a User Story to see if it’s Testable?

First of all, it’s small and fairly independent, which makes it inherently more testable to start with. This is a simple example so it should be easy to test. The scenarios are: Successful login, Failed login (user id), Failed login (password), Failed login (expired account), Failed login (authentication system unavailable), Remember me (if successful and ticked).

Importantly, identify the tests up-front, before the User Story is implemented. If developers know how the User Story will be tested, maybe they will write it to pass? 🙂

[View full post](https://crosstideconsulting.com/insights/blog/user-stories-should-be-testable/)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Crosstide Consulting Editorial Team"
  },
  "dateModified" : "2025-04-29T13:32:11.045Z",
  "datePublished" : "2024-09-03T23:00:00Z",
  "headline" : "User stories should be testable",
  "image" : {
    "@type" : "ImageObject",
    "height" : 836,
    "url" : "https://24984665.fs1.hubspotusercontent-eu1.net/hubfs/24984665/2094339850.jpg",
    "width" : 1253
  },
  "mainEntityOfPage" : "https://crosstideconsulting.com/insights/blog/user-stories-should-be-testable/",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "Insights"
  }
}
```