[FLINK-34279] Cross team testing

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Assignee: lincoln lee
• Reporter: lincoln lee
• Created: 30/Jan/24 09:48
• Updated: 18/Mar/24 07:27
• Resolved: 18/Mar/24 07:27

Description

For user facing features that go into the release we'd like to ensure they can actually be used by Flink users. To achieve this the release managers ensure that an issue for cross team testing is created in the Apache Flink Jira. This can and should be picked up by other community members to verify the functionality and usability of the feature.
The issue should contain some entry points which enables other community members to test it. It should not contain documentation on how to use the feature as this should be part of the actual documentation. The cross team tests are performed after the feature freeze. Documentation should be in place before that. Those tests are manual tests, so do not confuse them with automated tests.
To sum that up:

• User facing features should be tested by other contributors
• The scope is usability and sanity of the feature
• The feature needs to be already documented
• The contributor creates an issue containing some pointers on how to get started (e.g. link to the documentation, suggested targets of verification)
• Other community members pick those issues up and provide feedback
• Cross team testing happens right after the feature freeze

 

---

Expectations

• Jira issues for each expected release task according to the release plan is created and labeled as release-testing.
• All the created release-testing-related Jira issues are resolved and the corresponding blocker issues are fixed.

Issue Links

• is a child of: FLINK-34285 [Umbrella] Test Flink Release 1.19