lp:~zyga/checkbox/device-profiles

Branch merges

Propose for merging

No branches dependent on this one.

On hold for merging into lp:checkbox

Checkbox Developers: Pending requested 2013-02-18

Diff: 278 lines (+177/-51)

3 files modified

plainbox/plainbox/impl/integration_tests.py (+106/-44)
plainbox/plainbox/test-data/integration-tests/cpu/scaling_test.json (+11/-7)
plainbox/plainbox/testing_utils/resource.py (+60/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

2237. By Zygmunt Krynicki on 2013-07-05

plainbox:test-data: update integration testing scenarios to the current format

The real change is anchoring the result in the "result" key and adding
"job_name" as a parameter.

Signed-off-by: Zygmunt Krynicki <email address hidden>

2236. By Zygmunt Krynicki on 2013-07-05

plainbox:integration_tests: skip scenarios that are not intended for the current profile

[work in progress]

Profile is currently hard-coded as there is no easy way to pass it from
the test loader. This needs more work.

Signed-off-by: Zygmunt Krynicki <email address hidden>

2235. By Zygmunt Krynicki on 2013-07-05

plainbox:integration_tests: replace test_job_result() with test_job_result() and test_job_return_code()

The old test_job_result() was responsible for loading and running
everything. The new methods just observe state that was established
during setUp()

Signed-off-by: Zygmunt Krynicki <email address hidden>

Conflicts:
 plainbox/plainbox/impl/integration_tests.py

2234. By Zygmunt Krynicki on 2013-07-05

plainbox:integration_tests: load scenario data and run the job (if needed) during setUp()

This allows actual test methods to simply check if some of the
job result (be it return code or the output) matches expectations
encoded in the test scenario, thus making tests easier to read.

Signed-off-by: Zygmunt Krynicki <email address hidden>

2233. By Zygmunt Krynicki on 2013-07-05

plainbox:integration_tests: parametrize integration tests by scenario path, not job name

To support testing a single job multiple times (in various configurations)
we need to decouple the test scenario from the job it operates on.

Each job can have multiple scenarios that affect it, for example
with and without dependencies, on various OS versions, with various
hardware, etc.

[ this patch breaks the tree but is shorter to review ]

Signed-off-by: Zygmunt Krynicki <<email address hidden>

2232. By Zygmunt Krynicki on 2013-07-05

plainbox:integration_tests: add load_scenario_data() and execute_job()

[work in progress, needs docstring updates]

Those functions are going to replace the current implementation of
integration test suite. They grew to be too big to keep in the test
class itself

Signed-off-by: Zygmunt Krynicki <email address hidden>

2231. By Zygmunt Krynicki on 2013-07-05

plainbox:testing_utils: add ResourceCache

[work in progress, needs to become weak]

This class allows to share data among test cases.
It is used by integration tests to run jobs once and observe multiple
properties of each job in a separate test case.

Signed-off-by: Zygmunt Krynicki <email address hidden>

2230. By Zygmunt Krynicki on 2013-07-04

"[r=zkrynicki][bug=][author=zkrynicki] automatic merge by tarmac"

2229. By Zygmunt Krynicki on 2013-07-04

"[r=zkrynicki,roadmr,brendan-donegan][bug=][author=zkrynicki] automatic merge by tarmac"

2228. By Alberto Milone on 2013-07-04

"[r=brendan-donegan][bug=][author=albertomilone] checkbox-old/scripts/color_depth_info:
1) Prevent a UnicodeDecodeError. I can reproduce this with Python 3 in Saucy (the one in Precise works fine)
2) Be more strict in the regex so that we don't catch undesired strings."