<h1>Using Travis<aclass="headerlink"href="#using-travis"title="Permalink to this headline">¶</a></h1>
<p>Evennia uses <aclass="reference external"href="http://travis-ci.org/">Travis CI</a> to check that it’s building successfully after every commit to its Github repository (you can for example see the <codeclass="docutils literal notranslate"><spanclass="pre">build:</span><spanclass="pre">passing</span></code> badge at the top of Evennia’s <aclass="reference external"href="https://github.com/evennia/evennia">Readme file</a>). If your game is open source on Github you may also use Travis for free. See <aclass="reference external"href="http://docs.travis-ci.com/user/getting-started/">the Travis docs</a> for how to get started.</p>
<p>After logging in you will get to point Travis to your repository on github. One further thing you need to set up yourself is a Travis config file named <codeclass="docutils literal notranslate"><spanclass="pre">.travis.yml</span></code> (note the initial period <codeclass="docutils literal notranslate"><spanclass="pre">.</span></code>). This should be created in the root of your game directory. The idea with this file is that it describes what Travis needs to import and build in order to create an instance of Evennia from scratch and then run validation tests on it. Here is an example:</p>
<p>This will tell travis how to download Evennia, install it, set up a database and then run the test suite.
You need to add this file to git (<codeclass="docutils literal notranslate"><spanclass="pre">git</span><spanclass="pre">add</span><spanclass="pre">.travis.yml</span></code>) and then commit your changes before Travis will be able to see it.</p>
<p>For properly testing your game you of course also need to write unittests. <aclass="reference internal"href="Unit-Testing.html"><spanclass="doc">We have a page</span></a> on how we set those up for Evennia, you should be able to refer to that for making tests fitting your game.</p>
