Description:
The Microcks Test GitHub action defines an input called filteredOperations which allows users to specify a JSON array of operations to consider during tests. However, this input is correctly defined in the inputs section but is incorrectly referenced as ${{ inputs.filterOperations }} (missing the trailing 'd') in the args section of the action.yml file.
Because GitHub Actions treats undefined inputs as empty strings, the --filteredOperations flag passed to the microcks-cli always receives an empty value, effectively ignoring the user's filter.
Steps to Reproduce:
- Use the
microcks/test-github-action in a workflow.
- Provide a value for filteredOperations (e.g., ['operation1', 'operation2']).
- Observe that the Microcks test runs for all operations instead of the filtered ones.
- Expected Behavior: The value provided to filteredOperations should be passed correctly to the --filteredOperations flag of the CLI.
Description:
The Microcks Test GitHub action defines an input called
filteredOperationswhich allows users to specify a JSON array of operations to consider during tests. However, this input is correctly defined in the inputs section but is incorrectly referenced as ${{ inputs.filterOperations }} (missing the trailing 'd') in the args section of the action.yml file.Because GitHub Actions treats undefined inputs as empty strings, the --filteredOperations flag passed to the microcks-cli always receives an empty value, effectively ignoring the user's filter.
Steps to Reproduce:
microcks/test-github-actionin a workflow.