introduction of greentea - the CI system of mbedos
I get an introduction for ARM mbed-os team CI framework (GreenTea). https://os.mbed.com/docs/mbed-os/v5.15/tools/greentea-testing-applications.html
From my observation, the greentea is less matured than our SanityCheck + west system. The only ideas that come to my mind is:
1. Do we need to move the sanitycheck out of zephyr and make it as a separated module?
a) We can leave a lightweight wrapper script in zephyr for easy use of developer, but move mass of things to a separated module.
2. Do we give sanitycheck a project name?
I try to persuade LAVA to accept use docker environment(python3 run time), and just act as a distribute scheduler. Looks like ARM greentea has the same request. Further discussion will be followed.