Hi All, This weekly meeting agenda. 1. Round table for discussion. 2. Twister v2.0 intro duction. 3. Follow up on CI test case enhancement.

Hi, Test coverage is not automatically enforced, it is a guideline and can be enforced through reviews. We had CI running for a while checking the coverage and reporting on each PR but that was

Yes, but how do I write a new unit test, for code that has things like #ifdef CONFIG_CPU_CORTEX_M in it? Do those need to be changed instead to something like #if defined(CONFIG_CPU_CORTEX_M) ||

Looking at the daily jon, we do have unittest coverage… https://github.com/zephyrproject-rtos/zephyr/actions/runs/1791868898 Anas From: testing-wg@... <testing-wg@...> on behalf of

I mean to use the unit test type, since as far as I can tell, qemu arm doesn't support code coverage.-- Jeremy Bettis | ChromeOS FAFT lead | jbettis@... | 303-257-2486

We can also run on ARM qemu, but it was disabled because of few failures we had due to stack size, etc. Anas From: Jeremy Bettis <jbettis@...> Date: Thursday, February 3, 2022 at 3:37 PM To:

You mean test that runs in an emulator or using the unit test type in ztest, which builds as a host binary? Anas From: Jeremy Bettis <jbettis@...> Date: Thursday, February 3, 2022 at 3:37

I've noticed there is only coverage for posix and qemu_x86 on https://app.codecov.io/gh/zephyrproject-rtos/zephyr. Do you have any guides for making a unittest for non posix code? For example, if I

Dear all, Thanks for bringing and clarifying that question. And excuse me, Hake and all, I cannot attend this meeting tonight due to family activities of CNY. Thanks! Enjia

Hi, Coverage reports and having test coverage is a test activity, has nothing to do with Safety. Maybe it was not discussed here in this group in the past, but it’s something that belongs here

Coverage analysis is not conducted in the testing working group instead there is another team who is testing the kernel API coverage. IIRC it is safety team, correct me if I am wrong @Mai.Enjia@...

Cancelled: Zephyr: Testing WG weekly call This event has been cancelled. When: Thursday, February 3, 2022 7:00am to 8:00am (UTC-08:00) America/Los Angeles Where: Microsoft Teams

Dear Testers, I was recently asked by my colleague about quality standards related to Zephyr’s contributions, in particular to testing. A relevant section of our docs states: “When major new

Reminder: Zephyr: Testing WG weekly call When: 01/27/2022 7:00am to 8:00am (UTC-08:00) America/Los Angeles Where: Microsoft Teams Meeting Organizer: testing-wg@... An RSVP is requested.

Sorry for everyone testing group members, I cannot join this meeting tonight due to other confliction. Have a good night! BRs, Enjia

Hi All, This is today’s weekly meeting agenda: 1. V3.0.0-RC1 testing status. 2. Follow up on twister re-architecture 3. Round table discussion. Regards, Hake -----Original

Meeting has been updated: https://lists.zephyrproject.org/g/testing-wg/calendar Thanks -- Brett Preston Sr. Program Manager The Linux Foundation +1 (971) 303-9030 bpreston@...

Zephyr: Testing WG weekly call When: Thursday, January 27, 2022 7:00am to 8:00am (UTC-08:00) America/Los Angeles Repeats: Weekly on Thursday Where: Microsoft Teams Meeting Organizer:

Hi Brett, We choose the new time is Thursday 7:AM – 8:AM (UTC-09:00) Pacific Time (US & Canada) from next week. Please help to make the move/update. Thanks again. Regards, Hake

Hi Anas, You can’t access below link? Or you did not see Brett’s mail? Doodle: https://doodle.com/meeting/participate/id/9b69WYQa Regards, Hake