QA SoftVision Team/Mobile/Writing tests - Revision history

Edmorley: Bug 1082602

2014-12-21T17:08:51Z

Bug 1082602

← Older revision		Revision as of 17:08, 21 December 2014
Line 547:		Line 547:
	hg push -f -rtip ssh://<user>@hg.mozilla.org/try/		hg push -f -rtip ssh://<user>@hg.mozilla.org/try/

	* This will push the changes and will give you a ~~tbpl~~ link to your push		* This will push the changes and will give you a Treeherder link to your push
	* When the building process for the test build will start you will also receive an email with the push info		* When the building process for the test build will start you will also receive an email with the push info

AdrianT: /* How to start when writing a new test */

2013-11-04T07:08:56Z

How to start when writing a new test

← Older revision		Revision as of 07:08, 4 November 2013
Line 13:		Line 13:
	* If you already have the sources downloaded update to the lates version by running the command in the sources directory:		* If you already have the sources downloaded update to the lates version by running the command in the sources directory:
	hg pull -u		hg pull -u
	* Make the build by running ~~in '''superuser''' (sudo su) and make sure the [https://wiki.mozilla.org/QA_SoftVision_Team/Mobile/Robocop_automation_setup#Update_Android_SDK PATH] variable is updated with the Android SDK location~~:		* Make the build by running:
	make -f client.mk		make -f client.mk
	* Create a new file named "test" followed by the test name and with the extention "java.in" : for e.g. ''testBookmarks.java.in''		* Create a new file named "test" followed by the test name and with the extention "java.in" : for e.g. ''testBookmarks.java.in''

AdrianT: /* Substituting mSolo.sleep */

2013-11-01T08:34:42Z

Substituting mSolo.sleep

@@ Line 420: / Line 420: @@
 * Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)
 = Substituting mSolo.sleep =
 = Updating your test directory =
 It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .

AdrianT at 08:26, 1 November 2013

2013-11-01T08:26:47Z

← Older revision		Revision as of 08:26, 1 November 2013
Line 419:		Line 419:
	* You can use mAsserter.dumpLog(Sting) or mAsserter.ok(true, Sting, String) to print any string or value of any variable		* You can use mAsserter.dumpLog(Sting) or mAsserter.ok(true, Sting, String) to print any string or value of any variable
	* Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)		* Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)
			= Substituting mSolo.sleep =
	= Updating your test directory =		= Updating your test directory =
	It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .		It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .

AdrianT: /* Updating your test directory */

2013-07-10T08:36:51Z

Updating your test directory

← Older revision		Revision as of 08:36, 10 July 2013
Line 431:		Line 431:
	<pre>		<pre>
	cd objdir		cd objdir
	~~sudo~~ make -C build/mobile/robocop/		make -C build/mobile/robocop/
	~~sudo~~ make package </pre>		make package </pre>

	= Creating a diff patch file =		= Creating a diff patch file =

AdrianT at 14:58, 10 June 2013

2013-06-10T14:58:36Z

@@ Line 168: / Line 168: @@
 url
 </pre>
 = Basic code sequences to do different actions =

AdrianT: /* Pushing the patch */

2013-05-20T15:02:06Z

Pushing the patch

← Older revision		Revision as of 15:02, 20 May 2013
Line 354:		Line 354:
	Adds the last patch to the top of the queue. Alternatively you can specify a patch name to add.		Adds the last patch to the top of the queue. Alternatively you can specify a patch name to add.

	hg push [<patch_name>]		hg push -v [<patch_name>]

	== Viewing the diff file ==		== Viewing the diff file ==

AdrianT: /* Debugging using logs */

2013-04-25T12:16:31Z

Debugging using logs

← Older revision		Revision as of 12:16, 25 April 2013
Line 282:		Line 282:
	* You can see the screenshot of the output the moment the test failed		* You can see the screenshot of the output the moment the test failed
	== Debugging using logs ==		== Debugging using logs ==
	* You can use mAsserter.~~dump~~(Sting) or mAsserter.ok(true, Sting, String) to print any string or value of any variable		* You can use mAsserter.dumpLog(Sting) or mAsserter.ok(true, Sting, String) to print any string or value of any variable
	* Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)		* Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)

	= Updating your test directory =		= Updating your test directory =
	It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .		It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .

AdrianT at 14:26, 24 April 2013

2013-04-24T14:26:18Z

← Older revision		Revision as of 14:26, 24 April 2013
Line 274:		Line 274:
	mAsserter.ok(list != null, "checking that all pages list exists", list.toString()); // tests if		mAsserter.ok(list != null, "checking that all pages list exists", list.toString()); // tests if
	the list is null and if it isn't it prints the list after printing the message of what the test does		the list is null and if it isn't it prints the list after printing the message of what the test does
			= Debugging tests =
			== See the screenshot from the fail in the try run ==
			* Open the link to the tryrun and view the full logs of the failed run
			* Go the the position the fail you are interested in has happened
			* Search for "base64" and copy the hole line from the log
			* Remove the "SCREENSHOT" from the beginning of the string and paste it in the URL bar of the browser
			* You can see the screenshot of the output the moment the test failed
			== Debugging using logs ==
			* You can use mAsserter.dump(Sting) or mAsserter.ok(true, Sting, String) to print any string or value of any variable
			* Note that you will need to cast the variable to String in order to print it: String.valueOf(Variable)
	= Updating your test directory =		= Updating your test directory =
	It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .		It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini .

AdrianT: /* Push the changes to the tryserver */

2013-03-18T10:38:41Z

Push the changes to the tryserver

← Older revision		Revision as of 10:38, 18 March 2013
Line 382:		Line 382:
	hg push -f -rtip ssh://<user>@hg.mozilla.org/try/		hg push -f -rtip ssh://<user>@hg.mozilla.org/try/

	* This will push the changes and will give you a ~~tblp~~ link to your push		* This will push the changes and will give you a tbpl link to your push
	* When the building process for the test build will start you will also receive an email with the push info		* When the building process for the test build will start you will also receive an email with the push info