Hi, Please find bellow test cases

*** Settings ***
Documentation     A test suite with a single test for valid login.
...
...               This test has a workflow that is created using keywords in
...               the imported resource file.
Resource          resource.robot
Library           SeleniumLibrary   plugins=SeleniumTestability;True;30 Seconds;True
Library           Collections


*** Test Cases ***
Valid Login
    Open Browser To Login Page
    Set Storage Item  ${key}    ${value}    storage_type=sessionStorage
    Success Page Should Be Open
    [Teardown]    Close Browser

When I run test cases I am getting bellow error

Valid Login :: A test suite with a single test for valid login.               
==============================================================================
Valid Login                                                           | FAIL |
No keyword with name 'Set Storage Item' found.
------------------------------------------------------------------------------
Valid Login :: A test suite with a single test for valid login.       | FAIL |
1 critical test, 0 passed, 1 failed
1 test total, 0 passed, 1 failed

Error log

2020-07-20 09:19:54,245 - SeleniumTestability - DEBUG -  **** New Session Created for SeleniumTestability  **** 
2020-07-20 09:19:54,245 - SeleniumTestability - DEBUG - __init__(<SeleniumLibrary.SeleniumLibrary object at 0x10cd5ff40>,True,30 Seconds,True,True)

Versions

robotframework==3.2.1
robotframework-seleniumlibrary==4.4.0
robotframework-seleniumtestability==1.1.0
selenium==3.141.0

Add support for setting / getting and deleting values from localStorage & sessionStorage.

Most of this is easy to dict types within localStorage should do some json parsing.

Sub tasks:

1. make the flask test application (or some sub page of it) in assets/ to be atleast twice as big as a running viewport
2. add new suite that uses all scrolling keywords
3. Verifies that scrolling pends while scrolling is happening.

Expected Behavior

• SeleniumTestability should wait for 30 seconds instead of 5 secs

Actual Behavior

• SeleniumTestability wait for 5 secs and raise a timeout exception

Steps to Reproduce the Problem

1. Execute the robot test file as an example below
   https://pastebin.com/XRfDwR4e

Specifications

• selenium python package version: 3.141.0
• SeleniumLibrary version: 4.1.0
• SeleniumTestability version: 0.0.15
• Operating System: Windows
• Browser Version: Chrome 78
• WebDriver Version: Chromedriver 78

SeleniumTestability Log URL

https://pastebin.com/pp1NFZxc

Robot output.xml URL

https://pastebin.com/b5j0qa5v

Webdriver spec has commands to generate touch events but SeleniumLibrary doesn't support these yet. Implement in Testability

Add feature to detect viewport scrolling and mark those as waitable events

1. get webelement
2. check its x,y
3. check if other elements are in same coordinates via document.elementFromPoint(x,y) (overlays?)
4. move viewport
5. reiterate from 2 if necessary.

Hi,

It would be very intersting to have the ability to log or to get the detail of the reason why we are waiting during the execution of "Wait For Testability Ready".

Thanks.

Keep bug reports clean, remove any unnecessary fields and fill in all the information you can. Explain what you where expecting and what you are actually seeing.

And please, direct support questions to #seleniumtestability channel in Robot Framework slack.

In order to help you, run your robot framework tests with --loglevel TRACE:TRACE and attach SeleniunTestability.log from RF's output either as github gist or pastebin link.

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

Specifications

• SeleniumTestability version:
• Operating System:
• Browser Version:
• WebDriver Version:

Log URL

Background: sometimes in our staging we face a problem with 3rd party components (analytics and digital marketing to track the event) from time to time so it would be great if we can have this kind of the ability to scope down the request waiting for just the url we are interested (our system under test of course)

Expected Behavior

atest/logs.robot should pass on all platforms.

Actual Behavior

Fails on windows firefox because there´s rows in geckolog that are not in other platforms.

Steps to Reproduce the Problem

1. run current atest/logs.robot on windows

Specifications

• SeleniumTestability version: current
• Operating System: windows
• Browser Version: latest
• WebDriver Version: latest

Implement Open New Window keyword.

optional arguments url and switch_to

Current codebase uses os.path stuff here and there, rewrite the parts to use pathlib

Hey,

It looks like the 2.0.0 release does not include the changes mentioned in it. Subsequently the pypi package is also wrong.

https://github.com/MarketSquare/robotframework-seleniumtestability/releases/tag/v2.0.0 & https://pypi.org/project/robotframework-seleniumtestability/

For example: The DesiredCapabilities for Opera is still present.

Could you update it, so it matches the changes?

Thanks!

Best,
Tadej

Patching:

        window.navigator.geolocation.getCurrentPosition = function(success) {
            var position = {
                "coords" : {
                    "latitude": "%s",
                    "longitude": "%s"
                }
            };
            success(position);
        }'''
            % cords
        )

and fetching:

    def get_coordinates(self) -> tuple:
        latitude = self.execute_script(
            '''
        latitude = ""
        window.navigator.geolocation.getCurrentPosition(function(pos) {
            latitude = pos.coords.latitude
        });
        return latitude
        '''
        )

        longitude = self.execute_script(
            '''
        longitude = ""
        window.navigator.geolocation.getCurrentPosition(function(pos) {
            longitude = pos.coords.longitude
        });
        return longitude
        '''
        )

from https://github.com/dillonm197/extended-webdrivers/blob/master/extended_webdrivers/extended_webdriver.py

Let's say we have an ecommerce website, create an order and go to checkout for payment.
If the website redirect user to payment gateway and when get redirected back after successfully make a payment to its origin ecommerce website, the ecommerce website still require the basic authen.

Implement a feature to save and load cookies to a file.

Would allow sharing some session data between different browsers and/or run sessions.

https://adiralashivaprasad.blogspot.com/2018/05/how-to-get-css-attribute-value-in-robot.html

if test running environment is not able to load the images, tests will fail as no animations or transitions are done towards missing images.

For uploading files via dropzone and similar javascript frameworks.

Hello,

I apologize as I am new to this, but wanted to see if there is a work around for this.

When using Selenium Library version 4.0.0b3 I am getting the follow error below, yet when using version 3.141.0 it will run successfully. We installed the latest version of Selenium to test against Edge browser. Do you have a fix for this?

[ ERROR ] Error in file ‘C:\GIT\Repos\Eclipse\UPEnterprise_Robot\tests\Regressions\UPExchange\UPXREGEditProperties.robot’ on line 2: Initializing library ‘SeleniumLibrary’ with arguments [ plugins=SeleniumTestability;False;5 Seconds;True ] failed: Importing test library ‘SeleniumTestability’ failed: AttributeError: type object ‘DesiredCapabilities’ has no attribute ‘PHANTOMJS’
Traceback (most recent call last):
File “C:\AppData\Local\Programs\Python\Python37\lib\site-packages\SeleniumTestability_init_.py”, line 2, in
from .plugin import SeleniumTestability
File “C:\AppData\Local\Programs\Python\Python37\lib\site-packages\SeleniumTestability\plugin.py”, line 43, in
class SeleniumTestability(LibraryComponent):
File “C:\AppData\Local\Programs\Python\Python37\lib\site-packages\SeleniumTestability\plugin.py”, line 148, in SeleniumTestability
“phantomjs”: DesiredCapabilities.PHANTOMJS,
PYTHONPATH:
C:\GIT\Repos\Eclipse\UPEnterprise_Robot
C:\AppData\Local\Programs\Python\Python37\python37.zip
C:\AppData\Local\Programs\Python\Python37\DLLs
C:\AppData\Local\Programs\Python\Python37\lib
C:\AppData\Local\Programs\Python\Python37
C:\AppData\Roaming\Python\Python37\site-packages
C:\AppData\Local\Programs\Python\Python37\lib\site-packages

Expected Behavior

Drag and drop works correctly

Actual Behavior

Test throw errors right at the beginning and when it reaches drag and drop it fails the test

Steps to Reproduce the Problem

1. Upgrade to 4.0.0b3
2. Run any test that has seleniumtestability
3. Run test with drag and drop

robotframework==4.0.1
robotframework-pythonlibcore==2.2.1
robotframework-requests==0.8.0
robotframework-selenium2library==3.0.0
robotframework-seleniumlibrary==5.1.3
robotframework-seleniumtestability==1.1.0
selenium==3.141.0

I have just followed the link from the README to the documentation page, and got a 404 error.

http://omenia.github.io/robotframework-seleniumtestability

Currently, the instrumentation file is generated by release time and shipped within the python package.

It would be beneficial that users of SeleniumTestability to provide their own instrumentation.

One approach could be to publish the js part of our code as npm, then allow people to publish (or have a local copy) their own copy which could be taken into use at runtime to pointing some sort of environment variable to the package.

So I have a problem where testability automatic wait is somehow enabled after a test fails. I've used Disabled Testability Automatic Wait in the suite setup to disable it during the suite execution. When a test fails inside the suite, it moves on to the next test (as robot should) and the first selenium keyword that is executed fails with this error: TimeoutException: Message: Timed out waiting for testability ready callback to trigger. This is problematic as a single failed test will fail all of the tests that come after it in the testsuite.

As a test I put a call for Disabled Testability Automatic Wait as the first step in the test case that causes this TimeoutException, and the test passed. This leads me to believe that the automatic wait is somehow enabled after test failure.

Expected Behavior

Testability automatic wait should not be enabled at runtime automatically. If testability automatic wait is disabled in the setup, it should stay disable during the suite.

Actual Behavior

Testability automatic wait is enabled after any test case fails.

Steps to Reproduce the Problem

1. Create suite with more than 1 test case
2. Import seleniumlibrary with the testability plugin
3. Create suite setup that disables testability automatic wait
4. Make it so that the first test case fails. (fe. wait for element that is not present)
5. Run the suite

Specifications

• SeleniumTestability version: 1.1.0
• Operating System: WIN10-Pro 64bit
• Browser Version: Chrome 85.0.4183.102
• WebDriver Version: ChromeDriver 85.0.4183.83

Log URL

SeleniumTestability.log

I have also enclosed the failing keyword stacktrace from the html.log file: HtmlLog

SafeConfigParser that versioneer uses was removed with 3.12 python release so installation from source code will not work.

Automatic waiting was set to True as boolean parameters where not converted to bool's ..

via furl ..

Supporting angular should add waits for angular & angularjs and custom locators.

I was trying to generate the libdoc for SeleniumTestability using the following command in Command Line:
python -m robot.libdoc SeleniumLibrary::plugins=SeleniumTestability

However, it ends in an error message as follows:

Could not import runpy module
Traceback (most recent call last):
File "C:\Program Files\Python39\lib\runpy.py", line 14, in
import importlib.machinery # importlib first so we can test #15386 via -m
File "C:\Program Files\Python39\lib\importlib_init_.py", line 57, in
import types
File "C:\Program Files\Python39\Lib\site-packages\SeleniumTestability\types.py", line 2, in
from typing import Union, Optional, List, Dict
File "C:\Program Files\Python39\lib\typing.py", line 23, in
import contextlib
File "C:\Program Files\Python39\lib\contextlib.py", line 6, in
from functools import wraps
File "C:\Program Files\Python39\lib\functools.py", line 22, in
from types import GenericAlias
ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (C:\Program Files\Python39\Lib\site-packages\SeleniumTestability\types.py)

Any ideas on how to fix this?