# Best Practice on how to efficiently update test stories from failed test stories report **URL:** \ **Category:** \[Deprecated\] Rasa X Community Edition\ **Tags:** testing\ **Created:** [January 7, 2022, 5:05pm UTC](https://forum.rasa.com/t/best-practice-on-how-to-efficiently-update-test-stories-from-failed-test-stories-report/50452 "2022-01-07T17:05:35Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![AndreD](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@AndreD](https://forum.rasa.com/u/AndreD)\ **Post date:** [January 7, 2022, 5:05pm UTC](https://forum.rasa.com/t/best-practice-on-how-to-efficiently-update-test-stories-from-failed-test-stories-report/50452/1 "2022-01-07T17:05:35Z")
**Background:** We have a Rasa-x installation with CI/CD Github Action doing the rasa train & test. We produce our test files continuously with rasa-x. **Issue:** We have already a lot of test stories and when we make a fundamental change in our approach, we must regard all the test stories. Currently we do: 1. Check the failed\_test\_stories.yml → Search for “#” . Evaluate if this is a bug or a change is ok. In example e.g. below we want in the future correct in line 4 and determine that masterdata\_form is ok! 3- action: action\_before\_order\_service\_form 4- action: action\_get\_first\_name # predicted: masterdata\_form 5- action: action\_get\_last\_name # predicted: utter\_bot\_stores\_changes\_in\_d 1. Then we have to lookup the wrong test story in (/tests/test\_stories.yml) in order to change it accordingly – via editor a/o directly in the repo. Another way to fix it could be, throw all outdated test stories way and creating new once with interactive training in the rasay UI. Is there any best practice approach how to more efficiently do that as it really causes high manual effort ? --- _[View the full topic](https://forum.rasa.com/t/best-practice-on-how-to-efficiently-update-test-stories-from-failed-test-stories-report/50452)._