---
# System prepended metadata

title: Draft

---

### Questions to answer in this meeting:

1. What are the arguments against having **on TE per team/project**
2. What are the arguments against having **one TP for the entire 24.1 release testing**
3. **API vs. UI:** What are the reasons to separate them when it comes to TEs and TPs



------

My personal proposition for Test Executions:

Given the structure of our teams and the nature of the release, starting with one test execution per team might be the most streamlined approach, particularly if teams like ESG team’s work is closely related and collaborative by nature. This approach simplifies management and fosters a team-centric workflow, which can be particularly beneficial when integrating new modules into a complex SPA like The Shell.

However, if individual QA engineers on the team have distinct areas of responsibility or if the testing tasks vary significantly in scope or focus, dividing the work into separate test executions for each QA engineer could offer better granularity in tracking and accountability. This would be especially useful if certain aspects of the teams and products require specialized knowledge or focused testing beyond what a collective approach might accommodate.

Maintaining unified test executions for both API and UI within each cross-functional team ensures seamless feature integration and holistic testing. This approach prevents the creation of artificial divisions between back-end and front-end testing, fostering a collaborative environment. It simplifies management, reduces overhead, and enhances testing efficiency by leveraging the interconnected expertise of team members, crucial for delivering a cohesive user experience in our Shell SPA.

## Meeting notes
1. Technically it's not possible to assign TE to more than one QA
    - Technically it is possible
    - we can also multi select TCs and assign to others
2. TP per team
    - This gives a better visibility for the entire effort
    - We will have one big TP in Confluence to explain the effort, and then link the Xray repo that contains all TPs in there
3. TE
    - One TE per team
    - (If needed) two or more "sub test execution" per TE
4. TP
    - One TP per team and that's it!