According to what I learn from the sanitycheck scripts, the steps are: 1. Check the testcase.yaml/samples.yaml a) Which lists the dependency and platforms. b) Some test

Dear All, I would like to discuss the nomenclature used in sanitycheck reporting during our next meeting. It will relate to the issue:

Hello, yesterday I sent a new link to the Release Summary Report. Please don’t use it and ignore it, because my corporate Gdrive account will be still in use. Use file link as you used before.

Hello, I migrated Release Summary report Document to my private GDrive, because our company team moved from GDrive to OneDrive. Please refer to that new file

Reminder: Zephyr: Testing WG weekly call When: Monday, 16 November 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi All, This is this weekly meeting agenda. 1. Call for start weekly testing (All, 10 minuts) This weekly tag will be created on Monday night US time. 2. Test manager sytem survey

Masalski, Maksim has shared a OneDrive for Business file with you. To view it, click the link below. Allure-Working-Experience.docx Hello, I finished my notes about Allure. During next meeting I will

Hi Maciej It is 2:00pm to 3:00pm, (GMT+00:00) UTC Regards, Hake

Hi Hake, Could you please state the time in UTC? Is it as in call for RSVP: 14-15 UTC? Maciej Perkowski | Software Test Developer M +48 728 395 111 | Kraków, Poland nordicsemi.com |

Hi All, This is a notice to that weekly call will be 1 hour later for regions that do not use day time saving shift(e.g. China), if you have problem with this time, please propose your favourite

Reminder: Zephyr: Testing WG weekly call When: Monday, 9 November 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi All, This is this weekly meeting agenda. 1. versions.json with weekly usage case intro. (Anas, 10

Reminder: Zephyr: Testing WG weekly call When: Monday, 2 November 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi, Same here, won’t be able to attend today. Sorry. Anas From: <testing-wg@...> on behalf of "Perkowski, Maciej" <maciej.perkowski@...> Date: Monday, 2 November 2020 at 02:57 To:

Hi, I will have to skip today’s meeting as well. Regards, Maciej Maciej Perkowski | Software Test Developer M +48 728 395 111 | Kraków, Poland nordicsemi.com | devzone.nordicsemi.com

Hi All, This is this weekly meeting agenda. 1. Updates on versions.json update PR. (Anas, 10

Thanks Anas. My reason to create a new weekly json file. I find it is difficult to create a compatible json file. and I want to keep the versions.json consistent so that the existing parser

Hi All, Anash update this feature inhttps://github.com/zephyrproject-rtos/zephyr/pull/29583/files/2b962288f2058828282d100c18540928adc539bd..418ab8529567743a30a77ee6e5efdb4f66f7be54 Please

I did not suggest using another file, we should use exactly the same file but expand the data we store there: Add date Add a flag for weekly … I do not think creating a new file is needed..

Thanks Hake for the feedback, it seems I underestimated the impact of test machine performance.