Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desktop Library | Desktop session error in multi-file test execution #181

Closed
Wolfe1 opened this issue Feb 22, 2021 · 0 comments · Fixed by #182
Closed

Desktop Library | Desktop session error in multi-file test execution #181

Wolfe1 opened this issue Feb 22, 2021 · 0 comments · Fixed by #182
Assignees
Labels

Comments

@Wolfe1
Copy link
Member

Wolfe1 commented Feb 22, 2021

Brought up here: https://forum.robotframework.org/t/unable-to-run-multiple-testsuite-using-zoomba-desktop-library/1348/3

Essentially if we have two test files just like this in a directory:

*** Settings ***
Documentation     Zoomba Desktop Library Tests.
Library           Zoomba.DesktopLibrary
Suite Setup       Start App
Test Setup        Launch Application
Test Teardown     Quit Application
Suite Teardown    Driver Teardown
Force Tags        Windows

*** Variables ***
${REMOTE_URL}           http://127.0.0.1:4723
${APP}                  Microsoft.WindowsCalculator_8wekyb3d8bbwe!App

*** Keywords ***
Start App
    [Documentation]     Sets up the application for quick launching through 'Launch Application' and starts the winappdriver
    Driver Setup
    Open Application    ${REMOTE_URL}     platformName=Windows    deviceName=Windows   app=${APP}
    Maximize Window
    Quit Application

*** Test Cases ***
Switch To Desktop Test
    Close Application
    Switch Application      Desktop
    Wait For And Click Element           name=Start
    Wait For And Click Element           name=Start

And we run the whole directory (so file1, then file 2) and the 2nd file attempts to run 'Switch Application' it is referencing the old desktop session:
image

Need to investigate why the session data is being reused after the applications have been quit and the driver has been torn down.

@Wolfe1 Wolfe1 added the bug label Feb 22, 2021
@Wolfe1 Wolfe1 self-assigned this Feb 22, 2021
Wolfe1 added a commit that referenced this issue Feb 22, 2021
Wolfe1 added a commit that referenced this issue Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant