Test Scenarios - radhika-c/QA-Features GitHub Wiki

Feature 1:

Trimming of URL spaces in story API:

Text story: Verify whether user will be able to save and publish a story with reference URL with spaces.And spaces are trimmed.
Verify whether API reference URL is also trimmed.
Verify whether user will be able to save and publish a story with Vidible URL with spaces.And spaces are trimmed.
Verify whether user will be able to save and publish a story with Social media URL with spaces.And spaces are trimmed.
Verify whether API Social media URL is also trimmed.
Verify whether API Social media URL is also trimmed.
Verify whether user will be able to save and publish a story with Js Embeds with spaces.And apaces are trimmed.
Verify whether API JS Embeds is also trimmed
Video story: Verify whether Verify whether user will be able to save and publish a story with
Video URL with spaces.And spaces are trimmed.
External story:Verify whether user will be able to save and publish a story with reference URL with spaces.And spaces are trimmed.

Feature 2:

False Error on publish:

1.create story and save it and try to leave the story false error should not appear.
2.create story and dono't save a story,error should appear.

Feature 3:

Scenarios for FB video element url:

1.Verify for the post with photo and text.
2.Verify for post with lot of text.
3.Verify for post with video and text.
4.Verify for post with live video.
5.Verify for post with photo,Video.
Feature 4:

Add Menu Group:

1.Verify when adding menu group it gets added in list.
2.Verify whether user is able to select from list.
3.Verify the menu’s under ‘default’ menu group are only seen in amp version.
4.Verify whether the menu group name given under any menu gets updated in api’s.
5.Verify only when u assign menu group name to one of the menu then only u will be able to select the same to other menus.
Feature 5:

Non Blocking Auto Save:

Verify whether the newly added element gets saved once the auto save is triggered.
Verify whether the deleted element gets removed once the auto save is triggered.
Verify whether the modified version of the elements are seen after auto save is triggered in both existing and newly created story.
Verify adding a new image to the story and cross check whether it is present after the auto save is triggered.
Verify whether changing the caption and attribution of the image stay the same after the auto save
Verify whether the URL added to the socialmedia element gets saved everytime after the auto save
Verify whether the modified URL added and modified is available after the auto save
Verify whether the Js embed added gets saved after the auto save.
Verify whether the entities added to the story is getting saved after the auto saveis triggered.
Verify whether the modified entities details gets saved after the auto save is triggered.
Verify whether the images added to the image gallery element gets saved after the auto save is triggered.
Verify whether the images removed from the image gallery gets removed from the story after the auto save is triggered
Verify whether the story contains the latest version with the changes when refreshed after the auto save.
Verify whether the new card added is present after the auto save is triggered.
Verify whether the removed card is no more present after the auto save
Verify whether the changes made to the card is updated after the auto save
Verify whether the card ordered changed is updated in the story after the autosave triggered.
Verify whether the card share details are updated after the auto save is triggered.
Verify whether the card share details are updated after the auto save is triggered.
Verify whether the card share when switched off stays the same when the auto save is triggered.
Verify whether the Headline that is modified gets saved right after the auto save is triggered.
Verify whether the social share message that is modified gets saved right after the auto save is triggered.
Verify whether changing tabs in the story does not affect teh auto save functionality.
Verify whether the comments added to the elements gets saved when the auto savegets triggered. jumping issue on auto save
When we add text and summary elements for two times then add any other element. Elements are hiding.
Verify Auto save functionality on different states of stories.
Verify functionality of Auto save by Toggle On/Off of "Story Error messages"
Verify functionality of Auto save for card sharing
Verify functionality of Auto save for Multi user editing the same story.
Move elements between cards auto save happens go to workspace and come back to the same story the moved elements change not seen.
Add some text and select draft js element after auto save the tool tip should get disappear.(but it appears)
Irrespective the form is changed or not, Auto save call is triggered(Happens only in Social notificaion tab)
Auto save for live blog story type not working.
Feature 6:

Sitemap image URL's to be configurable:

Config API Url's should be updated as per image repository.
Sitemap also should be updated according to image repository.
Feature 7:

Send published story JSON to WRU:

1. Tested All Story Types except "Story Listicle" by directly publishing stories.
2. Tested All Story Types except "Story Listicle" by setting schedule time to publish stories.
3. Tested All Story Types except "Story Listicle" by rejecting & publishing the same stories.
4. Tested All Story Types except "Story Listicle" by redraft & publishing a stories.
5. Tested the "Story Recommended "Feature" toggle.
6. Create aBlank story with all elements & check WRU call is happening.
7. Change the WRU Merchant key in editor & check its reflecting in WRU's URL.

Issues:

1. If we keep "WRU Merchant key" field is empty on Admin -> Settings -> Other page in Itsman then by default it should take default value in url as 100000. But its not taking default value.
2. If we deliberately fail a call to WRU API, then in itsman logs it should show message as "Could not send the story to WRU".