MarketSquare / MarketSquare/robotframework-SikuliLibrary
FAIL : AttributeError: 'NoneType' object has no attribute 'run_keyword' in windows XP
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 163
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
Dear Wang Yang,
I use robotframework + sikulilibrary for the first time,I encountered a problem
When I use the keywords of sikulilibrary, I get the following error:
**Starting test: Test.Run-Sikulilibrary-Keyword.double click
20200326 15:37:38.609 : FAIL : AttributeError: 'NoneType' object has no attribute 'run_keyword'
20200326 15:37:38.609 : DEBUG :
Traceback (most recent call last):
File "E:\Python2.7.17\lib\site-packages\SikuliLibrary\sikuli.py", line 255, in run_keyword
return self.remote.run_keyword(name, arguments, None)
Ending test: Test.Run-Sikulilibrary-Keyword.double click**
please help me
EV:
Windows XP Professional x86
python -m pip List
Package Version
------------------------------ -----------
numpy 1.16.6
Pillow 6.2.2
pip 20.0.2
Pygments 2.5.2
PyPubSub 3.3.0
pywin32 227
robotframework 3.1.2
robotframework-ride 1.7.4.1
robotframework-seleniumlibrary 4.3.0
robotframework-SikuliLibrary 1.0.8
selenium 3.141.0
setuptools 41.2.0
six 1.14.0
urllib3 1.25.8
wxPython 4.0.7.post2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SikuliLibrary/sikuli.py at line 255 and reproduce the failing keyword using the listed Python 2.7, Robot Framework, Windows XP, and SikuliLibrary 1.0.8 environment. Investigate why self.remote is None; done means the SikuliLibrary keyword runs without this AttributeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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