Enhancement: For error tests, log the value that is used as trigger on a high level in the log.html for quicker debug analyses
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start by tracing the error-test flow that produces log.html and locating where the value triggering an error response is available. Review how API field rules are represented before deciding whether to log only the trigger value or also its accepted type and length; done means the generated log exposes the relevant value and error tests verify the output.
Written by the indexing model from the issue text.
Description
The actual used value that should trigger an error responsecode is currently quite deep hidden on debug loglevel. This makes debuganalyses sometimes pretty hard. And only if de API indeed throws the error message.
If the response does not contain the errormessage it is not clear what value should have triggerd it.
Perhaps it is possible to add this value to the log like:
Log error trigger value is ${value}
Even better if the reason or api specs for the specific field are added.
Log error trigger value is ${value} , accepted value is integer with max length 5
- Dominant language
- Python
- Stars
- 28
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from MarketSquare/robotframework-openapitools
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
MarketSquare/robotframework-openapitools#141 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MarketSquare/robotframework-openapitools#134 · 1 comment ·
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
refactor
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in MarketSquare/robotframework-openapitools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100