Test framework - Revision history

Stevenlawrance: /* Live versus Simulated Testing */

2007-09-09T02:53:40Z

Live versus Simulated Testing

← Older revision		Revision as of 02:53, 9 September 2007
Line 8:		Line 8:

	===Live versus Simulated Testing===		===Live versus Simulated Testing===
	By default, Thunderforce's test suite will run against a simulated Salesforce.com API. Note that this simulation is very basic and highly tuned for the tests; it's not a replacement for Salesforce.com and has nowhere near its level of functionality.		By default, Thunderforce's test suite will run against a [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/components/nsSalesforcePartnerSimulator.js simulated Salesforce.com API]. Note that this simulation is very basic and highly tuned for the tests; it's not a replacement for Salesforce.com and has nowhere near its level of functionality.

	When you want to run the tests live against your developer edition organization in Salesforce.com (please don't run the tests using your production organization), follow these steps to configure it:		When you want to run the tests live against your developer edition organization in Salesforce.com (please don't run the tests using your production organization), follow these steps to configure it:

Stevenlawrance: /* Assertion Methods */

2007-09-09T02:52:39Z

Assertion Methods

← Older revision		Revision as of 02:52, 9 September 2007
Line 45:		Line 45:

	===assertTrue(name, toEval)===		===assertTrue(name, toEval)===
	*Ensures that toEval is true		*Ensures that toEval is true. The string literal "true" also works
	*This assertion fails when toEval is false		*This assertion fails when toEval is false

	===assertFalse(name, toEval)===		===assertFalse(name, toEval)===
	*Ensures that toEval is false		*Ensures that toEval is false. The string literal "false" also works
	*This assertion fails when toEval is true		*This assertion fails when toEval is true

Stevenlawrance: /* Live versus Simulated Testing */

2007-09-09T02:51:52Z

Live versus Simulated Testing

← Older revision		Revision as of 02:51, 9 September 2007
Line 19:		Line 19:
	#Adjust the following settings to your testing preferences:		#Adjust the following settings to your testing preferences:
	#*'''thunderforcetest.username''' - Your developer edition organization login username		#*'''thunderforcetest.username''' - Your developer edition organization login username
	#*'''thunderforcetest.password''' - Your developer edition organization login password		#*'''thunderforcetest.password''' - Your developer edition organization login password. Note that this is saved as clear text in your ThunderforceTest profile's prefs.js file
	#*'''thunderforcetest.email''' - An email address that you want test email messages to be set to, which applies to tests that send email		#*'''thunderforcetest.email''' - An email address that you want test email messages to be set to, which applies to tests that send email
	#*'''thunderforcetest.live''' - When true, the real Salesforce.com is used for testing. When false, a simulated Salesforce.com is used		#*'''thunderforcetest.live''' - When true, the real Salesforce.com is used for testing. When false, a simulated Salesforce.com is used

Stevenlawrance: /* Running Tests */

2007-09-09T02:49:42Z

Running Tests

@@ Line 6: / Line 6: @@
 ==Running Tests==
 To run tests, [[Getting Started - Developer#Eclipse configurations for running and debugging Thunderforce|create the Eclipse run configurations for tests]] and then run those. Those configurations use the "-thunderforceTest Label" command line option in the Thunderforce testing extension to run basic, normal, extra, or all tests. By default, running with the -thunderforceTest option prevents Thunderbird's main user interface from being displayed, but it's possible to force Thunderbird to show with the -thunderforceRunThunderbird command line option. The [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/components/nsThunderforceTestCommandLine.js nsThunderforceTestCommandLine.js] file handles the command line options for Thunderforce testing.
 ==Creating Tests==

Stevenlawrance at 17:12, 6 September 2007

2007-09-06T17:12:41Z

← Older revision		Revision as of 17:12, 6 September 2007
Line 1:		Line 1:
	Thunderforce's test framework uses [http://xulunit.mozdev.org/ XULUnit] for both unit and integration testing.		Thunderforce's test framework uses a customized version of [http://xulunit.mozdev.org/ XULUnit] for both unit and integration testing.

	==Test Architecture - Deployment View==		==Test Architecture - Deployment View==

Stevenlawrance at 17:12, 6 September 2007

2007-09-06T17:12:11Z

← Older revision		Revision as of 17:12, 6 September 2007
Line 1:		Line 1:
	Thunderforce's test framework uses ~~XULRunner~~ for both unit and integration testing.		Thunderforce's test framework uses [http://xulunit.mozdev.org/ XULUnit] for both unit and integration testing.

	==Test Architecture - Deployment View==		==Test Architecture - Deployment View==

Stevenlawrance: /* Creating Tests */

2007-08-14T14:07:31Z

Creating Tests

← Older revision		Revision as of 14:07, 14 August 2007
Line 19:		Line 19:
	#Add a test by creating a new function and adding it to the appropriate code block at the top of the file. As an example, if you are adding a basic test, then you can add the following to the "if (runBasicTests) { }" block: nsTheComponentTests.add(new TestCase("My test case name", testMyNewBasicTestFunction));		#Add a test by creating a new function and adding it to the appropriate code block at the top of the file. As an example, if you are adding a basic test, then you can add the following to the "if (runBasicTests) { }" block: nsTheComponentTests.add(new TestCase("My test case name", testMyNewBasicTestFunction));
	#*In the test function's definition, call at least one of the methods in the [[Test framework#Assertion Methods\|assertion methods section]] to assert conditions. Each function requires a name that will appear under the test case in the XULUnit tree		#*In the test function's definition, call at least one of the methods in the [[Test framework#Assertion Methods\|assertion methods section]] to assert conditions. Each function requires a name that will appear under the test case in the XULUnit tree
			#*When referencing interfaces within Components.interfaces, please check if that interface has a constant declared at the top of [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/baseTest.js baseTest.js]. As an example, you can reference nsIProperties instead of having to write out Components.interfaces.nsIProperties. Add other interfaces to this file instead of your test file. When XULUnit is run, all JavaScript files referenced in the XUL file are compiled together. If multiple tests define the same constants, then the JavaScript code will not compile, necessitating the common constants to be defined in one place. The Components.interfaces constants are roughly similar in nature to Java's "import" keyword
	#Try out your test by running it. See the [[Getting Started - Developer#Eclipse configurations for running and debugging Thunderforce\|developer startup instructions for Eclipse running and debugging configurations]] to see how to set up the Eclipse run configurations for tests		#Try out your test by running it. See the [[Getting Started - Developer#Eclipse configurations for running and debugging Thunderforce\|developer startup instructions for Eclipse running and debugging configurations]] to see how to set up the Eclipse run configurations for tests

Stevenlawrance at 04:14, 14 August 2007

2007-08-14T04:14:08Z

@@ Line 2: / Line 2: @@
 ==Test Architecture - Deployment View==
-The Thunderforce test framework exists as a Thunderbird extension in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/ tests folder in Subversion]. Within that folder, test suites exist in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/ content subfolder] with a file name that equals the name of the [https://www.moonlightdesign.org/thunderforce/svn/trunk/extension/components/ XPCOM component] that the test suite tests. Each test suite is included in the test framework by being included as a &lt;script/&gt; line in [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/testrunner.xul testrunner.xul].
+The Thunderforce test framework exists as a Thunderbird extension in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/ tests folder in Subversion]. Withinthat folder, test suites exist in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/ content subfolder] with a file name that equals the name of the [https://www.moonlightdesign.org/thunderforce/svn/trunk/extension/components/ XPCOM component] that the test suite tests. Each test suite is included in the test framework by being included as a &lt;script/&gt; line in [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/testrunner.xul testrunner.xul].
 ==Running Tests==
@@ Line 8: / Line 8: @@
 ==Creating Tests==
-'''being written...'''
+To create unit and functionality tests for Thunderforce, please follow the following process:

Stevenlawrance at 21:12, 12 August 2007

2007-08-12T21:12:41Z

← Older revision		Revision as of 21:12, 12 August 2007
Line 2:		Line 2:

	==Test Architecture - Deployment View==		==Test Architecture - Deployment View==
			The Thunderforce test framework exists as a Thunderbird extension in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/ tests folder in Subversion]. Within that folder, test suites exist in the [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/ content subfolder] with a file name that equals the name of the [https://www.moonlightdesign.org/thunderforce/svn/trunk/extension/components/ XPCOM component] that the test suite tests. Each test suite is included in the test framework by being included as a <script/> line in [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/content/testrunner.xul testrunner.xul].

	==Running Tests==		==Running Tests==
			To run tests, [[Getting Started - Developer#Eclipse configurations for running and debugging Thunderforce\|create the Eclipse run configurations for tests]] and then run those. Those configurations use the "-thunderforceTest Label" command line option in the Thunderforce testing extension to run basic, normal, extra, or all tests. By default, running with the -thunderforceTest option prevents Thunderbird's main user interface from being displayed, but it's possible to force Thunderbird to show with the -thunderforceRunThunderbird command line option. The [https://www.moonlightdesign.org/thunderforce/svn/trunk/tests/components/nsThunderforceTestCommandLine.js nsThunderforceTestCommandLine.js] file handles the command line options for Thunderforce testing.

	==~~Adding~~ Tests==		==Creating Tests==
			'''being written...'''

Stevenlawrance: New page: Thunderforce's test framework uses XULRunner for both unit and integration testing. ==Test Architecture - Deployment View== ==Running Tests== ==Adding Tests==

2007-08-12T20:51:52Z

New page: Thunderforce's test framework uses XULRunner for both unit and integration testing. ==Test Architecture - Deployment View== ==Running Tests== ==Adding Tests==

New page

Thunderforce's test framework uses XULRunner for both unit and integration testing.

==Test Architecture - Deployment View==

==Running Tests==

==Adding Tests==