|
254.1.1
by Girish Rawat
Improved and extended READMEs. |
1 |
Running QML Unit Tests
|
2 |
======================
|
|
3 |
||
4 |
QML Unit Tests help with testing the internal working of components while |
|
5 |
autopilot tests help with testing the UI workflow as experience by the user. |
|
6 |
Running QML tests is quite simple and very fast. |
|
7 |
||
8 |
If you are submitting your bugfix/patch to the calculator app, please follow the |
|
9 |
following steps below to check whether that all tests pass before proposing a |
|
10 |
merge request. |
|
11 |
||
12 |
Running all unit test at once
|
|
13 |
=============================
|
|
14 |
||
15 |
* If you want to run all tests, then run the following command,
|
|
16 |
||
17 |
$ ctest --output-on-failure |
|
18 |
||
19 |
* If you want more verbose output, then run,
|
|
20 |
||
21 |
$ ctest -VV |
|
22 |
||
23 |
Running individual test cases,
|
|
24 |
==============================
|
|
25 |
||
26 |
If you want to run testcases individually, you can do so by navigating to the |
|
27 |
unit tests folder by, |
|
28 |
||
29 |
* Navigate to the tests/unit directory
|
|
30 |
||
31 |
$ cd tests/unit |
|
32 |
||
33 |
* Run the test by providing their filenames
|
|
34 |
||
35 |
$ qmltestrunner tst_hellocomponent.qml |
|
36 |