MarketSquare / MarketSquare/robotframework-SikuliLibrary

SikuliLibrary.Click failing with AttributeError: 'NoneType' object has no attribute 'run keyword'

Open
#153 3 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

Hi,

I am using sikuli library in automation to click on image. But I am getting following error,
AttributeError: AttributeError: 'NoneType' object has no attribute 'run keyword'.

![image](https://user-images.githubusercontent.com/20717294/121490031-4877a000-c9f2-11eb-9386-d55320e8758c.png)

During triaging the issue, I started the sikuli server manually using command " java -jar SikuliLibrary.jar 51248 .". I am not sure whether it started successfully or not. Please find the below screenshot.

![image](https://user-images.githubusercontent.com/20717294/121490779-fb47fe00-c9f2-11eb-8e3d-e32153eabcda.png)

Java version: java version "1.8.0_281"
Java(TM) SE Runtime Environment (build 1.8.0_281-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.281-b09, mixed mode)
Python: 3.7.5
OS: Windows 10 64 bit.

Please help me to resolve this issue.

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 Click failure on the reported Windows 10, Java 8, and Python 3.7.5 environment, then inspect how SikuliLibrary starts and communicates with the server launched by `java -jar SikuliLibrary.jar 51248 .`. Trace why the object used to run the keyword is None; done means the Click keyword works with the documented startup flow or the failure is clearly diagnosed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, python
Domain
desktop, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.