Basic Test Management app

[edit: since posting, I’ve made an updated version, scroll down]

I shared this app elsewhere in the Fibery community, but I figured I could leave a link to it here as well, so that it might be easier to find.

Here are the type relations:

The idea is that a Test Case can be defined with a collection of named Steps (each with an Action and an Expected Result).

When the ‘Execute Test Case’ button is pressed, a linked Test Execution is created (automatically assigned to the current user and named with the day’s date). The Test Execution is created with a collection of Step Results - one for each named Step in the Test Case.

Using auto-linking to connect the Step Results to the correct Steps (based on matching the Test Case and entity names) the Step Results inherit (read-only) fields for the Action and Expected result.

Each Step Result has an editable Actual Result field, which to be filled in by the tester when the test is run, together with a Pass/Fail/TBD single-select field.

By doing all this, it’s possible to have a table view for all the Step Results of each Test Execution showing Action, Expected result, Actual result and Outcome.

I also added a bit of logic so that the overall outcome of the Test Execution (pass or fail) can be determined based on the outcomes of the Step Results, and some date comparison logic so that it’s easy to see whether a Test Execution is the latest one for that Test Case.

I designed a Vizydrop report to summarise the results, but it seems that this does not get included in the shared app, sorry :-/

Anyway, hope it might be useful or inspirational for someone. There’s obviously lots of room for improvement/enhancement, so please add your own tweaks and re-share :slight_smile:


Following the discussion on the October 2020 digest…

I think I get it, and I will have a go at adding that functionality.

1 Like

Reports, Whiteboards and Smart Folders are not supported yet in App Sharing. We are working on it and will add them soon.

I’ve created a slightly enhanced version with Test Plans and Test Runs now included. I have also added a few extras:

  • made use of the name-formula feature recently introduced
  • introduced some mechanisms for checking if the Test Execution has become out-of-sync with the Test Case (for example the text of the Test Case changes)
  • added buttons to choose Pass, Fail or TBD for each Step Result and timestamp it

The App lends itself well to being configured with smart folders and reports, but these are not yet supported, as Michael has indicated, so I have just included some simple tables and boards. If you install it, I suggest creating smart folders: one for Test Plans and Test Cases (with a table of Steps) and one for Test Runs and Test Executions (with a table of Step Results).

Hope someone (maybe @AdrianC) finds it useful (or at least inspires others to make something useful :slight_smile:)


The user voice feed back can help fitst these ux , report working parlele to others as thes make usaer more interest , , logicaly bad report can be version 1 bad to better,Thus app withour good resuls report , the experiments , progress delay too .Chr1sG very good work need user feedbacks to have progress , This wiki edu feedback app , i am trying 02 yeras , now well made wiki feedback 1 wiki creator to 60 user depency can explode fibery memory space, but many high impact thes meet based wiki dpenden feedback all projects need