AppSuite:Testing 3rd-party code - Revision history

Khgras at 09:20, 22 May 2017

2017-05-22T09:20:12Z

← Older revision		Revision as of 09:20, 22 May 2017
Line 18:		Line 18:
	== using karma-ox-ui ==		== using karma-ox-ui ==

	The [~~[AppSuite~~:~~GettingStarted_7~~.6.0\|shared grunt configuration]] ships with most of the parts pre-configured. Still, a little setup is needed to enable automatic testing for an external app. Since we use many standard libraries, this approach can be extended as you wish.		The [https://documentation.open-xchange.com/latest/ui/customize/app/first-app.html shared grunt configuration] ships with most of the parts pre-configured. Still, a little setup is needed to enable automatic testing for an external app. Since we use many standard libraries, this approach can be extended as you wish.

	=== Setup ===		=== Setup ===

2016-02-11T08:46:22Z

← Older revision		Revision as of 08:46, 11 February 2016
Line 1:		Line 1:
			<!-- !!! -->
			<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
			<!-- !!! -->

	<div class="title">Testing 3rd-party code</div>		<div class="title">Testing 3rd-party code</div>

2014-07-29T09:16:06Z

Added section on jshint

@@ Line 116: / Line 116: @@
 });
 </pre>
 === Running the tests ===

2014-07-25T09:04:42Z

Running the tests

← Older revision		Revision as of 09:04, 25 July 2014
Line 121:		Line 121:
	There are multiple targets provided in		There are multiple targets provided in
	[https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration].		[https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration].
	The recommended way is to run:
			The <tt>grunt/local.conf.json</tt> needs to be configured and point to an existing build of the core UI (coreDir setting). When testing on a machine with the core UI installed from distribution packages, also the German translations need to be installed to run the tests. After that, coreDir can be set to <tt>/opt/open-xchange/appsuite/</tt>.

			The recommended way to start testing is to run:

	grunt dev		grunt dev

	This will start a connect server, the karma		This will start a connect server, the karma
	test server and a watcher for changes. You can trigger a ~~testrun~~ manually by running:		test server and a watcher for changes. Optionally, it is possible to connect multiple browsers to the host running the karma server (port 9876). Tests will run in those browsers, too. You can trigger a test run manually by running:

	grunt testrun		grunt testrun

2014-07-18T08:19:54Z

Matthias.biggeleben moved page AppSuite:TestingUIPlugins to AppSuite:Testing 3rd-party code: Better reflects target audience

← Older revision	Revision as of 08:19, 18 July 2014
(No difference)

2014-07-18T08:18:17Z

← Older revision		Revision as of 08:18, 18 July 2014
Line 1:		Line 1:
	<div class="title">Testing 3rd party code</div>		<div class="title">Testing 3rd-party code</div>

	__TOC__		__TOC__

2014-07-18T07:20:28Z

Running the tests

← Older revision		Revision as of 07:20, 18 July 2014
Line 128:		Line 128:
	test server and a watcher for changes. You can trigger a testrun manually by running:		test server and a watcher for changes. You can trigger a testrun manually by running:

	grunt testrun		grunt testrun

	in another terminal. This will be done automatically by the grunt watch		in another terminal. This will be done automatically by the grunt watch

2014-07-18T07:20:19Z

← Older revision		Revision as of 07:20, 18 July 2014
Line 121:		Line 121:
	There are multiple targets provided in		There are multiple targets provided in
	[https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration].		[https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration].
	The recommended way is to run ~~<tt>~~grunt dev~~</tt>.~~ This will start a connect server, the karma		The recommended way is to run:
	test server and a watcher for changes. You can trigger a testrun manually by running
	~~<tt>~~grunt testrun~~</tt>~~ in another terminal. This will be done automatically by the grunt watch		grunt dev

			This will start a connect server, the karma
			test server and a watcher for changes. You can trigger a testrun manually by running:

			grunt testrun

			in another terminal. This will be done automatically by the grunt watch
	task, after any source file of your project has been changed.		task, after any source file of your project has been changed.

2014-07-18T07:18:31Z

Setup

← Older revision		Revision as of 07:18, 18 July 2014
Line 28:		Line 28:
	After that, in your plugin directory generate a new karma.conf.js:		After that, in your plugin directory generate a new karma.conf.js:

	~~jb@wiggum ~/code/appsuite/ox_pgp_mail (git)-[karma] % karma init~~

	~~Which testing framework do you want to use ?~~
	~~Press tab to list possible options. Enter to move to the next question.~~
	~~> mocha~~

	~~Do you want to use Require.js ?~~
	~~This will add Require.js plugin.~~
	~~Press tab to list possible options. Enter to move to the next question.~~
	~~> no~~

	~~Do you want to capture any browsers automatically ?~~
	~~Press tab to list possible options. Enter empty string to move to the next question.~~
	>

	~~What is the location of your source and test files ?~~
	~~You can use glob patterns, eg. "js/.js" or "test//Spec.js".~~
	~~Enter empty string to move to the next question.~~
	>

	jb@wiggum ~/code/appsuite/ox_pgp_mail (git)-[ding] % karma init		jb@wiggum ~/code/appsuite/ox_pgp_mail (git)-[ding] % karma init

2014-07-18T07:17:01Z

← Older revision		Revision as of 07:17, 18 July 2014
Line 1:		Line 1:
	<div class="title">Testing ~~UI plugins~~</div>		<div class="title">Testing 3rd party code</div>

	__TOC__		__TOC__