Re: [EXT] [testing-wg] Updated Event: Zephyr: Testing WG weekly call #cal-invite
This weekly meeting agenda.
1. Progress on test result repo. (20 Minutes)
2. Final the test type definition.
a) PASS - test was successful
b) FAIL - test assertion(s) failed
c) ERROR – is usually reported when test setup fails before the test even attempts to test the test assertions or some other error occurred during the execution
d) NOT_EXECUTED (reason in msg) - Test was skipped due to some conditions at the specification stage (e.g. was on a filtered list). This would indicate that the behavior (not executing) was expected
e) IGNORED – Test was skipped due to being marked manually by a user. E.g. faulty tests could get such flag before they are repaired and be skipped during the execution
f) MISSING – test was in the specification marked as to be executed, although it was not found in the report. It will work only if we decide to take an approach where after tests execution the program runs through the list of tests in the specification (extracted in advance) and looks for the results in the results report.
3. Round table discussion. (20 minutes)
From: testing-wg@... <testing-wg@...>
On Behalf Of testing-wg@... Calendar via lists.zephyrproject.org
Caution: EXT Email
Zephyr: Testing WG weekly call
An RSVP is requested. Click here to RSVP