Files
alfresco-ng2-components/lib/testing
Alfresco Build 6704d68bae Update branch for JS-API PR#134 (#7638)
* [ci:force][auto-commit] Update JS-API to 4.11.0-134 for branch: update-js-api originated from JS-API PR: 134

* [ci:force][auto-commit] Update JS-API to 4.11.0-136 for branch: update-js-api originated from JS-API PR: 136

* [ci:force][auto-commit] Update JS-API to 4.11.0-137 for branch: update-js-api originated from JS-API PR: 137

* [ci:force][auto-commit] Update JS-API to 4.11.0-138 for branch: update-js-api originated from JS-API PR: 138

* [ci:force][auto-commit] Update JS-API to 4.11.0-138 for branch: update-js-api originated from JS-API PR: 139

* [ci:force][auto-commit] Update JS-API to 4.11.0-140 for branch: update-js-api originated from JS-API PR: 140

* [ci:force][auto-commit] Update JS-API to 4.11.0-142 for branch: update-js-api originated from JS-API PR: 142

* [ci:force][auto-commit] Update JS-API to 4.11.0-144 for branch: update-js-api originated from JS-API PR: 144

* [ci:force][auto-commit] Update JS-API to 4.11.0-145 for branch: update-js-api originated from JS-API PR: 145

* [ci:force][auto-commit] Update JS-API to 4.11.0-146 for branch: update-js-api originated from JS-API PR: 146

* [ci:force][auto-commit] Update JS-API to 4.11.0-147 for branch: update-js-api originated from JS-API PR: 147

* [ci:force][auto-commit] Update JS-API to 4.11.0-148 for branch: update-js-api originated from JS-API PR: 148

* [ci:force][auto-commit] Update JS-API to 4.11.0-149 for branch: update-js-api originated from JS-API PR: 149

* [ci:force][auto-commit] Update JS-API to 4.11.0-150 for branch: update-js-api originated from JS-API PR: 150

* [ci:force][auto-commit] Update JS-API to 4.11.0-154 for branch: update-js-api originated from JS-API PR: 154

* [ci:force][auto-commit] Update JS-API to 4.11.0-154 for branch: update-js-api originated from JS-API PR: 157

* [ci:force][auto-commit] Update JS-API to 4.11.0-158 for branch: update-js-api originated from JS-API PR: 158

* [ci:force][auto-commit] Update JS-API to 4.11.0-159 for branch: update-js-api originated from JS-API PR: 159

* [ci:force][auto-commit] Update JS-API to 4.11.0-161 for branch: update-js-api originated from JS-API PR: 161

* [ci:force][auto-commit] Update JS-API to 4.11.0-162 for branch: update-js-api originated from JS-API PR: 162

* [ci:force][auto-commit] Update JS-API to 4.11.0-163 for branch: update-js-api originated from JS-API PR: 163

* [ci:force][auto-commit] Update JS-API to 4.11.0-164 for branch: update-js-api originated from JS-API PR: 164

* [ci:force][auto-commit] Update JS-API to 4.11.0-165 for branch: update-js-api originated from JS-API PR: 165

* [ci:force][auto-commit] Update JS-API to 4.11.0-166 for branch: update-js-api originated from JS-API PR: 166

* [ci:force][auto-commit] Update JS-API to 4.11.0-167 for branch: update-js-api originated from JS-API PR: 167

* [ci:force][auto-commit] Update JS-API to 4.11.0-169 for branch: update-js-api originated from JS-API PR: 169
2022-06-13 09:33:02 +02:00
..
2021-06-19 23:03:17 +02:00

Alfresco Testing Library

Contains the reusable pages for e2e tests

Run e2e against a remote env using the .env.cloud file

Create a file .env.cloud under the e2e folder

HOST_BPM="https://gateway.example.com"
HOST_SSO="https://identity.example.com/auth/realms/alfresco"
URL_HOST_IDENTITY="https://identity.example.com/auth/admin/realms/alfresco"
IDENTITY_USERNAME_ADF="username"
IDENTITY_PASSWORD_ADF="password"

How can I run the cloud e2e against a remote env with chrome headless ?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh

FOLDER="process-services-cloud"
URL_HOST_ADF="http://myadf.example.com"
...

or ./scripts/test-e2e-lib.sh -host http://myadf.example.com -f process-services-cloud

How can I run the cloud e2e against a remote env with full chrome ?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh -env .env.cloud

BROWSER_RUN=true
FOLDER="process-services-cloud"
URL_HOST_ADF="http://myadf.example.co"
...

or ./scripts/test-e2e-lib.sh -host http://myadf.example.com -f process-services-cloud -b

How can I run specific specs agains a remote env?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh -env .env.cloud

LIST_SPECS="process-services-cloud/apps-section-cloud.e2e.ts,process-services-cloud/task-filters-cloud.e2e.ts"
URL_HOST_ADF="http://myadf.example.co"
...

or ./scripts/test-e2e-lib.sh -host http://myadf.example.com -s process-services-cloud/apps-section-cloud.e2e.ts,process-services-cloud/task-filters-cloud.e2e.ts

Run e2e against a local env (use dist) using the .env.cloud file

Create a file .env.cloud under the e2e folder

HOST_BPM="https://gateway.example.com"
HOST_SSO="https://identity.example.com/auth/realms/alfresco"
URL_HOST_IDENTITY="https://identity.example.com/auth/admin/realms/alfresco"
IDENTITY_USERNAME_ADF="username"
IDENTITY_PASSWORD_ADF="password"

How can I run the cloud e2e against a local env with chrome headless ?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh -ud -env .env.cloud

FOLDER="process-services-cloud"
URL_HOST_ADF="http://localhost:4200"
...

or ./scripts/test-e2e-lib.sh -ud -host http://localhost:4200 -f process-services-cloud

How can I run the cloud e2e against a local env with full chrome ?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh -ud -env .env.cloud

BROWSER_RUN=true
FOLDER="process-services-cloud"
URL_HOST_ADF="http://localhost:4200"
...

or ./scripts/test-e2e-lib.sh -ud -host http://localhost:4200 -f process-services-cloud -b

How can I run specific specs agains a local env?

Add to .env.cloud and run ./scripts/test-e2e-lib.sh -ud -env .env.cloud

LIST_SPECS="process-services-cloud/apps-section-cloud.e2e.ts,process-services-cloud/task-filters-cloud.e2e.ts"
URL_HOST_ADF="http://localhost:4200"
...

or ./scripts/test-e2e-lib.sh -ud -host http://localhost:4200 -s process-services-cloud/apps-section-cloud.e2e.ts,process-services-cloud/task-filters-cloud.e2e.ts