MarketSquare / MarketSquare/robotframework-seleniumtestability
After using seleniumtestability ;seleniumtestability specific keywords I am not able to access in the test case
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Keep bug reports clean, remove any unnecessary fields and fill in all the information you can. Explain what you where expecting and what you are actually seeing.
And please, direct support questions to #seleniumtestability channel in Robot Framework slack.
In order to help you, run your robot framework tests with --loglevel TRACE:TRACE and attach SeleniunTestability.log from RF's output either as github gist or pastebin link.
## Expected Behavior
## Actual Behavior
## Steps to Reproduce the Problem
1.
1.
1.
## Specifications
- SeleniumTestability version:
- Operating System:
- Browser Version:
- WebDriver Version:
## Log URL
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
No implementation files, tests, or entry points are identified. Start by running the Robot Framework tests with --loglevel TRACE:TRACE and collect SeleniunTestability.log, then fill in the expected behavior, actual behavior, reproduction steps, and version details. Done requires a reproducible report with enough information to investigate the access failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100