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

[Christopher Lee]

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

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

[Leo Arias (elopio)]

Thanks.

review: Approve

[PS Jenkins bot (ps-jenkins)]

review: Approve (continuous-integration)

=== modified file 'docs/faq/faq.rst'
--- docs/faq/faq.rst	2015-01-22 16:37:38 +0000
+++ docs/faq/faq.rst	2015-01-25 23:12:49 +0000
@@ -182,7 +182,7 @@
 
 For instance launching gedit is as easy as::
 
-  $ autopilot launch gedit
+  $ autopilot3 launch gedit
 
 *Autopilot launch* attempts to detect if you are launching either a Gtk or Qt
 application so that it can enable the correct libraries. If is is unable to
@@ -198,7 +198,7 @@
 inform autopilot that it is a Qt application so that it can enable the correct
 support::
 
-  $ autopilot launch -i Qt testapp.py
+  $ autopilot3 launch -i Qt testapp.py
 
 Now that it has been launched with Autopilot support we can introspect and
 explore out application using the :ref:`vis tool <visualise_introspection_tree>`.
 
=== modified file 'docs/tutorial/getting_started.rst'
--- docs/tutorial/getting_started.rst	2014-05-16 02:09:23 +0000
+++ docs/tutorial/getting_started.rst	2015-01-25 23:12:49 +0000
@@ -149,7 +149,7 @@
 
 From the root of this directory structure, we can ask autopilot to list all the tests it can find::
 
-	$ autopilot list example
+	$ autopilot3 list example
 	Loading tests from: /home/thomi/code/canonical/autopilot/example_test
 
 	    example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
@@ -161,7 +161,7 @@
 
 To run our test, we use the autopilot 'run' command::
 
-	$ autopilot run example
+	$ autopilot3 run example
 	Loading tests from: /home/thomi/code/canonical/autopilot/example_test
 
 	Tests running...
@@ -171,7 +171,7 @@
 
 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::
 
-	$ autopilot run -v example
+	$ autopilot3 run -v example
 	Loading tests from: /home/thomi/code/canonical/autopilot/example_test
 
 	Tests running...
@@ -196,7 +196,7 @@
 
 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::
 
-	$ autopilot run example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
+	$ autopilot3 run example.tests.test_window.MainWindowTitleTests.test_main_window_title_string
 
 .. _tut_test_with_interaction: