MarketSquare / MarketSquare/robotframework-SikuliLibrary

[WinError 10061] No connection could be made because the target machine actively refused it

Open
#92 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
163
Forks
60
PR merge metrics
No merged PRs in 30d

Description

Hello,

With all my tests I have a .bat script that calls robot:
`SET "LST_PATH=%HOMEDRIVE%\Program Files (x86)\Atlas Copco\LinuxSupportTool 2.0.0.8\LinuxSupportTool.exe"`
`robot --include open_close LST2.0.0.0/`

And in my code I call:
```
*** Settings ***
Documentation LinuxSupportTool test simple open close.
Library SikuliLibrary
Resource ${CURDIR}/resources/shared_var.resource

*** Variables ***
${IMAGE_DIR} ${CURDIR}\\img

*** Test Cases ***
LST Open Close
[Documentation] Open close LST.
[Tags] LST not_ready open_close
Start App
Close App

*** Keywords ***
Start App
Run Keyword If ${INDIVIDUAL_TESTING} == ${FALSE} Return From Keyword
Open Application %{LST_PATH}
Sleep ${APP_LOADING_TIME}

Close App
Run Keyword If ${INDIVIDUAL_TESTING} == ${FALSE} Return From Keyword
Close Application ${APP_EXE_NAME}
```
`INDIVIDUAL_TESTING` is set to true. I get:
![connection_broken](https://user-images.githubusercontent.com/11850698/54270320-748be880-457f-11e9-81e9-1043e5e9e889.png)

What could be the reason for that problem?
Thanks a lot for your help :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the .bat command and Robot Framework test using the shown Open Application and Close Application keywords. Start by checking whether the LST_PATH executable is reachable and whether SikuliLibrary can establish its connection; done means identifying the cause of WinError 10061 and documenting a verified resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
desktop, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.