[Avocado-devel] Port autotest client tests to avocado: next steps?

Amador Pahim apahim at redhat.com
Mon Jan 11 17:12:00 UTC 2016


Hello,

In a first interaction trying to port autotest client tests to avocado, 
I could verify the port was quite simple for the tests I worked on 
(stress, compilebench, aiostress and bonnie). These 4 tests are already 
present in examples/tests/ directory.

There are currently 105 tests in avocado-client-tests and we should now 
discuss if/when(priority?) are we going to port them all and, if yes, 
some extra points should be discussed:

- Many tests are just a matter of extract/configure/make a tarball and 
run the binary with proper arguments. Instead of writing one test per 
tarball, we could create a base test and vary only the yaml file 
containing the url to on-demand download the tarball and the arguments 
to be used with the resulting binary.

- Either downloading the tarball during the test or keeping the tarball 
in the repository, should we create a separate repository to keep all 
those tests/tarballs?

The hope is we can discuss/define the next steps regarding this matter. 
Could you share your thoughts?

Best,
--
apahim




More information about the Avocado-devel mailing list