Autopilot

Merge lp:~canonical-platform-qa/autopilot/docs-autopilot-to-autopilot3-command into lp:autopilot

  1. docs-autopilot-to-autopilot3-command
  2. Merge into trunk
Proposed by Christopher Lee
Status: Merged
Approved by: Leo Arias
Approved revision: 536
Merged at revision: 537
Proposed branch: lp:~canonical-platform-qa/autopilot/docs-autopilot-to-autopilot3-command
Merge into: lp:autopilot
Diff against target: 60 lines (+6/-6)
2 files modified
docs/faq/faq.rst (+2/-2)
docs/tutorial/getting_started.rst (+4/-4)
To merge this branch: bzr merge lp:~canonical-platform-qa/autopilot/docs-autopilot-to-autopilot3-command
Reviewer Review Type Date Requested Status
PS Jenkins bot continuous-integration Approve
Leo Arias (community) Approve
Review via email: mp+247541@code.launchpad.net

Commit message

Update docs from using `autopilot` to `autopilot3` command.

Description of the change

Update docs from using `autopilot` to `autopilot3` command. (just updated the few that were missed in the recent docs sprint.)

To post a comment you must log in.
Revision history for this message
Leo Arias (elopio) wrote :

Thanks.

review: Approve
Revision history for this message
PS Jenkins bot (ps-jenkins) :
review: Approve (continuous-integration)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'docs/faq/faq.rst'
2--- docs/faq/faq.rst 2015-01-22 16:37:38 +0000
3+++ docs/faq/faq.rst 2015-01-25 23:12:49 +0000
4@@ -182,7 +182,7 @@
5
6 For instance launching gedit is as easy as::
7
8- $ autopilot launch gedit
9+ $ autopilot3 launch gedit
10
11 *Autopilot launch* attempts to detect if you are launching either a Gtk or Qt
12 application so that it can enable the correct libraries. If is is unable to
13@@ -198,7 +198,7 @@
14 inform autopilot that it is a Qt application so that it can enable the correct
15 support::
16
17- $ autopilot launch -i Qt testapp.py
18+ $ autopilot3 launch -i Qt testapp.py
19
20 Now that it has been launched with Autopilot support we can introspect and
21 explore out application using the :ref:`vis tool <visualise_introspection_tree>`.
22
23=== modified file 'docs/tutorial/getting_started.rst'
24--- docs/tutorial/getting_started.rst 2014-05-16 02:09:23 +0000
25+++ docs/tutorial/getting_started.rst 2015-01-25 23:12:49 +0000
26@@ -149,7 +149,7 @@
27
28 From the root of this directory structure, we can ask autopilot to list all the tests it can find::
29
30- $ autopilot list example
31+ $ autopilot3 list example
32 Loading tests from: /home/thomi/code/canonical/autopilot/example_test
33
34 example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
35@@ -161,7 +161,7 @@
36
37 To run our test, we use the autopilot 'run' command::
38
39- $ autopilot run example
40+ $ autopilot3 run example
41 Loading tests from: /home/thomi/code/canonical/autopilot/example_test
42
43 Tests running...
44@@ -171,7 +171,7 @@
45
46 You will notice that the test application launches, and then dissapears shortly afterwards. Since this test doesn't manipulate the application in any way, this is a rather boring test to look at. If you ever want more output from the run command, you may specify the '-v' flag::
47
48- $ autopilot run -v example
49+ $ autopilot3 run -v example
50 Loading tests from: /home/thomi/code/canonical/autopilot/example_test
51
52 Tests running...
53@@ -196,7 +196,7 @@
54
55 Both the 'list' and 'run' commands take a test id as an argument. You may be as generic, or as specific as you like. In the examples above, we will list and run all tests in the 'example' package (i.e.- all tests), but we could specify a more specific run criteria if we only wanted to run some of the tests. For example, to only run the single test we've written, we can execute::
56
57- $ autopilot run example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
58+ $ autopilot3 run example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
59
60 .. _tut_test_with_interaction:
61

Subscribers

People subscribed via source and target branches