Skip to content

scorecard - add new identifier field to config.yaml #4617

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

Closed
jmccormick2001 opened this issue Mar 8, 2021 · 4 comments
Closed

scorecard - add new identifier field to config.yaml #4617

jmccormick2001 opened this issue Mar 8, 2021 · 4 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. scorecard Issue relates to the scorecard subcomponent
Milestone

Comments

@jmccormick2001
Copy link
Contributor

Feature Request

Describe the problem you need a feature to resolve.

allow for a unique test ID to reference a scorecard test, this would support xunit output processing for example.

Describe the solution you'd like.

today, scorecard has a simple test name for each test, for some systems that process test results, it would be beneficial to allow a user to specify a unique ID

https://source.redhat.com/groups/public/polarion/polarion_importer_documents/polarion_results_xunit_importer#jive_content_id_Using_the_default_Custom_id_of_Test_Case_ID

So, within the scorecard config.yaml, maybe a solution is to add another field within the expected config.yaml schema that lets users enter an ID if they choose, this would be an optional field.

@jmccormick2001
Copy link
Contributor Author

[email protected]

@nellyc
Copy link

nellyc commented Mar 8, 2021

Thanks @jmccormick2001
This ask directly ties into the junit/xunit feature requests[1]
I can provide more details if needed

[1] #4616 & #4488 we can probably close 1 of them if we can agree on 1 schema .

@jberkhahn jberkhahn added kind/feature Categorizes issue or PR as related to a new feature. scorecard Issue relates to the scorecard subcomponent help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 8, 2021
@jberkhahn jberkhahn added this to the Backlog milestone Mar 8, 2021
@theishshah theishshah self-assigned this Mar 9, 2021
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 8, 2021
@theishshah
Copy link
Member

added in API pr110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. scorecard Issue relates to the scorecard subcomponent
Projects
None yet
Development

No branches or pull requests

5 participants