Merge pull request #78 from autotest/travis-ci

Travis ci

.travis.yml

+language: python
+python:
+    - "2.7"
+
+branches:
+    only:
+        - master
+
+virtualenv:
+    system_site_packages: true
+
+before_script:
+    - echo "deb http://ppa.launchpad.net/lmr/autotest/ubuntu saucy main" | sudo tee -a /etc/apt/sources.list
+    - sudo apt-get update -q
+    - sudo apt-get -y --force-yes install autotest
+
+install:
+    - pip install sphinx tox simplejson MySQL-python pylint autopep8
+    - pip install inspektor
+    - pip install -r requirements.txt
+
+script:
+    - inspekt lint

README.rst

+================================
+QEMU test provider for virt-test
+================================
+
+This is the official [1] test provider for the following
+subtest types:
+
+* QEMU
+* Generic (Virtualization backend agnostic)
+* OpenVSwitch
+
+Really quick start guide
+------------------------
+
+1) Fork this repo on github
+2) Create a new topic branch for your work
+3) Create a new test provider file in your virt test repo,
+   like:
+
+::
+
+    cp io-github-autotest-qemu.ini myprovider.ini
+::
+
+    [provider]
+    uri: file:///home/foo/Code/tp-qemu
+    [generic]
+    subdir: generic/
+    [qemu]
+    subdir: qemu/
+    [openvswitch]
+    subdir: openvswitch/
+You can optionally delete temporarily the
+`io-github-autotest-qemu.ini` file, just so you don't have test
+conflicts. Then you can develop your new test code, run it
+using virt test, and commit your changes.
+
+4) Make sure you have `inspektor installed. <https://github.com/autotest/inspektor#inspektor>`_
+5) Run:
+
+::
+
+    inspekt lint
+    inspekt style
+6) Fix any problems
+7) Push your changes and submit a pull request
+8) That's it.
+
+[1] You can always create your own test provider, if you have special purposes, or just want to develop your work indepentently.

requirements.txt

+coverage==3.6
+nose==1.3.0
+nosexcover==1.0.8
+tox==1.5.0
+virtualenv==1.9.1