Skip to content
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

Add a --skipvectors argument to the run command #141

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

cazou
Copy link
Contributor

@cazou cazou commented Aug 10, 2023

For automated tests, it is useful to be able to skip some vectors that are failing on a specific hardware or with a specific decoder.

This adds an argument to skip those vectors and mark then as Not Run.

Note that the TestCase is still created but flagged to be skipped so that it is included in the report as skipped and not just completely ignored.

@mdimopoulos
Copy link
Contributor

@cazou thanks for your contribution! CI reported a code format failure, could you check and modify accordingly please?

@cazou
Copy link
Contributor Author

cazou commented Aug 11, 2023

@cazou thanks for your contribution! CI reported a code format failure, could you check and modify accordingly please?

@mdimopoulos Indeed, this is fixed now :)

@rgonzalezfluendo
Copy link
Contributor

CI reported a new failure. You can execute make check in local to be sure CI will pass.

@ylatuya
Copy link
Contributor

ylatuya commented Oct 3, 2023

The README should be updated as well.

@cazou
Copy link
Contributor Author

cazou commented Oct 3, 2023

The README should be updated as well.

Right, done !

For automated tests, it is useful to be able to skip some vectors that
are failing on a specific hardware or with a specific decoder.

This adds an argument to skip those vectors and mark then as Not Run.
The generated reports will mark them as Skipped.

Signed-off-by: Detlev Casanova <[email protected]>
@mdimopoulos mdimopoulos merged commit 303a6ed into fluendo:master Oct 3, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants