| Anchor | ||||
|---|---|---|---|---|
|
| Center | |||
|---|---|---|---|
|
|
| Anchor | ||||
|---|---|---|---|---|
|
Introduction
Selenium 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 or comments on the material presented in this guide, 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/.
For complete directions on installing and running Selenium IDE in Firefox, please reference the "Installation" section of Getting Started with Selenium.
Find Issues Assigned to You in OLETS
Open the OLETS Jira Project and log in with your Kuali KIS username and password. You will find the "Log In" link in the upper right-hand corner of the page.
...
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.
Download & Run the Selenium Script
Once you have the OLETS issue open, scroll down to the "Attachments" section. The Selenium script will appear here as an HTML file. Right-click on the file and select "Save Link As..."
...
| 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! |
| Anchor | ||||
|---|---|---|---|---|
|
Determine Success or Failure
As Selenium runs, whatever command the application is currently executed will be highlighted in yellow in the "Table" tab. Once the command has been successfully executed, it will turn green. A failed command will turn red and return an error message in the log window.
...
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, 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.
Success
If the test script completes all commands and shows a status of one script run with no failures, then the script was completely successful. All you need to do in this case is pass the test case in the OLETS Jira project and add your comment (as explained below). Adding a screenshot of the successful run is helpful, but completely optional.
Failure
If a test script finishes running with one or more errors, the test was not successful. You will need to document your findings by adding a screenshot and a comment to your test case (as explained below).
...
When a test script fails, the QA team needs to receive information about what caused the script to fail. If there is only one error, you can provide us with this information by taking a screenshot that shows the command which failed during execution. If there are multiple errors, it is more helpful to include the log information as a text file on the test case. This process will be explained in more detail below.
| Anchor | ||||
|---|---|---|---|---|
|
Document Your Findings
Updating the Test Case
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.
...
Once you have entered your comments and any attachments to be added to the test case, you will need to click on the button reading either "Test Passed" or "Test Failed" in the lower right-hand corner of the test results dialogue box. Once you do so, the test results dialogue box will disappear, and your comments and attachments will be added to the test case.
Adding Screenshots
There are two ways to create a screenshot for attachment to a JIRA issue. One is to use the built-in screenshot function on your computer, and the other is to use the JIRA screenshot function.
...
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.
Log Files (Only Needed During Failure)
To attach a Selenium log as a text file, first keep Selenium open after the test has failed. If you've already closed the Selenium application window, you'll need to re-open it and run your test script again to repeat the failure.
...
Now just save the text file and add it as an attachment to the OLETS test case, just as you would a screenshot.
| Center | |||
|---|---|---|---|
|