questions missing caught_exception logic

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by comparing the caught-exception handling added for Element in #10. Inspect the Attribute, List, Number, Selected, and Text questions, then verify that their targeting errors are passed to hamcrest assert_that in See as failure reasons.

Written by the indexing model from the issue text.

Description

As part of #10 we updated Element to catch targeting errors so that we could pass the caught exception to hamcrest assert_that in See as the reason for failure.

There a several other questions that didn't get this same treatment.

  • Attribute
  • List
  • Number
  • Selected
  • Text
Dominant language
Python
Stars
7
Forks
2
No merged PRs in 30d

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.

More from ScreenPyHQ/screenpy_selenium

All issues in ScreenPyHQ/screenpy_selenium

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.