...
Table of Contents |
---|
outline | true |
---|
maxlevel | 3 |
---|
indent | 5px |
---|
style | none |
---|
separator | newline |
---|
|
|
Anchor |
---|
| DocumentingResultsTestingProcessDocumentingResults |
---|
| TestingProcess |
---|
|
Testing
This article covers how to execute and document the results of your tests in the OLETS Jira project. In some cases, the results you need to document will depend upon which of two testing methods you employ.
...
Top of Page
User Testing
- User Testing consists of the following steps:
- Revising the Test Case
- You will need to revisit the Test case and ensure that the steps, if they exist, adequately match the current functionality of the OLE system.
- If testing steps do not yet exist, you will need to review the steps necessary to fulfill the purpose statement of the Test Case.
- Executing the Steps
- You will need to execute the testing steps by hand. Selenium will need to be running so that it can record your actions.
- Recording Your Results
- Once you have determined whether the test should pass or fail, you will need to advance the Test Case through the workflow, and comment with your results and any other feedback you would like to include.
Top of Page
Top of Section
Selenium Testing
- Selenium Testing consists of the following steps:
- Executing the Selenium Test Script
- You will need to open the Test Case and find the Selenium test script in the "Attachments" section. It will be included as an HTML file, with a name like "OLETS-### - Title of Test Case," where ### is the OLETS Test Case ID.
- Recording Your Results
- In Selenium testing, your comments will largely focus on whether the script passed or failed. If the script failed, you will need to include additional documentation, such as a screenshot or a copy of the Selenium log.
Top of Page
Top of Section
Determining Success or Failure
...
Failure for such issues of nuance is a difficult thing to decide. The QA Team encourages you to think in terms of the big picture: does the software accomplish its task in a reasonably useful way? If so, the best course of action may be to pass the Test Case, but share your insight in a comment so that we can address the issue in a later release of the software.
Return to Section
Return to TopTop of Page
Top of Section
Anchor |
---|
| DocumentSelenium |
---|
| DocumentSelenium |
---|
|
...
It is also worth noting that warnings may appear frequently in the Selenium log file, especially if you happen to be testing a function that involves pop-up windows or items opening in new tabs. These warnings will appear in red, but they will not be bolded, and they will be prefixed with "warn" rather than "error" in the log window. These are just informational messages, and do not signify an impending failure.
Top of Page
Top of Section
Recording Your Results
...