UNIVERSAL STUDIOS/IBM

K2 Testing Procedure
Steps for Successful QA Completion
4/1/2016

0
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

Purpose: The purpose of this document is to outline the steps needed in order to
properly run QA test scenarios against K2 user stories.
Steps:
1. Sign in to VPN
2. Navigate to http://uso12qtcm13/ (Tridion Content Editor)
3. Select Content Explorer
Follow the following folder path in order to navigate to the component template
folder that you will be testing:
\020 UO.com Content Master (EN-US)\Building Blocks\Content\UO.com Content Angular\UnitTests\Navigation

4.

1
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

5. Open the folder of the component that you will be testing

6. From Rally, copy the QA url and paste into a new tab (this will bring you to
the web page)

2
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

7. Take a screenshot of the web page and leave the web page open. You will use
this screenshot to the web page after making your edits to ensure that your
edits were populated.
8. Return to Tridion Content Editor. Make an edit to each piece of editable
content. Take screenshots to capture each edit.
a. For text fields and the text within CTA (call to action, or buttons)
fields we suggest adding -ONE to the first change, -TWO to the
second change, and so forth.
b. In the link portion of CTA fields change the link to
http://universalorlando.com/
c. For image fields, change the image to one of the images provided by
the onsite K2 team.
If there is an additional piece of content that is editable, but was no described
in the user story, raise a defect for the item. If there is an item that is
described as editable in the user story, but the field is not in content editor,
raise a defect. All defects should be assigned to Michael Berkhofer, who will
then assign them to the appropriate developer. Please refer to the How to
Test Using Rally and Defect Creation Process decks I have provided to
understand how to properly execute tests and record defects.

3
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

9. Once you have made all of the necessary edits, click Save and Close.

10.Follow the following path and open the component that you saved in the
previous step: 060 UO.com Website (EN-US) Root UnitTests
11.Click Publish. Ensure that QA Staging, QA Live, and Publish Content
Now are selected. Click the Publish button. This will publish the changes
to the web page.
12.Navigate to back to the web page that you took a screenshot of in Step 7 of
this procedure. Hit the refresh button in the browser. Once the page loads
you should be able to view all of the changes that you made in Step 8 of this
procedure.
13.Validate that every field that you made edits to in Step 8 of this procedure
have populated correctly on the web page. As you are doing this, record
screenshots. Each one of these validations will have a separate test scenario
and will require the screenshot the screenshots captured in Steps 7 and 8 of
this procedure, as well as the one taken during this step.

4
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

a. For text fields, if you follow our advice of changing the text fields you
should be able to count the number of changes, i.e. if you made 10
text field changes you should be able to count -ONE, -TWO TEN
b. For CTA fields, click the link and ensure that you are taken to the link
that you provided when you modified it.
c. For image fields, ensure that the image was changed to the image you
provided when you modified it.
14.Next, you must test the rendering of the screen at every required breakpoint.
We will focus on breakpoints H, D, and A only. In order to set the breakpoint,
resize your browser and look at the bottom right corner of the screen. You will
see the breakpoint that your screen is currently set at. Ensure that all the
elements are rendering correctly (i.e. no overlapping/modified text, stretched
images, or anything else that makes the screen unsettling to read or
consume). There should be an individual test scenario for breakpoints H, D,
and A. Record your results in Rally.

5
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

6
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

15.Finally, you will need to test the experience manager functionality of Tridion.
To do this click the SDL Tridion box in the top left corner of the page. This
will bring you to a screen in which you can make in line edits to fields on the
web page.

16.You will be brought to Tridion Experience Manager (see screen below):

7
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

17.In order to modify a text field, hover your mouse over the field (will be
outlined in green) and click. For example, if you were to do this over the
Appetizers header you should see the following on your screen if successful:

18.Modify the changes that you made to each piece of editable content in Step 8
of this procedure (each should be a separate test scenario).
a. For text fields, If you followed our advice you should be deleting the
numbers that you added. For example, in the template below you will
delete -ONE in the Appetizers header.
b. For CTA fields, change the field back to the original link (the one you
modified in Step 8)
c. For image fields, change the image back to the original image (the one
you modified in Step 8).
Record a screenshot after making each edit. After making the changes
click the Finish Editing button in the top toolbar. You can modify every
field that you edited in Step 8 so that you only need to test the experience
manager for a given page once.

8
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

19.After you click Finish Editing you need to publish the page. Click the
hamburger menu in the top left corner of the page, then click Content
Explorer.

20.Follow the following path and open the component that you were working on
in the previous step: 060 UO.com Website (EN-US) Root UnitTests

9
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

21.Click Publish. Ensure that QA Staging, QA Live, and Publish Content

Now are selected. Click the Publish button. This will publish the changes
to the web page.

22.Return to the web page and ensure all changes that you made via Experience
Manager were made. Record a screenshot of the entire page. Return to Rally
and record the results. Your Experience Manager test cases should have a
screenshot of the original web page (after the initial change was made in
Step 8), a screenshot of the act of changing (Step 18), and a screenshot of
10
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015

the web page after making the edit via experience manager (Step 22, this
step).

11
UNIVERSAL AND IBM CONFIDENTIAL

March 28, 2015