Difference between revisions of "AppSuite:RunTests"

(Libraries)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
<!-- !!! -->
 +
<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
 +
<!-- !!! -->
 +
 
{{Stability-experimental}}
 
{{Stability-experimental}}
 
<div class="title">Running the ui tests</div>
 
<div class="title">Running the ui tests</div>
Line 15: Line 19:
 
== Setting up your system ==
 
== Setting up your system ==
  
You need at least ''node'' version 0.8 to use the latest version of ''karma'', which we need. To install the (latest stable version of) karma runner, run
+
=== Before starting: Mac only ===
 +
  brew install phantomjs
 +
...or link it in path and set executable bit on phantomjs binary yourself. After this follow the rest of the guide.
  
    npm install -g karma
+
=== All ===
 +
You need at least ''node'' version 0.8 to use the latest version of ''karma'', which we need. Karma will be installed with all other development dependencies. So just make sure you ran
  
in a shell. You might need admin rights to do that, use ''sudo'' if needed.
+
    npm install
  
If you have karma installed already you may have to run
+
within your ui directory in the appsuite repository.
  
    npm -g update
+
== Running the tests ==
 
 
at least once, if the karma dependencies fail at least 2 times.
 
  
After that you may have to add the path to your node modules to the ''local.conf'' file.
+
The recommended way to start testing is to run:
  
    export NODE_PATH="/usr/local/lib/node_modules:/usr/local/share/npm/lib/node_modules:$NODE_PATH"
+
  grunt dev
  
== Running the tests ==
+
This will start a connect server, the karma
 +
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:
  
Running the tests is pretty easy. For now, in the ''ui'' directory of your sources start the karma server with this jake task
+
  grunt testrun
  
    ./build.sh testserver
+
in another terminal. This will be done automatically by the grunt watch
 +
task, after any source file of your project has been changed.
  
After that, open up a browser and point it to http://localhost:9876/.
 
  
If you don’t want to use the appserver proxy but your own backend, you need to adjust the proxies section in your ''ui/karma.conf.js''. The appserver or a running backend won’t be needed in the future.
 
  
 
[[Category:AppSuite]]
 
[[Category:AppSuite]]
 
[[Category:UI]]
 
[[Category:UI]]
 
[[Category:Development process]]
 
[[Category:Development process]]
 +
[[Category:Testing]]

Latest revision as of 08:39, 11 February 2016


API status: In Development

Running the ui tests

This article explains the test system of the frontend. It is aimed at developers that want to work with the frontend, be it creating new plugins or applications or modifying existing code using BDD. Bringing a BDD testing infrastructure to the frontend is still a work in progress and subject to (breaking) changes. Please contribute to the stability by reporting any issues or ideas to me.

Libraries

Setting up your system

Before starting: Mac only

  brew install phantomjs

...or link it in path and set executable bit on phantomjs binary yourself. After this follow the rest of the guide.

All

You need at least node version 0.8 to use the latest version of karma, which we need. Karma will be installed with all other development dependencies. So just make sure you ran

   npm install

within your ui directory in the appsuite repository.

Running the tests

The recommended way to start testing is to run:

 grunt dev

This will start a connect server, the karma 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

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