robotframework / robotframework/RIDE
RunAnything plugin - Expose Context/RF built-in variables ?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 385
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
Hi there!
I'm trying to create a macro with VCS commands to save the tests suites in an automated way so that the QA team can create and save it's tests as needed; But I can't find a way to expose the suite path to the plugin.
Reading a bit I found that the ${CURDIR} is calculated at Execution time but since that's not exposed to the plugin I tried to debug how it's calculated with no luck. I also tried to see how RIDE TestRunner Class calculated the command used to execute the tests, but it seems it's already initialized that way.
With that said, I was wondering if there is a way to save,calculate or expose the current directory being used to the plugin in a RF fashion, or perhaps a feasible work-around.
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 the RunAnything plugin and the RIDE TestRunner class, then compare how ${CURDIR} is calculated at execution time. Determine whether the current suite directory can be exposed to the plugin for VCS commands; done means the plugin can access that directory or a documented workaround is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100