...
Pre-Scripted Testing in OLE means that the tester is inheriting an issue in the OLETS Jira project for which the test case, steps, and automated test script have already been created. This can happen with certain issues, such as bug-fixes which have been requested by the QA team and now need a functional tester. It is also the norm with Round-2 testing of functional specifications.
Click on the images in this guide to expand them. If you have any questions, please email Rich Slabach or Jain Waldrip.
Install Selenium IDE
Selenium IDE is a Firefox plug-in that allows users to record and playback browser automation scripts. You can download Selenium IDE at http://seleniumhq.org/download/. If you do not have the Firefox web browser installed, you can download it from http://www.mozilla.org/en-US/firefox/new/.
...
Click on the "Issues" drop-down menu near the top of the screen. Highlight and click "Search for Issues."
In the "Issue Navigator" pane, on the left-hand side of the screen, find the "Projects" list and scroll down to "OLE Test Scenarios," then click to highlight it. A blue notification bar will appear below the "Issue Type" list:
***info/code box: "Project or Issue Type changed. Refresh search to update form fields."
Click on the red "Refresh Search" link and wait for the page to refresh. Scroll down until you see the title "Issue Attributes" in the Issue Navigator pane. The second field in this section should be "Assignee." Click the assignee drop-down box and select "Current User."***Screenshot - Highlight "Current User" in "Assignee" box
Scroll back up to the top of the screen and click the "Search" button. Once the page refreshes, you should see all of the issues currently assigned to you. ***Screenshot - Search Results
Any issue with a value of "Assigned to Test (RD 1)" or "Assigned to Test (RD 2)" is ready to be tested. Click on the "Key" or "Summary" field for any issue to open it.
...
Once you have the test script downloaded, open Firefox, and then Selenium. You may have an icon providing a shortcut to Selenium on your Firefox toolbar. If not, open the Firefox menu, select the "Web Developer" category, and click on "Selenium IDE." Selenium will open in a separate window.
***Screenshot - Opening Selenium IDE in Firefox
In the Selenium IDE window, click on the "File" menu, select "Open," and navigate to the appropriate test script.***INFO BOX -
| Note | ||||
|---|---|---|---|---|
| ||||
Selenium does not allow multiple test scripts to be selected with the "Open" function. If you need to run multiple test scripts for your OLETS issue, you will need to select "Add Test Case" instead, about halfway down the length of the menu. |
To run the Selenium script, you can click on the "Actions" menu and select "Play current test case," or you can click the icon highlighted in the image below.
***Screenshot - Running a Test Script in Selenium
***INFO BOX -
| Note | ||||
|---|---|---|---|---|
| ||||
The Selenium script will be executed in whatever Firefox window was most recently active. Be careful not to run a Selenium script in a window you've been working in so that you don't lose your work! |
Determine Success or Failure
...
Verify statements are used for two primary reasons in OLE Selenium testing. The first is to test a non-essential condition that may give a reviewer more information about why a test script failed. The second is when a Selenium script is being used to test a large number of values. For example, if a test script is testing an operation performed on a number of requisitions in the Order Holding Queue (OHQ - ***INFORMATIONAL LINK), the script may need to verify that all information about each requisition is displayed correctly in the queue before continuing. In this case, verify statements would be used so that if a single piece of information is missing, the test script can report exactly what information is and is not present.
...
Open the OLETS test case if you don't already have it open. You should see the options "Test Passed" and "Test Failed" at the top of the screen. Click on the appropriate option, and a dialogue box will appear.
***Screenshot - Pass/Fail options (maybe just combine these two?)
***Screenshot - Pass/Fail Dialogue
Enter the current date as the date tested. Next, you will need to select either "Passed" or "Failed" by hand in the section labelled "Test Results." You will also have the option to attach a file by clicking "Choose File," and then selecting the appropriate screenshot or log file in the file selection dialogue. You can attach multiple files, if necessary, by selecting "Choose File" again, after the first file has been attached.
...
If you prefer, you can use the "Attach Screenshot" JIRA function. This function can also be found under the "More Options" drop-down menu. Once you click on the "Attach Screenshot" function, a dialogue box will appear, prompting you to take and attach a screenshot.
***Screenshot - Screenshot Dialogue
You will still need to use your operating system's built-in screenshot function for this dialogue box. Highlight the window you wish to capture, press the Alt + Prnt Scrn key combination, then return to the screenshot dialogue box and click the "Paste" button. Once your image appears in the window, you have the option to enter a filename for your screenshot. You may also enter a comment describing the screenshot in the "Update comment" field. Once you're ready to save your screenshot, just click the "Attach" button. The dialogue box will disappear, and your screenshot and comment will be added to the test case.
...