We have three sets of tests:
- the normal unit tests (ninja test)
- integration tests using GstValidate.
- manual tests
Since version 0.91, our backend test suite is much smaller and simpler; since most of the core functionality is now handled by GES, you need to run GES's test suite instead if you want to test more thoroughly.
You can run the tests with the
ptvtests alias created when you enter
the development environment:
$ alias ptvtests ptvtests='ptvenv gst-validate-launcher /.../pitivi-dev/pitivi/tests/ptv_testsuite.py'
NOTE: If you are on macOS or Windows, replace
Run the entire unit tests suite:
Run only the tests in a particular file:
$ ptvtests -t test_project
Run only one particular unit test:
$ ptvtests -t tests.test_project.TestProjectManager.test_loading_missing_project_file
Normally it should work to use just the name of the test method:
$ ptvtests -t test_loading_missing_project_file
To lists all the available tests, run:
$ ptvtests -L
Writing unit tests
We use the
unittest.mock module extensively for writing unit tests for
The integration tests are run with GstValidate. They are located in the
.scenario file in the
subdirectory contains a sequence of actions which represent a test.
When a test is run, the actions in the scenario are performed by handlers in pitivi/utils/validate.py, or by handlers in GES. The handlers generally act on the widgets and check the expected effect has been obtained on the GES objects. Besides the checks integrated in the handlers, for now it is not possible to have additional checks.
A scenario file is created automatically each time Pitivi is used.
You can run the integration tests with:
$ ptvenv tests/validate-tests/runtests
Standard QA Scenarios – No description available
The results of the search are