BDD Testing for the Schulcloud-Verbund

Available Tests

name	description
adminLogin	tests the login with an admin account
teacherLogin	tests the login with a teacher account
pupilLogin	tests the login with a pupil account
wrongPasswordLogin	tests the login with a wrong password

Installation

First you need to setup and start a local version of Schulcloud-Verbund Software & a database. This is the project against we run all the tests

# install all direct dependencies
npm i

Database seeding

During test execution the servers database will be resetted before test execution. For this, start the server management api in schulcloud-server using npm run nest:start:management. This application then will call http://localhost:3333/api/management/database/seed to reset the database.

Usage

# run the selenium driver in an extra command line
npm run selenium

# run all tests
npm run test
# or run a specific test
npm run test -- -t @teacherLogin

Options

Environment Variables

key	description
IT_CLIENT_URL	URL where the schulcloud-client is running.

Command Line Parameters

-h, --help                   output usage information
-v, --version                output the version number
-s, --steps <path>           path to step definitions. defaults to ./step-definitions
-p, --pageObjects <path>     path to page objects. defaults to ./page-objects
-o, --sharedObjects [paths]  path to shared objects - repeatable. defaults to ./shared-objects
-b, --browser <path>         name of browser to use. defaults to chrome
-r, --reports <path>         output path to save reports. defaults to ./reports
-d, --disableTestReport [optional]  disables the test report from opening after test completion
-t, --tags <tagName>         name of tag to run
-c, --context <path>        contextual root path for project-specific features, steps, objects etc
-f, --featuresPath <path>   path to feature definitions. defaults to ./features
-e, --email [optional]      sends email reports to stakeholders
-n, --environment [<path>]  name of environment to run the framework/test in. default to dev
-g, --reportName [optional] basename for report files e.g. use report for report.json
-u, --updateBaselineImage [optional] automatically update the baseline image after a failed comparison
-x, --extraSettings [optional]  further piped configs split with pipes
-w, --remoteService [optional]  which remote driver service, if any, should be used e.g. browserstack
-k, --keepOpenOnError       keeps the browser window open, when an error occurs

By default tests are run using Google Chrome, to run tests using another browser supply the name of that browser along with the -b switch. Available options are:

Browser	Example
Chrome	-b chrome
Firefox	-b firefox

Inside Test Cases

The following variables are available within the Given(), When() and () functions:

| Variable | Description | | :------------ | :--------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | driver | an instance of web driver (the browser) | | webdriverio | the raw webdriver module, providing access to static properties/methods | | page | collection of page objects loaded from disk and keyed by filename | | shared | collection of shared objects loaded from disk and keyed by filename | | helpers | a collection of helper methods things webdriver.io does not provide but really should! | | expect | instance of chai expect to expect('something').to.equal('something') | | assert | instance of chai assert to assert.isOk('everything', 'everything is ok') | | trace | handy trace method to log console output with increased visibility | | fs | exposes fs (file system) for use globally | | dir | exposes dir for getting an array of files, subdirectories or both | | request | exposes the request-promise for API testing | use for making API calls | | date | exposes the date method for logs and reports | | log | exposes the log method for output to files and emailing | | envConfig | exposes the global environment configuration file | for use when changing environment types (i.e. dev, test, preprod) |

Visual Regression functionality with Resemble JS

Visual regression testing, gives the ability to take and compare whole page screenshots or of specific parts of the application / page under test. If there are Elements in the page that contain dynamic contents (like a clock or something like tipp of the day), you can hide this elements before taking the screenshot by passing the selector (or an array of selectors) to the saveScreenshot function.

// ./runtime/imageCompare.js

compareImage: async function (fileName) {
  const verify = require('./imageCompare');
  await verify.assertion(fileName);
  await verify.value();
  await verify.pass();
}

// usage within page-object file:
  await verify.saveScreenshot(fileName);
  await helpers.compareImage(fileName);

Reports

HTML and JSON reports are automatically generated and stored in the default ./reports folder. This location can be changed by providing a new path using the -r command line switch:

Event handlers

You can register event handlers for the following events within the cucumber lifecycle.

const {After, Before, AfterAll, BeforeAll} = require('@cucumber/cucumber');

Event	Example
Before	Before(function() { // This hook will be executed before all scenarios})
After	After(function() {// This hook will be executed after all scenarios});
BeforeAll	BeforeAll(function() {// perform some shared setup});
AfterAll	AfterAll(function() {// perform some shared teardown});

How to debug

Most webdriverio methods return a JavaScript Promise that is resolved when the method completes. The easiest way to step in with a debugger is to add a .then method to a selenium function and place a debugger statement within it, for example:

When(/^I search DuckDuckGo for "([^"]*)"$/, function (searchQuery, done) {
	driver
		.element('#search_form_input_homepage')
		.then(function (input) {
			expect(input).to.exist;
			debugger; // <<- your IDE should step in at this point, with the browser open
			return input;
		})
		.then(function (input) {
			input.setValue(selector, searchQuery);
			input.setValue(selector, 'Enter');

			done(); // <<- let cucumber know you're done
		});
});

Default directory structure

You can use the framework without any command line arguments if your application uses the following folder structure:

.
├── features
│   └── duckDuckGo-search.feature
├── step_definitions
│   └── duckDuckGo-search-steps.js
├── page-objects
│   └── duckDuckGoSearch.js
|__ runtime
|   |__ world.js
└── shared-objects
│   ├── test-data.js
└── reports
    ├── cucumber-report.json
    └── cucumber-report.html

Bugs

Please raise framework related bugs via the klassi-js issue tracker and, if possible, please provide enough information to allow the bug to be reproduced.

Contributing to the framework

Anyone can contribute to this project simply by opening an issue here or fork the project and issue a pull request with suggested improvements. In lieu of a formal styleguide, please take care to maintain the existing coding style.

Credits for the testing framework

John Doherty

License

Apache License © 2019 Larry Goddard