robotframework / robotframework/RIDE
Preprocess testrunner variables in first place, and then test suite definitions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 385
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
This is certainly a corner case, but it may be relevant for fix for similar situations.
When using the Remote library (which is a library not having keywords and doc) we pass the host address and port. RIDE consults this URL to obtain the keywords documentation defined in that remote library. But, if the URL is defined with variables, and they are only defined in options to pybot/robot, then the documentation is not found. Here is proposed for RIDE before trying to find documentation (and variables definitions) to consult the definitions at testrunner arguments text.
Examples:
Contributor guide
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 by tracing how RIDE processes Remote library URLs and resolves variables supplied through pybot/robot options before looking up keyword documentation. The change is complete when variables defined in testrunner arguments allow the remote library URL to resolve and its keyword documentation to be found, as shown by the provided examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100