# Failed Story in test stories **URL:** \ **Category:** Rasa Open Source\ **Tags:** testing\ **Created:** [August 4, 2022, 3:50pm UTC](https://forum.rasa.com/t/failed-story-in-test-stories/54661 "2022-08-04T15:50:51Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![AndreD](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@AndreD](https://forum.rasa.com/u/AndreD)\ **Post date:** [September 5, 2022, 12:13pm UTC](https://forum.rasa.com/t/failed-story-in-test-stories/54661/2 "2022-09-05T12:13:21Z")
Hi jalowiec, I am hanging around with storytesting as well as you can see here: > [@End to end story testing; how to read results of failed\_test\_stories.yml](http://forum.rasa.com/t/end-to-end-story-testing-how-to-read-results-of-failed-test-stories-yml/53859): > > Hi all, I am hanging around for a while now without success regarding end to end testing. It all starts already how to interprete the results of the test run being written into failed\_test\_stories.yml. Currently the overall results show 3 of 30 test stories are correct, which results in having 27 in the failed\_test\_stories.yml. What I understood so far from the docs then is that one can expect the #tag to indicate where the test story deviates from the prediction. But here my problem starts - c… I have currently two major topic with that: 1. Nobody seems to know how to read the failed test stories file. For my understanding the hash-tag (#) should indicate wrong predictions, which gives you a hint where the story fails. **Problem here:** I have quite often more rejected stories in the file than hash-tags. **→ Why is that ?** 1. I found differences between my CI/CD chain and my local test runs I am still in the middle of my investigation here, but honestly I have no clue what this might be, as all data- and config-files are the same … --- _[View the full topic](https://forum.rasa.com/t/failed-story-in-test-stories/54661)._