One thing to bear in mind, from what we have observed running CI on TCF with Zephyr is that there are issues (failures, errors) that will creep randomly and then not appear again for a

Hi All, This mail is to propose a process for efficient test working group to control the issues that are found in test runs. 1. We need create a periodic summary report e.g. We can choose

Hello As promised on the call on 11/19, here are some examples for complex testcases with TCF. As an example, this is testing the USB CDC sample; references for this in

Hi Svein, Thanks for the reply. Basically I agree with you. But there are two major item, I want to raise here: 1. Will testing working group own all the samples and tests? If not how could

Hi Hake, Comments inline [Svein]. Br Svein Aga

Minutes - Nov 5th Monday, 5 November 2018 Attendees: Anas, Hake, Inaky, Svein, Andrei Opens • Hake: Test plan discussion, where should it happen? Continue offline.

Hi Svein, Thanks a lot. Some feedback in lines leading with [Hake] Regards, Hake

Hello All Thanks for attending the presentation last Monday; here are the links: TCF: http://intel.github.com/tcf Slide deck:

Hi, I’ve proposed some changes/additions below inblue + some comments and questions. A more general comment is that the Zephyr project can define a top level master test plan that is

Hi All, I initialize a test plan based on IEEE 829 template.https://github.com/zephyrproject-rtos/qm/pull/2. I propose we can start at defining below things: 1. Testing Items a)

Members of the Zephyr Testing Working Group, The kick-off call for the group has been moved to next week. You should have just received a Doodle to capture your availability, but if not, the link is