Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FI-2096 Add list of applicable options to 'Inferno Tests' sheet in test procedure matrix #455

Merged
merged 4 commits into from
Sep 6, 2023

Conversation

arscan
Copy link
Contributor

@arscan arscan commented Aug 14, 2023

There was some confusion about the content in the 'Inferno Tests' sheet because we don't indicate that some tests only apply to certain standards. This PR adds a column to that sheet with that information.

I originally just created it to send to drummond to help explain how that sheet works, but it seems to make sense to include it going forward.

Screenshot 2023-08-16 at 9 48 13 AM

If multiple options apply, they all will be listed. I suppose it would be nicer if we had a column per option, and then filled in that column with option value selected (if any), but that was a little more complicated and this conveys the same amount of information.

Run by doing bundle exec rake g10_test_kit:generate_matrix

@arscan arscan changed the title Add list of applicable options to 'Inferno Tests' sheet in test procedure matrix FI-2096 Add list of applicable options to 'Inferno Tests' sheet in test procedure matrix Aug 16, 2023
runnable_and_parents = [runnable].tap do |parents|
while runnable.respond_to?(:parent) &&
runnable.respond_to?(:suite_option_requirements) &&
(runnable = runnable.parent)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
(runnable = runnable.parent)
(runnable == runnable.parent)

I'm assuming you're intending to do a comparison rather than an assignment here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, this is just bad code that i wrote quickly. This is what allowed the while loop to traverse upwards. I updated the code to be a bit simpler.

I'm not sure if this has to be this complicated though, I just wasn't sure how much options got pushed down to children in the test tree... so i just had it gather all relevant options for itself and all of its ancestors and then eventually do a 'uniq' to throw out any duplicates.

@arscan arscan merged commit 77551c1 into main Sep 6, 2023
3 checks passed
@arscan arscan deleted the options-in-matrix branch September 6, 2023 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants