Conversation
…ayed by checkbox-cli [fix]
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1986 +/- ##
=======================================
Coverage 50.60% 50.60%
=======================================
Files 384 384
Lines 41180 41180
Branches 7636 7642 +6
=======================================
Hits 20841 20841
+ Misses 19594 19592 -2
- Partials 745 747 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fc4fe2c to
1ada613
Compare
|
The same version of black is giving me conflicting advice. Black 25.1.0 fails here saying: so Black 25.1.0 apparently doesn't like that single line dictionary. But Black 25.1.0 locally always wants to reformat that to a single line. (I changed that offending dictionary to match what Black 25.1.0 is saying here, and then when I run Black 25.1.10 diff locally I get this: So... which black 25.1.0 is correct? and why am I getting two conflicting bits of advice here? this is going to be messy if I have to run black to reformat code and then have to undo it because black doesn't like what black did. |
Hook25
left a comment
There was a problem hiding this comment.
Please remove the un-related changes and the untested script
d52d367 to
57ffccf
Compare
…ayed by checkbox-cli (BugFix) (#1986) Clear up duplicated test plan names that lead to confusion when displayed by checkbox-cli [fix]
…ayed by checkbox-cli (BugFix) (#1986) Clear up duplicated test plan names that lead to confusion when displayed by checkbox-cli [fix]
…ayed by checkbox-cli (BugFix) (#1986) Clear up duplicated test plan names that lead to confusion when displayed by checkbox-cli [fix]
…ayed by checkbox-cli (BugFix) (#1986) Clear up duplicated test plan names that lead to confusion when displayed by checkbox-cli [fix]
Description
After some discussion on MM led me to running checkbox-cli directly to test some thing, I noticed that a few test plans had duplicate names with no context, which become quite confusing when displayed via checkbox.
After working through this I found a lot more than initially seen so I made an effort to fix all of the duplicated test-plan name fields so that when listed in checkbox-cli, all test plan names are unique and any potential duplicates have some sort of context... for example there were many "after suspend" test plans that had the same name as their "before suspend" counterparts.
Resolved issues
fixes CHECKBOX-1966
Documentation
No doc changes needed, I believe, the name field is only really used in the list of test plans in the Checkbox UI and CLI (e.g.
checkbox-cli list 'test plan' --format='json' --a | jq -r '.[] | "name: " +.name + " id:" + .id' | sort)Tests
Doublechecked the changes by re-running the analyze_testplans.py script claude created while I was having it analyse the providers directory.
Example before and after:
Also ran a quick find/grep and visually checked to doublecheck the script as well.
for x in `find ../providers/ -name test-plan.pxu`; do cat $x |grep "name: " |sort; done |less