Proposal for New Label for Testing PRs

[mohamedawnallah]

Description

I wanted to discuss the possibility of introducing a new label for pull requests, such as kind/test. Currently, PRs that involve adding unit tests and end-to-end tests don't fit neatly into the existing kind/failing-test or kind/feature categories. This misalignment could lead to confusion and make it harder to track and manage these PRs effectively.

Introducing a kind/test label could help in categorizing and organizing these PRs more clearly, preventing any potential messiness and ensuring that they are labeled properly.

What are your thoughts on this proposal?

cc: @XiShanYongYe-Chang, @zhzhuang-zju

[zhzhuang-zju]

Introducing the label kind/test is a good idea. Should we keep the previous label kind/failing-test or remove it?

[mohamedawnallah]

IMHO, the kind/failing-test label might not be necessary, as its description states: Categorizes issue or PR as related to a consistently or frequently failing test.. That said, others may have different views, or some users might find this label useful.

[zhzhuang-zju]

I think we can keep it for now. kind/failing-test can serve as a supplement to kind/test, providing more detailed categorization.

[XiShanYongYe-Chang]

I agree that a dedicated label that focuses on tests is needed to represent test-related code, which includes subsequent UT and E2E code additions.

Is there a specific action plan?

[mohamedawnallah]

@XiShanYongYe-Chang I think adding labels is restricted to those with admin privileges?

[XiShanYongYe-Chang]

cc @RainbowMango

[RainbowMango]

It makes sense to me that have a label for testing efforts.
/assign

It might take some time as currently we have a lot of more priority stuff and I also need some time to test if the label could be handled by karmada-bot.

[liangyuanpeng]

this can resolved by:

• Enable auto labels for PRs #5183