Conversation
| @psh.run | ||
| def harness(p): |
There was a problem hiding this comment.
I'm considering whether to organize the tests in a uniform manner, for example, in relation to the CONTROL CODE CHEAT SHEET, and whether to expand the tests from basic ones that test a given control code, to tests that use several, and up to those that use as many as possible. It would be beneficial if the combinations reflected real-world scenarios. So, then you could also divide the tests into separate functions (?)
There was a problem hiding this comment.
This test is just to check that this control codes works, doesn't need to test them with full possibility use set.
d8ba5ca to
01345a4
Compare
0ef59b3 to
c4c686e
Compare
c4c686e to
4061065
Compare
4061065 to
865eb37
Compare
865eb37 to
ae3958c
Compare
ae3958c to
c213850
Compare
Unit Test Results8 442 tests - 991 7 918 ✅ - 926 42m 4s ⏱️ - 7m 24s Results for commit de178e1. ± Comparison against base commit f646ce7. This pull request removes 1000 and adds 9 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
4eeaf60 to
b369a37
Compare
JIRA: CI-397
JIRA: CI-397
b369a37 to
de178e1
Compare
Description
JIRA: CI-397
Motivation and Context
Types of changes
How Has This Been Tested?
Checklist:
Special treatment
psh: Add fast cursor movement and cut&paste phoenix-rtos-utils#211
armv7a9-qemu: Adjust serial device phoenix-rtos-project#997
Using armv7a9-zynq7000-qemu startup script without qemu control #352
stm32l4-multi: add support for DMA on STM32N6 phoenix-rtos-devices#592
scripts: add zynqmp-qemu script with adjust serial control for CC test phoenix-rtos-project#1434