Scenario NothingIsFound passes any refusal as if it were the empty page
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 358
Description
## Goal
A scenario whose then is NothingIsFound fails when the call is refused, naming the exception it got.
## Background
tests/scenario/bai_scenario/components/answers.py: when the response is None, NothingIsFound.look returns Refused(type(answered.raised), answered.raised). Refused only complains when the raised exception is not an instance of the expected type, and here the expected type is the raised type itself, so any refusal is reported as '거부: ' with no problem and the row passes. A row meant to see an empty page cannot tell a refusal from success.
## Acceptance criteria
- NothingIsFound (and any then in the tree that names the raised type as the expected one) reports a problem when the call is refused.
- The rows using it still pass, and their report.md lines do not change.
## Related
- BA-7776 (scenario test tree)
- BA-7809 (found while transcribing the resource policy rows)
JIRA Issue: BA-7842
Contributor guide
Research direction
Start in tests/scenario/bai_scenario/components/answers.py, focusing on NothingIsFound.look and Refused, then inspect the scenario test tree referenced by BA-7776. Confirm that a refused call is reported as a problem rather than an empty page, while the existing rows still pass and their report.md lines remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100