- if tests should be run in phantomjs, it must be installed manually and must be included in the system PATH
- phantomjs 2.0 should be used instead of version 1.9.8
OSx download url: https://github.com/eugene1g/phantomjs/releases
- npm install -g bower gulp
- npm install
- bower install
- bundle install (in
cucumber
directory)
-
gulp build:xxx
to just compile app (xxx
can be eitherdev
,integration
,prod
) -
gulp dev
build app inbuild:dev
mode and run local dev server -
gulp dev:minified
built app inbuild:dev
with minified resources and run local dev server -
gulp integrate
build app inbuild:integration
mode with minified resources and run a local integration server (proxies ttm-itest, but uses files from the local maschine) -
gulp package:app
build app inbuild:prod
mode and package the application into one *.tar file which contains all relevant files for live deployment -
gulp package:cucumber
package all cucumber integration tests into one *.tar file -
gulp test:units
run unit tests and create code coverage report -
gulp test:integration:xxx
run integration tests on specified system (xxx
can be eitherlocal
,itest
,stag
,prod
)
General options:
-
gulp <task> --minified
minify css and js so that only 1 file per type is generated (automatically set fordev:minified
andintegrate
tasks)
Integration test options:
-
gulp <task> --browser=xxx
use specified browser to run integration tests (xxx
can be eitherchrome
,firefox
,safari
,phantomjs
),chrome
is used by default -
gulp <task> --feature=xxx
only use specified feature file to run integration tests (xxx
is the path to the feature file, cucumber synctax with line number is possible)
-
make sure, widgetloader is also available
-
place following html code somewhere on the page
<div class="tui-widget" data-widget="r-search" data-r-search></div>
This will render an
<input type="text">
with 100% width of the parent container.
Example: cucumber --tag @itest PROFILE=tui.com.itest BROWSER=chrome