summaryrefslogtreecommitdiff
path: root/unittests/json_results_update_tests.py
AgeCommit message (Collapse)AuthorFilesLines
2016-04-16unittests: Fix spelling mistakesEric Engestrom1-1/+1
Signed-off-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Dylan Baker <baker.dylan.c@gmail.com> Signed-off-by: Vinson Lee <vlee@freedesktop.org>
2016-04-13unittests: Fix tests that leave temporary files laying aroundDylan Baker1-12/+4
These are a bit more complicated, and the solution is more difficult. Basically the problem is that the temporary file gets renamed out from under the test, and the name of the file is a generated and unknown. To get rid of these I've wrapped the shared private method in the utils.test_in_tempdir, and extended that decorator to return a value. This is kind of a hack, and all of this should be fixed by mocking out things rather than using files. Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
2016-02-08framework,unittests: use __future__ unicode_literalsDylan Baker1-1/+3
Use unicode_literals from __future__. This makes undecorated strings (those not using and b or u prefix) into unicode instead of bytes in python 2. This means that bytes strings need to have a b prefix now. This also fixes a couple of unittests that broke during the transition. Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com> Acked-by: Jose Fonseca <jfonseca@vmware.com>
2016-02-08python: use six.{iter,view}{items,keys,values}Dylan Baker1-3/+5
This was initially generated via the following sed command: sed -i \ -e 's@in \(.*\)\.iter\(values,keys,items\)()@in six.iter\2(\1)@g' \ -e 's@in \(.*\..*\)\.iter\(values,keys,items\)()@in six.iter\2(\1)@g' Then cleaned up by hand, including changes for view*. Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com> Acked-by: Jose Fonseca <jfonseca@vmware.com>
2016-01-08unittests: move framework/tests to unittestsDylan Baker1-0/+819
Currently the framework is pretty confusing. There's 'test' which is a package containing test classes, then there's 'tests' which contains unit tests for the framework. This is obviously not optimal. Beyond that the unittests get installed, and that isn't really necessary. As a bonus this removes the unit tests from coverage reports, which is a nice plus. Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>