New keyword "Compare Query Results"
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. Start by locating the existing query-related keywords and their tests, then clarify row ordering, row-count mismatches, output formatting, and assertion behavior. Done means the comparison keyword, error reporting, and visual difference output have defined behavior for equal and unequal results.
Written by the indexing model from the issue text.
Description
The keyword should compare results of two SQL queries and show the difference.
The arguments would be like query_1, query_2 and assert_results_equal (True or False).
If False, there is no assertion - just show print the difference in the RF log.
Both queries must deliver the same columns - same numbers and the same names.
It has to be implemented in the queries themselves.
The output should look like a merged table
- The columns are the same, they're merged (no duplicated cols like Col_A_Query_1 and Col_A_Query_2 - just Col_A).
- The cells with not equal values should get a red background and contain both values like
Value 1 != Value 2. - The column name and the row number with a cell with unequal values shall be highlighted as well.
- And maybe keep them visible during the scrolling (sticky scroll)?
- All other cells with equal values should be either not highlighted at all or get a green background maybe.
Apart from the visual highlighting, there should be an assertion to provide the keyword status and the error message
- The error message should not include all details, but maybe a number of rows and column names? Like this: X rows had differences in cols A, B and C?
The very first check though should be the comparison of row number in results
- If they are unequal, there should be an error message (without details) - and an additional visual output.
- Visually, it would be maybe nice to print both tables aside and highlight rows, which exist in one of the results only - in green and red, like git merge style?
- No further assertions are performed in this case.
- Dominant language
- Python
- Stars
- 179
- Forks
- 178
- 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/Robotframework-Database-Library
-
new_client
Difficulty 3/5 1-2 days Newbie friendliness 48/100
MarketSquare/Robotframework-Database-Library#260 · 1 comment ·
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
MarketSquare/Robotframework-Database-Library#256 · 4 comments ·
-
improvement
Difficulty 5/5 Over a week Newbie friendliness 45/100
MarketSquare/Robotframework-Database-Library#255 · 2 comments ·
-
new_client
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MarketSquare/Robotframework-Database-Library#195 · 1 reaction ·
All issues in MarketSquare/Robotframework-Database-Library
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Add .devin pluginOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ayghri/i-have-adhd#249 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelscope/FunASR#3762 ·
Maintainers usually reply within 1 day