Test XFLOW story

thIs an example of an Xflow that is used to open an object type called "test video". The "test video" object type was created so that a test user could store a screen recording they made whilst running through a series of planned tests on website.

The Test series was first built by a test engineer, with individual "Tests" being created for different use cases.

Then, it was decided that a video of the test would be the best record of the test, for for future review.

During each test the tester first takes ownership of the "Test" itself (by associating to is as "Tester"). They then start the Test and commence a screen recording. 

At the end of the test they would complete the "Test" record and upload the Test Video to the Test.

The Test Reviewer would subsequently review the screen recording, as if witnessing the test as it happened. This XFLOW provides the Test Reviewer with access to the video whilst also recording that the Test Reviewer did the review.

The Test Videos are always available for the Test Reviewer to watch. But we needed to record that the video has been viewed at least once.

This XFLOW first checks if there are any test videos remaining to be reviewed. It then checks if the video being opened is receiving its first review, by checking a specific property of the "Test Video" object called "PreloadVideo".When the "test video's" were added to the system, this property was deliberately set to "noneSelected". So the XFLOW checks if the PreloadVideo property is "noneSelected". If it is, then it sets it to "Load Auto".

It then checks to see if there are ANY remaining videos to be tested. If there aren't it opens the video in the Xpor video viewer. If there are some test videos remaining to be reviewed, it will pop out a message for the reviewer to be told that there are still remaining videos to be reviewed, after this one has been reviewed and then opens the video in the XPOR video viewer.

the XFLOW flow path goes like this.

"Get data" xflow block has the "root object" selected as the "Test". This is used as the Root for the selected "DataSource". This datasource is built to Start with the "Test" object and list out the "Test Videos" "contained by" the "Test".

It then applies a filter to this list, to return those videos that do not have the "PreLoadVideo" property set to "Load Auto". I.e. it returns all Videos yet to be reviewed.

It gives the list of "Test Videos" it ahs generated, a variable name "Videos Not Yet Reviewed".

The flow then uses an Evaluate Property block, to check if the returned table "Videos Not Yet Reviewed" contains any entries (exists).

If the "Videos Not Yet Reviewed" table is empty, the XFLOW passes along the No path and fires the next XFLOW block, a "Stop XFLOW block.

if the list does contain at least one video, the XFLOW follows the "Yes" path and moves to the next XFLOW block, a "Question Block". This pops out a question form, where we ask the user if they want to continue to watch the video, as this will then result in the system recording that the Video has now been reviewed.

If they select YES, then the XFLOW will follow the Yes path from the Question block, to the next block, a Set Value block. This block has

1. the On Object configuration option set to the video being tested

2. The Video Property being set to "PreloadVideo"

3. The Property Value set to "Load Auto"

This will set the Video property called "PreloadVideo" to "Load Auto".

The XFLOW then passes tot he next XFLOW block, an "Open Video Viewer" block, which has the Video selected. This will play the video for the user