Dear all, I'd be grateful for clarifying a few issues regarding Autotest.
I have following setup: 1. Custom HW interface to connect Target to Host 2. Target board with Linux 3. Host PC - debian/ubuntu. I would like to unify the test setup and it seems that the Autotest test framework has all the features that I would need: - Extensible Host class (other interfaces can be used for communication - i.e. USB) - SSH support for sending client tests from Host to Target - Control of tests execution on Target from Host and gathering results - Standardized tests results format - Autotest host's and client's test results are aggregated and displayed as HTML - Possibility to easily reuse other tests (like LTP, linaro's PM-QA) - Scheduling, HTML visualization (if needed) On the beginning I would like to use test harness (server+client) to run tests and gather results in a structured way. However, I have got a few questions (please correct me if I'm wrong): - On several presentations it was mentioned that Avocado project is a successor of Autotest. However it seems that Avocado is missing the client + server approach from Autotest. - What is the future of Autotest? Will it be gradually replaced by Avocado? - It seems that there are only two statuses returned from a simple test (like sleeptest), namely "PASS" and "FAIL". How can I indicate that the test has ended because the environment was not ready to run the test (something similar to LTP's "BROK" code, or exit codes complying with POSIX 1003.1)? - Is there any road map for Autotest development? I'm wondering if avocado's features (like per test SHA1 generation) would be ported to Autotest? Thanks in advance for support. -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
