citrusframework / citrusframework/yaks
Failures thrown in the YAKS config scripts are not reported
- Dominant language
- Java
- Stars
- 90
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Errors thrown during YAKS config scripts are not reported in `yaks report command` tests are automatically skipped and there is no mention about that in the `yaks report` command output. This means that we can't rely on the yask report and we have to count feature files or manually go through every test log to check script errors.
```
➜ camel-k-example-basic git:(master) ✗ yaks test test
Creating new test namespace yaks-c8aebb66-2c5a-410b-9891-ee066d460ef8
Unable to find existing YAKS operator - adding new operator instance to temporary namespace by default
Running integrations:
Error: unknown command "xx" for "kamel"
Failed to run integrations:
exit status 1
AutoRemove namespace yaks-c8aebb66-2c5a-410b-9891-ee066d460ef8
Test results: Total: 0, Passed: 0, Failed: 0, Errors: 1, Skipped: 0
Errors: 1
[
"Failed to run integrations: exit status 1"
]
Error: Failed to run integrations: exit status 1
➜ camel-k-example-basic git:(master) ✗ yaks report -o junit
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.