MarketSquare / MarketSquare/robotframework-sherlock

Could this tool check for errors likes "Multiple keywords with name XXX found" ?

Open
#71 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
14
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I had a test suite failing due to this error:

```
FAIL | Multiple keywords with name 'Read Json File' found. Give the full name of the keyword you want to use:
module1.Read Json File
module2.Read Json File
```
Screenshot from HTML report:
2022-08-25 16_06_44
Python source code of `module1.py`:
```python
import json

def read_json_file(filepath):
with open(filepath, encoding='utf8') as file:
return json.load(file)

...
```
Python source code of `module2.py`:
```python
from module1 import read_json_file
...
```
Usage in `feature.resource`:
```
Library ../libraries/module1.py
Library ../libraries/module2.py
...
${body}= Read Json File ${CURDIR}/postPayload.json
```

Could `robotframework-sherlock` be able to detect the error raised at runtime by Robot Framework?

Note: I previously asked for the same feature to be added to https://github.com/MarketSquare/robotframework-robocop/issues/687 who mentioned this interesting project

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 failure using module1.py, module2.py, and feature.resource, then inspect how robotframework-sherlock currently analyzes Robot Framework usage. The work is complete when the tool detects and reports the ambiguous “Multiple keywords with name” error represented by these duplicate libraries.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.