Test status text from output.xml is not parsed
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 48/100
Research direction
Start in robot_results_parser.py at _parse_test_status, then inspect database_writer.py at _create_table_test_status. Use the provided output.xml example to verify that the test status message is parsed and stored in the database as a TEXT column.
Written by the indexing model from the issue text.
Description
It seems that error message in test status is not parsed from output.xml and saved to db. Fixing this would only require adding two lines of code (one for parsing and one for column creation):
- robot_results_parser.py --> _parse_test_status --> 'message': test.message
- database_writer.py --> _create_table_test_status --> 'message': 'TEXT'
E.g. "Keyword 'Wait Until Element Is Visible' failed ..." should be parsed (simplified example from output):
<test><status status="FAIL" endtime="20190201 13:21:01.497" critical="yes" starttime="20190201 13:20:09.986">Keyword 'Wait Until Element Is Visible' failed ...</status></test>
- Dominant language
- Python
- Stars
- 60
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/DbBot
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MarketSquare/DbBot#27 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MarketSquare/DbBot#26 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
MarketSquare/DbBot#24 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MarketSquare/DbBot#23 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MarketSquare/DbBot#22 · 3 reactions ·
All issues in MarketSquare/DbBot
Similar issues
-
deployment release-lag
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nolte/kamerplanter#2047 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-plugin-claude-subscription-directsdk#94 ·
Maintainers usually reply within 1 day
-
namespace operations
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day