Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Changes
Page history
Update Testing Guide
authored
May 10, 2022
by
Julian Rausch
Show whitespace changes
Inline
Side-by-side
Guidelines/Testing-Guide.md
View page @
febdddc2
...
...
@@ -51,6 +51,27 @@ For "legacy" tests (JUnit), the development team agreed on the following naming
-
Unit tests (classes under
```test```
) SHOULD end in "UnitTests".
-
Integration tests (classes under
```integration-test```
) SHOULD end in "Tests".
E2E with Cypress
----------------------------------------------------
### Getting Started ###
For starting Cypress Tests a cypress.env.json file is needed. This file should contain the following:
```
{
"operator_username": "otp",
"operator_password": "otp"
}
```
To define an individual baseUrl use the following command:
```
export CYPRESS_BASE_URL=https://localhost:8080```
All Cypress tests can be run with ```npm run cy:run```
For Individual testing and to use the gui run the command ```npm run cy:open```
Unit Testing (With Fake Objects)
--------------------------------
...
...
...
...