-
Notifications
You must be signed in to change notification settings - Fork 475
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
Ability to isolate tests #742
Comments
similar to #743 |
Hi @ekelali Thank you for the response. e.g. file: controlid123: Thanks uk-bolly |
Also, this issue may be related, maybe this should be done for all resource types? |
hi @ekelali Apologies for the delay, thanks |
Describe the feature:
Running industry benchmarks testing these can mean ensuring that different lines may occur within the same file each with a unique test. These will have differing titles, meta data dependent on the test that takes place.
I am sure this type of testing that may occur is not unique to this but the is an example i am working with.
In the example below
It appears the filename used by the file test is the unique identifier and therefore only take the output of the final test that runs. These benchmarks for each line could be in the same file or different files. Only the last benchmark that runs using the goss test reports the output.
e.g.
file:
/etc/somefilename:
{{ if .Vars.test1 }}
title: test1
exists: true
contains:
- test1_line
meta:
test1_ID
other_data
{{ end }}
{{ if .Vars.test2 }}
title: test2
exists: true
contains:
- test2_line
meta:
test2_ID
other_data
{{ end }}
If both are enabled the output would only show test2 information.
I have tested with different files, filenames etc.
Is there a better way that i can achieve this?
Describe the solution you'd like
Ability to run the different requirements on using a like goss test and control that is able to report back all the output and the associated data
Describe alternatives you've considered
Rewrite each control with the command test and rename that command title to make them unique. But using the actual goss test is more efficient and less calls than running the command test.
The text was updated successfully, but these errors were encountered: