Frequently Asked Questions¶

How do I install the client?¶

sudo apt-add-repository ppa:utah/stable
sudo apt-get update
sudo apt-get install utah-client

Is there an example testsuite I can look at?¶

There is an example testsuite.

How do I run the utah-client locally?¶

sudo utah -r <master.run>

Why are there so many control files?¶

The goal of UTAH is to make sharing and reusing testsuites and testcases as easy as possible. The control files make it possible to define testcases and testsuites fully and allow a third party using a testsuite or testcase the control they need to run the them in their own environment and to suit their own needs.

Can I run the utah client on a local testsuite?¶

You can, but it must be in a supported (bzr, git) local repository.

Why doesn’t the utah client support running a testsuite in the current directory or a local copy?¶

In order to maintain tracability utah needs to know which version of a testsuite was run. This is the reason we require testsuites be in a VCS. This makes troubleshooting test failures and reproducing test runs in other environments much easier and more reliable.

How do I get help with writing or migrating my tests to UTAH?¶

Send an email to ubuntu-utah-devel@lists.ubuntu.com and we will be happy to help you.

What provisioning methods are currently supported?¶

Virtual machines via kvm and qemu are currently supported and physical machines via cobbler. The physical machine support is specific to the Ubuntu Engineering QA Lab setup.

Do you support provisioning LXC, existing VMS, of other methods?¶

Not at this time. There are plans for adding new provisioning methods and we’d be happy to review merge proposals. The branch is in launchpad under the UTAH project.