summaryrefslogtreecommitdiff
path: root/decoder/test/arm_etmv3/stm32f105/etmv3.output
diff options
context:
space:
mode:
authorGerhard Sittig <gerhard.sittig@gmx.net>2021-12-25 20:02:00 +0100
committerGerhard Sittig <gerhard.sittig@gmx.net>2021-12-26 13:37:03 +0100
commit97b2e74f29fa79c15ece5844fd99aa2dd0f6d0b0 (patch)
tree60df01b16f7f866ad2e8d27959145554b76d2468 /decoder/test/arm_etmv3/stm32f105/etmv3.output
parent873dd231a86f022c00d2f4562c18694024b1051c (diff)
downloadsigrok-test-97b2e74f29fa79c15ece5844fd99aa2dd0f6d0b0.tar.gz
sigrok-test-97b2e74f29fa79c15ece5844fd99aa2dd0f6d0b0.zip
ir_irmp: introduce IRMP test cases, cover NEC/RC5/RC6/SIRC and others
The upstream IRMP project's decoder core is only slowly moving, we can consider the IRMP decoder integration to be stable and don't expect the output to change violently any longer. The issue of requiring a single core instance remains and affects the GUI, but not the single threaded test suite. This set of test cases re-uses the NEC, RC5, RC6, and SIRC dumps which are covered by individual decoders, too. Ideally detection results would be identical, but in practise the annotation positions and the level of details will differ between implementations due to their internal operation and design choices. The IRMP test set also covers dumps which are not covered by other IR decoders. It's interesting to see how not all key repetitions are caught and how single press might be missed as well. It's valuable to remain aware during maintenance, and see how occassional failure changes. This is why an empty output for a non-empty dump is kept here, too.
Diffstat (limited to 'decoder/test/arm_etmv3/stm32f105/etmv3.output')
0 files changed, 0 insertions, 0 deletions