vandonr-amz opened a new issue, #30407:
URL: https://github.com/apache/airflow/issues/30407
### Description
using `breeze testing tests` recently I noticed that the way to specify
which tests to run is very confusing:
* `--test-type` supports specifying one type only (or `All`), allows
specifying which provider tests to run in details, and is ignored if
`--run-in-parallel` is provided (from what I saw)
* `--test-types` (note the `s` at the end) supports a list of types, does
not allow to select specific provider tests, and is ignored if
`--run-in-parallel` is NOT specified.
I _think_ that the two are mutually exclusive (i.e. there is no situation
where one is taken into account and the other isn’t ignored), so it’d make
sense to merge them.
Definition of Done:
- --test-type or --test-types can be used interchangeably, whether the tests
are running in parallel or not (it'd be a bit like how `kubectl` allows using
singular or plural for some actions, like `k get pod` == `k get pods`)
- When using the type `Providers`, specific provider tests can be selected
between square brackets using the current syntax (e.g.
`Providers[airbyte,http]`)
- several types can be specified, separated by a space (e.g. `"WWW CLI"`)
- the two bullet points above can be combined (e.g. `--test-type "Always
Providers[airbyte,http] WWW"`)
### Use case/motivation
having a different behavior for a very similar option depending on whether
we are running in parallel or not is confusing, and from a user perspective,
there is no benefit to having those as separate options.
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
