Teaching your Test Framework to Speak LAVA
summary
A simple technique makes existing test runners emit LAVA signals so LAVA sees each test case instead of one pass/fail blob: add a small reporter (for example conf_test.py for pytest), a -L flag or executor change for BATS, and a capital L option in ptest; the result turns a single-suite pass/fail into per-test entries (the demo shows ~20 pages of individual results versus one failing blob), supports numeric measurements/units partially, and requires only minor runner changes with no post-processing and immediate dashboard benefits.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:48Testing in LAVA
- 2:00Lifecycle of a test case
- 3:21What can we do
- 4:15Extras
- 5:12PI Test
- 7:46Before and After
- 8:24Output
- 8:55Comp Test Pie
- 9:38Results Tab
- 10:03COFF Test Pie
- 10:52More Test Runners
- 12:17LAVA Stream
- 12:51Convert Results
- 13:04Test Case Names
- 13:31Test Case Teardown
- 15:31Test Case Results
- 16:01PTest
- 18:13Make Array
- 19:45Test Case Runner
- 21:01Test Results
- 21:17Test Runner
- 21:42Summary
- 25:01Questions
- 28:01Test Stop High
- 28:52Measurement
- 29:44Test Cases
related talks
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
41mLAVA Users Forum
44mAutomation beyond Testing and Embedded System Validation
45mUpdate on LAVA Testing for bare metal systems
22mLAVA community enabled testing
26mLAVA + OpenQA = Automated, Continuous Full System Testing
34mFrom Zero to First Test in Your Own LAVA Laboratory in less than 45 minutes)
41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...