libreoffice-online/cypress_test
Tamás Zolnai 84f46074f9 cypress: start Xvfb with screen argument.
It fixes an error during cypress verify:
https://github.com/cypress-io/cypress/issues/6184

Change-Id: I993bf6cda5f8018d394ee6ee506f99d07b1e6e56
Reviewed-on: https://gerrit.libreoffice.org/c/online/+/93793
Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com>
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>
2020-05-10 12:45:28 +02:00
..
data cypress: add tests for form field button. 2020-05-10 01:47:26 +02:00
eslint_plugin cypress: add a custom ESLint rule against cy.get().contains() usage. 2020-04-28 18:42:56 +02:00
integration_tests cypress: add tests for form field button. 2020-05-10 01:47:26 +02:00
plugins cypress: integrate cypress-failed-log package. 2020-03-13 15:00:54 +01:00
support cypress: try to fix TypeError: cy.waitUntil is not a function. 2020-04-08 11:11:31 +02:00
.eslintignore cypress: Add node_modules to eslintignore 2020-01-24 09:30:48 +01:00
.eslintrc cypress: add a custom ESLint rule against cy.get().contains() usage. 2020-04-28 18:42:56 +02:00
.gitignore cypress: try to fix TypeError: cy.waitUntil is not a function. 2020-04-08 11:11:31 +02:00
cypress.json cypress: try to fix random "Uncaught SyntaxError" failures. 2020-04-09 12:31:04 +02:00
Makefile.am cypress: start Xvfb with screen argument. 2020-05-10 12:45:28 +02:00
package.json cypress: add a custom ESLint rule against cy.get().contains() usage. 2020-04-28 18:42:56 +02:00
README cypress: update README. 2020-03-20 12:45:23 +01:00
run_iteratively.sh cypress: add run_iteratively.sh for catching inconsistent test failures. 2020-04-10 13:37:48 +02:00

Cypress based test framework for LibreOffice Online
====================================================


Installation
------------------

You need to have run configure with the --enable-cypress option.

In a normal desktop environment you only need to install npm
packages for running cypress tests. This is done by the build
system, so running 'make check' will do the basic installation.
https://docs.cypress.io/guides/getting-started/installing-cypress.html#npm-install

For CI you might need to install some additional dependencies:
https://docs.cypress.io/guides/guides/continuous-integration.html#Dependencies


Running tests
------------------

All tests are part of the make check build. So you can
just execute it from the root folder or under the
cypress_test folder to run cypress tests only.

    make check

IMPORTANT: Before stepping under cypress_test folder
and running any command listed here, make sure you've
done a top-level make, so everything is up-to-date.
Running commands from under cypress_test folder won't
trigger a rebuild.

To run cypress test cases selectively, you need to
go in to the cypress_test folder first and run one of
the following commands.

To run all desktop tests:

    make check-desktop

To run all mobile tests:

    make check-mobile

To run one specific test suit of desktop tests,
use spec argument with a relative path to
cypress_test/integration_tests/desktop/:

    make check-desktop spec=example_desktop_test_spec.js

To run one specific test suit of mobile tests,
use spec argument with a relative path to
cypress_test/integration_tests/mobile/:

    make check-mobile spec=writer/toolbar_spec.js


Running one specific test
------------------

To run one test case of a test suit you can use Mocha's
'only' feature. Just replace the it(...) function with
it.only(...) in the spec file for the selected test case
and run the test suit using the spec parameter.

For example, to run the test with title 'Apply font name.'
inside apply_font_spec.js file, you need to add it.only():

-    it('Apply font name.', function() {
+    it.only('Apply font name.', function() {

Then run the test suit with:

    make check-mobile spec=writer/apply_font_spec.js

Or open the file in the interactive test runner.

    make run-mobile


Openning interactive test runner
----------------------------------

Cypress has an interactive test runner application which
runs the test in the browser. So you can see the result of
the different steps your test makes in the browser. It's useful
during writing new tests or checking why an existing
test fails.
https://docs.cypress.io/guides/core-concepts/test-runner.html

To open desktop tests in the test runner:

    make run-desktop

To open mobile tests in the test runner:

    make run-mobile

During the build we run the tests with Chrome browser, so make sure
you select Chrome browser on the GUI while checking tests.
We are using different configuration and environment variables for
mobile and desktop tests, that's why there are two separate commands
for them and there is no option to open all the tests in the
test runner.