On 15/05/13 12:52 PM, Gawlas, Julius wrote:
One of our users is interested in running a secret test, which is a test
that has legal restrictions on who can run it.
Let’s say we are given some test covered by NDA and it was agreed that
only limited set of people can see it and run the code. How would we go
about hooking such test to autotest instance?
Any ideas or pointers?
Should be pretty simple.
'Secret' tests were very common back when I worked for IBM, and google
also had its own internal tests. What we did back then was to have a
separate repo that contains the test modules and put them under
client/site_tests.
The tests could be elsewhere, global_config.ini can point out to other
filesystem locations where this repo could be.
There are other options, such as putting them in tarballs and passing
the urls to job.run_test(), as it is described here:
https://github.com/autotest/autotest/wiki/ExternalTests
So I'd say there is no shortage of options you can use here.
Now maybe you want to imply that other people can't look at the code or
the results of such tests at all. In this case, well... I don't know,
there are no provisions for obfuscating test results on an autotest
server. Perhaps using kerberos/ldap auth and restricting the list of
allowed logins?
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
