# October 2020 digest **URL:** \ **Category:** News & Announcements\ **Created:** [November 3, 2020, 10:27am UTC](https://community.fibery.io/t/october-2020-digest/1123 "2020-11-03T10:27:43Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![AdrianC](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@AdrianC](https://community.fibery.io/u/AdrianC)\ **Post date:** [November 3, 2020, 3:13pm UTC](https://community.fibery.io/t/october-2020-digest/1123/7 "2020-11-03T15:13:48Z")
Yes, that’s it in a nutshell. I have to create a Test Plan Run to start with, then execute each test case in the Test Plan and in turn execute each Test Step for each Test Case I will show you an example, I have 2 test plans under a development ( which is a collection of user stories / use cases ) Development / Test Plans ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/078378e639758f7931e835ce86875eed6604b70e.png) You can see 2 test plan runs for the test plan ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d37c518a8b493f0aa7684aecd388d07788c7f65b.png) 1 test failed on the first run and 1 was on hold The 4 tests passed on the second run I didn’t set up any test steps on this example, I just wanted to indicate the test plan / test case relationship --- _[View the full topic](https://community.fibery.io/t/october-2020-digest/1123)._