Category Archives: Summary

Krupa Nanda 6:28 am on April 27, 2025
Tags: ,   

Test Chat Summary: April 23, 2024

On Thursday, April 23, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @pavanpatil1. The agenda can be found here.

Attendance

@sirlouen @krupajnanda @pavanpatil1 @zeelthakkar @oglekler @pratiklondhe (async) @muddassirnasim(async) @nikunj8866 (async) @narenin (async)

2. Volunteer

This week’s Note-taker and facilitator:

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • No updates

6. Questions/Blockers

  • No Questions/Blockers reported in this meeting

7. Call for Testers/Visibility

  • WordPress 6.8 is already out. If you come across any issues, please report them on Core Trac or GitHub.
  • The GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 20.7 is now available – https://wordpress.org/plugins/gutenberg/

8. Discussion

During the meeting, @sirlouen raised the issue of the Workflow Keywords, specifically around the keyword needs-testing-info, which has been causing confusion due to its similarity with needs-testing.
Two solutions were proposed, with the renaming of the keyword considered the most viable. Here, the objective is to enhance usability and maintain clarity in the keyword naming scheme. @joemcgill suggested the keyword needs-test-info, as it aligns better with the current format of existing workflow keywords.

A quick poll was conducted during the meeting, and the majority voted for the following naming convention:

  • needs-test-info
  • has-test-info

These changes will align testing-related keywords with the overall naming scheme used in the project.

@krupajnanda asked whether the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team would support implementing these changes once the updated keywords and their intended usage are shared. @joemcgill confirmed his willingness to assist with this.

@sirlouen mentioned that once @muddassirnasim completes the meeting notes, he will forward the information to @dd32 for inclusion in the official TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. documentation.

9. Open Floor

No items discussed

10. Next Meeting 🗓

April 30, 2025, at 21:30 GMT+5:30: <test-triage> #core-test! 

May 07, 2025, at 21:30 GMT+5:30: <test-chat>  #core-test!

#core-test, #meeting-notes

Muddassir Rahman Nasim 2:30 pm on April 14, 2025
Tags:   

Test Chat Summary: 10th April 2025

On Thursday, April 10, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@muddassirnasim @sirlouen @krupajnanda @oglekler @ravigadhiyawp @pbearne @sumitbagthariya16 @mukesh27 @indirabiswas27 @pavanpatil1 @mkrndmane @pratiklondhe @narenin @mebo (async) @nikunj8866 (async) @vaibhavsweb (async)

2. Volunteer 

For the next bi-weekly chat –

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • We are in a 6.8 release cycle and only a week from our final release. WordPress 6.8 is going to be released on April 15, 2025
  • Check what to expect in WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@Muddassir Nasim reported successful testing using the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. Tester PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, expressed interest in learning WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/, and showed a willingness to explore interactive testing through CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress..

  • @Krupa Nanda suggested testing via WP-CLI and directed Muddassir to @Makarand Mane for further guidance.
  • @Makarand Mane reaffirmed his availability to support WP-CLI testing and offered assistance proactively.
  • @Manuel Camargo sought clarification on the scope of Nasim’s interest, distinguishing between WP-CLI specific testing and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing.

@Olga Gleckler encouraged to test the site with real and data, if you have this opportunity. So, if you can test on a staging site close to what you have on production (not on production, of course). Becasue some things can only happen in certain circumstances and conditions.

7. Call for Testers/Visibility

8. Open Floor

@krupajnanda suggested @SirLouen to prepare a draft for the suggestion and feedbacks he added here and mentioned once thr post will be ready we can post it in the community for feedback. 

9. Next Meeting 🗓

The next meeting will be on Wednesday, April 23, 2025, at 12:00 AM GMT+8 , held on #core-test!

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

#meeting-notes 

#core-test

vgnavada 5:45 pm on March 17, 2025
Tags: , ,   

Test Chat Summary: March 12, 2025

On Wednesday 12 March 2025 at 21:30 GMT+5:30, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@Krupajnanda, @oglekler, @sirlouen, @vgnavada, @kausaralm, @shiponkarmakar, @pavanpatil1, @narenin, @nikunj8866, @pmbaldha, @mukesh27

2. Looking for Volunteers

  • @vgnavada volunteered to take notes on this meeting.

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • Beta 2 release of WordPress 6.8 is now available for testing.
  • The BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 release of WordPress 6.8 is scheduled for next Tuesday, March 18th. Please check the detailed overview of the release schedule for WordPress 6.8.  Don’t miss the Release Party in #core to test and provide feedback! :dart:
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 20.4 was released on Wednesday, March 5th. Check out the milestone for the issues that were part of the 0.4 release.

4. Test Team Updates

5. Focal Group Updates

  • We are in the 6.8 release cycle and only 2 weeks from our first RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release.
  • Check out what to expect in the WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@sirlouen questioned about the testing suggestions doc: https://docs.google.com/document/d/1Q7Kzs-78XvrAjnjG_MhBJR6bSBk80rvzwnV90iYTjhg/edit?tab=t.0

7. Call for testers/visibility

8. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Addressing Ethical Practices in Testing:
    • @vgnavada: Highlighted the issue of copying someone else’s test case, including the exact screenshot and text copy, and presenting it as their own, pointing out the unethical nature of this practice.
    • @sirlouen: Stated that the other user likely reused the same steps to confirm the patch without taking the time to do the work again from scratch. He described this as poor testing practice, as it would have been better to try different approaches to expand the testing cases.
    • @oglekler: Acknowledged that such issues hadn’t been caught before but noted that it should be looked into now. While copying someone else’s work is demotivating, She reassured that it wouldn’t benefit the person doing it and advised not to worry too much about it.
    • @krupajnanda: Expressed understanding of the concern and emphasized that copying someone else’s work, especially when it involves significant effort, is not the right way to contribute. She suggested that more eyes should be on each ticket to offer different perspectives and solutions.

  2. Bridging the Gap: Improving Collaboration Between QA and Development Teams
    • Challenges Identified: @sirlouen mentioned the often it observed that patches get approved with minimal verification, which can lead to unexpected issues down the line. When tickets don’t clearly outline use cases, it can slow down testing and create confusion. We need a clear mechanism for this situation to be resolved.
    • Proposed Solutions: Introduce a needs-use-cases tag to ensure clear reporting and smoother testing to encourage detailed testing reports and context from committers.
    • Next Steps: @mukesh27 supported the ideas and suggested a blog post to drive awareness and change.

9. Next Meeting 

10. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community is encouraged to continue contributing and collaborating outside of scheduled meetings.

  • @krupajnanda thanked @sirlouen for their feedback and assured them that the team would work on resolving the gaps identified. She acknowledged the active participation of the team during the meeting and emphasized that team members can raise questions or start discussions anytime in the Test Team channel.

Takeaways

The main takeaway is that better teamwork, clear communication, and accountability between QA and development teams are key to success. When both sides work together with honesty, transparency, and shared responsibility, things run more smoothly and lead to better results.

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #summaries

Patrick Lumumba 4:48 pm on February 14, 2025
Tags: , ,   

Test Chat Summary: 12th February 2025

On Wednesday, February 12, 2025, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @nazmul111, @kausaralm, @huzaifaalmesbah, @shiponkarmakar, @sumitbagthariya16, @oglekler, @pavanpatil1, @lumiblog and @narenin (async).

2. Looking for Volunteer

  • February 26: Test Chat Meeting Facilitator: Volunteer Needed 
  • February 26: Test Chat Meeting Recap Notes: Volunteer Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • We are in the WordPress 6.8 release cycle and only a few weeks away from the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release.
  • Check what to expect in WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Call for Testers/Visibility

8. Open Floor

Will you be joining us on the Contributors Day at WCAsia 2025? Remote/In-person? Tell us in this thread.

9. Next Meeting 🗓

The next meeting will be on Wednesday, February 12, 2025, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

Patrick Lumumba 2:03 pm on February 1, 2025
Tags: , ,   

Test Chat Summary: 29th January 2025

On Wednesday, January 29, 2025, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @huzaifaalmesbah, @oglekler, @kausaralm, @sumitbagthariya16, @narenin, @dhruvang21, @pavanpatil1, and @lumiblog

2. Looking for Volunteer

  • February 12: Test Chat Meeting Facilitator – Volunteer Needed 
  • February 12: Test Chat Meeting Recap Notes – Volunteer Needed
  • Remote Table leads for WCAsia. Please check this guide for more details on what to expect as a Test Table Lead.
  • A volunteer to work on Call for testing WordPress 6.8 release. For more details, check out the guide: How to Facilitate a Call for Testing

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

There was no issue to discuss. 

8. Next Meeting 🗓

The next meeting will be on Wednesday, February 12, 2025, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

Krupa Nanda 2:00 pm on January 21, 2025
Tags: ,   

Test Chat Summary: January 15, 2024

On January 15, 2025, at 21:30 GMT+5:30,  <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@krupajnanda, @mobarak, @oglekler, @krupal, @zeelthakkar, @jagirbahesh, @ankit-k-gupta, @hage, @patrickl, @nazmul111, @narenin

2. Looking for Volunteers

@zeelthakkar volunteered to take notes for this Meeting.

3. Announcements 

  • WordPress 6.8: Release Team, Schedule, and Key Areas of Focus
  • WordPress 6.8 Release Cycle: Look at the WordPress 6.8 Development Cycle for details.
  • WordPress 6.7.2: Currently, there is no scheduled release date for WordPress 6.7.2, but you can explore the next minor release milestone for updates.
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 20.0 marks the milestone 200th release of the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. 
  • WordCamp Asia 2025 Scholarship Recipients

4. Test Team Updates

5. Focal Group Updates

There were no updates shared during the meeting.

6. Questions/Blockers

The members reported no blockers or questions.

7. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Improving Test Results Trustworthiness:
    • We explored some ideas for improving the test reports.
    • @krupajnanda shared this post which is dedicated to celebrate the International Women’s Day.
  2. Next Steps:
    • @SirLouen mentioned that he will begin reviewing the points discussed in the last meeting to provide additional details for the document on key improvement for test reports.

The open floor concluded with a call for participants to contribute their ideas, ensuring diverse perspectives are incorporated.

8.Next Meeting 🗓

9. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community was encouraged to continue contributing and collaborating outside of scheduled meetings

PS: This chat summary is originally written by Zeel Thakkar but due to some access issue she could not publish it.

#core-test, #meeting-notes

Mobarak Ali 10:02 am on December 22, 2024
Tags: , ,   

Test Chat Summary: December 18, 2024

On Wednesday, December 18, 2024, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@krupajnanda, @n8finch, @mayanktripathi32, @lumiblog, @mobarak, @hage, @oglekler, @shanemuir, @narenin, @sirlouen, @patrickl, and Narendra Sishodiya

2. Looking for Volunteers

3. Announcements 📣

  • WordCamp Asia 2025 Contributor Day: The Test Team is seeking leads for the Contributor Day table at WordCamp Asia, which will take place on February 20, 2025. Please express interest in the thread if you plan to attend WCAsia in person or can assist remotely.
  • WordPress 6.7.2:  No release date is currently planned for WordPress 6.7.2. Please review the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. milestone for 6.7.2 and check the associated tickets for ways to contribute.
  • WordPress 6.8 Release Cycle:  The team is currently working on the WordPress 6.8 release cycle.
  • Proposals for Major Releases in 2025:  A proposal for 2025 has been drafted. Review the post for more details.
  • Write Books With the Block Editor:  We are currently discussing how to use the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor to write books.
  • State of the Word 2024: The State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2024 session focuses on Legacy, Innovation, and Community.

4. Test Team Updates

5. Focal Group Updates

No updates were reported during the Meeting.

6. Questions/Blockers

The members reported no blockers or questions.

7. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Improving Test Results Trustworthiness:
    • @OGlekler raised the need to enhance trust in test results, suggesting that test case coverage be included as proof in reports.
    • @krupajnanda agreed and emphasized the importance of detailing scenarios covered in testing fixes/PRs to reduce regression risks and improve clarity on the scope of fixes.
    • @OGlekler shared an example from a workplace discussion, noting the value of systematic reporting and documenting test cases.
  2. Forum for Brainstorming Ideas:
    • @SirLouen proposed having a persistent space, like a forum or blog post, to brainstorm and collect broader feedback on such topics.
    • The group agreed that creating a collaborative Google Doc to collect ideas and present the issue without initial bias could be effective.
  3. Next Steps:
    • @krupajnanda committed to sharing a collaborative Google Doc link for feedback collection.
    • The group agreed to publish a finalized document on the team blog and invite input from other teams and contributors.

Resources:

The open floor concluded with a call for participants to contribute their ideas, ensuring diverse perspectives are incorporated.

8. Next Meeting 🗓

9. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community was encouraged to continue contributing and collaborating outside of scheduled meetings.

Highlights:

  • @krupajnanda thanked everyone for their participation and emphasized the community spirit of Test Team contributors.
  • @OGlekler extended gratitude to the team, wishing everyone a great end to the year and an inspiring start to 2025.

Takeaways

  • Keep engaging in discussions within the channel.
  • Use this time of year to reflect, recharge, and prepare for exciting contributions in the new year.
  • Remember to bring family and friends into the WordPress journey!

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #meeting-notes, #summaries

Patrick Lumumba 10:33 am on December 7, 2024
Tags: , ,   

Test Chat Summary: 4th December 2024

On Wednesday, December 4, 2024, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @noruzzaman, @sainathpoojary, @ankitkumarshah, @sarthaknagoshe2002, @oglekler, @mayanktripathi32, @shanemuir, @sirlouen, @narenin (async), @lumiblog (async), and @hage

2. Looking for Volunteer

  • December 11: Test Triage Facilitator: Volunteers Needed
  • December 18: Test Chat Meeting Facilitator: Volunteers Needed 
  • December 18: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

@sirlouen mentioned that he had been thinking about testing reports after following several conversations in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. He expressed curiosity about the extent to which developers appreciate such reports, noting that he had observed developers re-testing and commenting on information that was already clear in the reports.

@oglekler suggested that sometimes the reports might lack sufficient information and proposed that improvements could be made by ensuring all possible test cases are accounted for and explicitly checked.

@sirlouen wondered if they should inquire what information developers find useful or if the reports might be too convoluted, leading developers to disregard them.

@krupajnanda added that it would be important to observe if this pattern was specific to certain tickets owned by the same developer or spread across different developers. If so, improvements to the parameters shared in the reports would be necessary.

@sirlouen concluded by stating that he would monitor and log these occurrences over time to gather precise information, acknowledging that this behaviour might only apply to a few developers and that he wasn’t following all categories of reports.

8. Next Meeting 🗓

The next meeting will be on Wednesday, December 18, 2024, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

Patrick Lumumba 5:54 am on November 21, 2024
Tags: , ,   

Test Chat Summary: 19th November 2024

On Tuesday, November 19, 2024, at 02:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@jagirbahesh, @krupajnanda, @lumiblog, @zeelthakkar, @dhruvang21, @mayanktripathi32, @sumitbagthariya16, @parthvataliya, @sukhendu2002, @yogeshbhutkar, @sainathpoojary, @abcd95, @ankitkumarshah, @hage, @narenin, @sarthaknagoshe2002, and @noruzzaman

2. Looking for Volunteer

  • November 26: Test Triage Facilitator: Volunteers Needed
  • December 3: Test Chat Meeting Facilitator: Volunteers Needed 
  • December 3: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

  • WordPress 6.7, Rollins, is out!
  • Keep an eye on the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for the 6.7.X series
  • Please join the WordPress Community Team as a Supporter of Cohort 2024-25
  • Successfully completed the six weeks of the mentorship program, and many folks have graduated! Congratulations to all the mentees!
  • The Playground team added browser support for cURL, making it easier for WordPress pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developers to showcase their plugins directly in Playground and use them in runPHP blueprint steps.
  • Experimental inline comments: In GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 19.6, inline commenting is now available as an experiment. You can follow the ongoing development of this feature in the tracking issue or review the previous work in the original pull request. Testing and feedback are needed.
  • Introducing the WordPress.org Experiments plugin: A new plugin called WordPress.org Experiments allows contributors to test experimental features before they’re integrated into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

There was nothing from the members. 

8. Next Meeting 🗓

The next meeting will be on Tuesday, December 3, 2024, at 11.00 UTC, held on #core-test!

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#meeting-notes, #summary

Patrick Lumumba 10:21 am on November 6, 2024
Tags: , ,   

Test Chat Summary: 5th November 2024

On Tuesday, November 5, 2024 at 02:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @sumitbagthariya16, @narenin, @pkbhatt, @sppramodh, @dhruvang21, @jagirbahesh, @zeelthakkar, @parthvataliya, @mohitdadhich10, @hage, and @lumiblog

2. Looking for Volunteer

  • November 12: Test Triage Facilitator : Volunteers Needed
  • November 19: Test Chat Meeting Facilitator: Volunteers Needed 
  • November 19: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

No updates were reported by the members.

6. Questions/Blockers

@pkbhatt, attending a Test Chat Meeting for the first time, requested guidance on finding tickets to test. @krupajnanda welcomed him and shared a list of recent tickets, suggesting he could also search for additional tickets to work on.

7. Call for Testers/Visibility

8. Open Floor

There was nothing from the members. 

9. Next Meeting 🗓

The next meeting will be on Tuesday, November 19, 2024 at 11.00 UTC, held on #core-test!

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

#meeting-notes, #summary