Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 75 Next »

This testing grid is intended to act as a minimal set of tests which should be run before each release. For more details on the format of this page and for a full test suite, please see the full Storytelling Tool Manual Testing Grid


Grid last updated:
February 26, 2021

Tests last completed: February 26, 2021


Action sequences:

  1. Story Builder: User is able to publish a story with no blocks and no other fields filled in
  2. Story Builder: User is able to publish a story with one empty block of each type and no other fields filled in (empty, but with empty blocks too)
  3. Story Builder: User is able to publish a story with two text blocks
  4. Story Builder: User is able to publish a story with two image blocks, both images uploaded from the file system*
  5. Story Builder: User is able to publish a story with two image blocks, both images captured from the device*
  6. Story Builder: User is able to publish a story with two image blocks, one image captured, one image uploaded*
  7. Story Builder: User is able to publish a story with two audio blocks, both files uploaded from the file system*
  8. Story Builder: User is able to publish a story with two audio blocks, both files captured from the device*
  9. Story Builder: User is able to publish a story with two audio blocks, one file captured, one file uploaded*
  10. Story Builder: User is able to publish a story with two video blocks, both files uploaded from the file system*
  11. Story Builder: User is able to publish a story with two video blocks, both files captured from the device*
  12. Story Builder: User is able to publish a story with two video blocks, one file captured, one file uploaded*
  13. Story Builder: User can publish a story with one block of each type and all the fields filled in
  14. Story Builder/Viewer: Listening to the story with the Orator plays the story completely both in the Story Preview and on viewing a published story, and the Orator highlights text as it reads
  15. All pages: Imagery changes along with UIO contrast theme changes
  16. Back and forward within the editor steps works properly, state is not remembered on page reload
  17. Story Viewer: User sees appropriate error message when trying to load a story with an invalid ID
  18. Story Builder: User sees appropriate error message when trying to edit a story with an invalid ID
  19. Story Builder: User is able to load a published story into the editor, make changes and republish

* for the sequences that require two images, videos, audio files, etc. the intent is that these files be different from one another. I.e. for two uploaded images, make sure they're different images.


Device NameOS & VersionBrowser & Version12345678910111213141516171819
Apple iPad Air 3iOS 13.3Safari6PassPassPassPassPassPass11PassPassPassPassPassPass3, 4PassPass7
Desktop PCWindows 10 Pro v.20H2Chrome 886PassPassPassN/AN/APassN/AN/APassN/AN/APass2Pass4PassPass7
Desktop PCWindows 10 Pro v.20H2Firefox 866PassPassPassN/AN/APassN/AN/APassN/AN/APassPassPass4PassPass7
Google Pixel 5Android 11Chrome 866PassPassPassPassPassPassPassPassPassPassPassPass2Pass4PassPass7
MacBook Pro 15" (mid-2015)macOS High Sierra 10.13.6Safari 13.0.26PassPassPassN/AN/APassN/AN/APassN/AN/APassPassPass4PassPass7


Issues noted in latest pass:

Issue #JiraDescription
1

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Audio capture option is not presented, can only upload. Likely not much to be done about this, as it may depend on Firefox not sending the same Android Intents as Chrome. This is a previously known issue.

2

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The Orator highlighting does not appear at all. This is a previously known issue.

3

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Safari can navigate back through history after publishing
4

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

After traversing backward through history in the story editor and refreshing the page, can navigate forward.
5

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

iPad: Uploading freshly-captured image, the block editor preview did not appear, though the file uploaded and showed in the story preview just fine. Issue went away after capturing a new photo
6

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Stories can no longer be published with no content (and no blocks added), so Test 1 will always fail. It appears to publish successfully, but since the localStorage ID was null, the author is redirected to the View page with a story ID of null afterwards, which of course fails.

Consider removing this test from the grid, or adding a check for null story before publishing, and then adjusting this test to reflect the check

7

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Since accounts are not enabled on the staging site, Test 19 is no longer usable. Either enable accounts on the Staging site (needs a Jira + work) or remove this test
  • No labels