Re: Test coverage and its measurements
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 IMO.
From: testing-wg@... <testing-wg@...> on behalf of Hake Huang <hake.huang@...>
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@...
From: testing-wg@... <testing-wg@...> On Behalf Of Perkowski, Maciej via lists.zephyrproject.org
Sent: 2022年2月3日 17:14
Cc: Wang, Guojun <guojun.wang@...>
Subject: [EXT] [testing-wg] Test coverage and its measurements
Caution: EXT Email
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 functionality is added, tests for the new functionality MUST be added to the automated test suite. All new APIs MUST be documented and tested and tests MUST cover at least 80% of the added functionality using the code coverage tool and reporting provided by the project.”