Hi Maureen, Anas, Testing working group wants to add a link in thehttps://github.com/zephyrproject-rtos/zephyr/wiki to introduce device testing method and other related stuff. Is this OK for us to

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

Hi All, This weekly meeting agenda. 1. Some discussion on test result generation alignment which raised by Alexey(github.com/zephyrproject-rtos/zephyr/issues/28113). – 10 minutes

Sure. Regards, Hake From: testing-wg@... <testing-wg@...>On Behalf Of Masalski, Maksim via lists.zephyrproject.org Sent: 2020年9月30日 15:40 To: Hake Huang <hake.huang@...>;

Let’s keep the meeting then. Regards, Hake From: Perkowski, Maciej <Maciej.Perkowski@...> Sent: 2020年9月30日 15:34 To: Hake Huang <hake.huang@...>; maksim.masalski@...;

Great! Hake, please add in the agenda the main topic points. 1. Find out the Main Editor – person who will responsible for all editing in the document. I vote for Maciej. I would to suggest

I will attend if the meeting takes place. Maciej Perkowski | Software Test Developer M +48 728 395 111 | Kraków, Poland nordicsemi.com |devzone.nordicsemi.com From: Hake Huang

I can manage to attend, if the other audiances can attend. The main topic next week is about 1. some discussion on test result generation alignment which raised by

I agree. Regards, Hake From: Masalski, Maksim <maksim.masalski@...> Sent: 2020年9月30日 1:18 To: Masalski, Maksim <maksim.masalski@...>; Hake Huang <hake.huang@...>; maciej.perkowski@...;

BTW, to avoid our misunderstanding in the text formatting I suggest to write “golden sample” section, which will be approved by all of us, then we can use that section like a reference for the

Hi, I can’t attend next meeting on Monday 5th October due to National holiday in China. Hake, what about you? Should we cancel meeting next Monday? Maksim From: Hake Huang

Thanks. I believe it’s going in a good direction😊 Maciej Perkowski | Software Test Developer M +48 728 395 111 | Kraków, Poland nordicsemi.com |devzone.nordicsemi.com From: Hake Huang

Thanks, and I have updated the document for my parts, please check. Regards, hake From: Perkowski, Maciej <Maciej.Perkowski@...> Sent: 2020年9月29日 18:53 To: Hake Huang <hake.huang@...>;

But this article states exactly what I am proposing😊 (or am I missing something?) I never said that relative position should be used (it shouldn’t, as the position may change). Instead we refer

I see. But I am only aware about rules that cite table with its title, but not from relative position(https://blog.apastyle.org/apastyle/tables-and-figures/ ). And it is the first time that I meet

This refers to the standard that whenever one puts a table or a figure in a document this table/figure has to be mentioned in the main text. In other words it is considered an “error” if there is

Hi Hake, I think it is better to keep the numbering, even if the numbers will change later on. It allows for a correct referring of an entry in the main text to the labeled

Hi Maksim, Sorry no discuss with you, the reason I do this is because: We’d better keep the TAB x.x as a pseude token, because we do not know whether we need to insert a new table, just to

Hake, what is the Table ID? I removed it, and assigned real number to it. Please, if you want to change design (not content) ask me first. Yesterday I updated Maciej’s section according to the

Hi Maciej, I update the information explaining on every section, please check. Also I unified the table title to `Heading 3` format and add [Table ID] as template