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

Provide non-regression tests for regression #1872 #1875

Closed
apupier opened this issue Jan 5, 2021 · 2 comments
Closed

Provide non-regression tests for regression #1872 #1875

apupier opened this issue Jan 5, 2021 · 2 comments
Labels
area/test good first issue Does not require full understanding of the codebase status/never-stale
Milestone

Comments

@apupier
Copy link
Contributor

apupier commented Jan 5, 2021

a fix has been provided but there is no tests to prevent another regression on the same kind of issue #1873

@apupier
Copy link
Contributor Author

apupier commented Jan 7, 2021

Based on regression, interesting use case to test:

  • kamel (without arguments, this is used to check that a binary is available by VS Code, also personally using it to accessing help)
  • kamel help
  • kamel -h
  • kamel --help
  • kamel --unknownPropertyToCheckItDoesntExplode

Based on fix provided, interesting use case to test:

  • kamel local run --help

@nicolaferraro nicolaferraro added this to the 1.4.0 milestone Jan 8, 2021
@nicolaferraro nicolaferraro added the kind/bug Something isn't working label Jan 8, 2021
@nicolaferraro nicolaferraro added the good first issue Does not require full understanding of the codebase label Feb 4, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.4.0, 1.5.0 Apr 13, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.5.0, 1.6.0 Jul 5, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.6.0, 1.7.0 Sep 7, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.7.0, 1.8.0 Nov 15, 2021
@oscerd oscerd modified the milestones: 1.8.0, 1.9.0 Jan 19, 2022
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@oscerd oscerd modified the milestones: 1.9.0, 1.9.1 Apr 26, 2022
@oscerd oscerd modified the milestones: 1.9.1, 1.9.2 May 13, 2022
@oscerd oscerd modified the milestones: 1.9.2, 2.0.0 May 23, 2022
@squakez squakez closed this as completed Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test good first issue Does not require full understanding of the codebase status/never-stale
Projects
None yet
Development

No branches or pull requests

4 participants