- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1
Closed
Labels
Best PracticeNot functionality problem, but refactor need itNot functionality problem, but refactor need itDocumentationRelated to documentationRelated to documentationFeatureNew functionality proposalNew functionality proposalTestcase
Description
TODO
-  knows about ENV name for opera browser driver
- test about : "-Dopera.binary="
- test about : "-Dwebdriver.opera.driver="
 
- add new drivers to module qadrivers
- add to one public node and test it manually FAILED at 12-12-2017
Documentation
http://www.opera.com/es/computer
Tests
- test for mode local and browser_name opera
- test for mode remote and browser_name opera
- manual test for mode remote and browser_name opera , opening page
- manual test for mode remote and browser_name opera , using webelement
- manual test for mode remote and browser_name opera , using ControlBase
Manuals
Need to test combinations for
- env var command lane -Dopera.binary= and -Dwebdriver.opera.driver=
 -->
- node browser name opera and operablink
 -->
- python remote browser name opera and operablink
- var name 1 + node name 1 + python selenium code 1
- var name 1 + node name 1 + python selenium code 2
- var name 1 + node name 2 + python selenium code 1
- var name 1 + node name 2 + python selenium code 2
- var name 2 + node name 2 + python selenium code 1
- var name 2 + node name 2 + python selenium code 2
Issues related
- official opera chromium based OperaDriver should look for the Opera executable on the PATH by default operasoftware/operachromiumdriver#9
- qadrivers, update binary from v0.2.32 to v0.2.33 Update operadriver to v0.2.33 qadrivers#5
Metadata
Metadata
Assignees
Labels
Best PracticeNot functionality problem, but refactor need itNot functionality problem, but refactor need itDocumentationRelated to documentationRelated to documentationFeatureNew functionality proposalNew functionality proposalTestcase