novonordisk-opensource/QMS generate verification report
Generates a verification report based on pipeline metadata and test results as inputs.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| testresults_artifact | Artifact name of files uploaded of previously generated test results during runs of (IV, PV) or (pIV, pPV), e.g. [testresults-validation, testresults-production]. | yes | "" |
| repository_artifact | Artifact name of the repository being tested: it will almost always be the triggering branch and repository of the workflow calling this action. | yes | "" |
| ready_for | Indicates whether the verification report is generated for the validation or production environment with respective possible values: [production, use]. | yes | "" |
| feature_files_path | Path to the directory containing the feature files (.feature). Subfolders within is supported. Relative to the root of the provided repository. | yes | "" |
| system_design_specification_path | Path to the directory containing the system design specifications files (.md). Subfolders within is supported. Relative to the root of the provided repository. | yes | "" |
| system_configuration_specification_path | Path to the directory containing the system configuration specifications files (.md). Subfolders within is supported. Relative to the root of the provided repository. | yes | "" |
| it_solution_name | Name of the IT solution. This will be in the verification report. | yes | "" |
| project_name | Name of the project. This will be in the verification report. | yes | "" |
| environment_name | Name of the environment. This will be in the verification report. | yes | "" |
| github_token | GitHub token to use for API access. | yes | "" |
Outputs
no outputs