├── docs
├── manual
├── rest-tests
├── ui-tests
├── ui-tests-protractor
└── utilities
On-going initiative to provide comprehensive guide to current code structure.
BDD scenarios to be tested manually for now.
Java based tests that use Cucumber scenarios.
Test actions are executed directly to syndesis-rest
backend.
Java based tests that use Selenide and Cucumber BDD scenarios. Test actions are mainly UI driven with additional 3rd party validation like Salesforce, Twitter etc.
Typescript based tests that use Protractor and Cucumber BDD scenarios.
Circle CI job is configured to be executed on OpenShift Dedicated cluster, with configuration located in .circleci/config.yml
https://circleci.com/gh/syndesisio/syndesis-qe
Test scenarios are provided in Gherkin language in a BDD fashion. Located in ./resources
directory of *-tests
module, e.g. UI scenarios.
Every scenario is wrapped with appropriate tags to target specific execution on demand.
NOTE: Successful execution of tests requires fully configured credentials. All the callback URLs, Oauth tokens, etc. for Salesforce and Twitter accounts.
Placed to the root of syndesis-qe
directory.
test.properties
syndesis.config.openshift.url=https://192.168.64.2:8443
syndesis.config.openshift.token=<openshift-token>
syndesis.config.openshift.namespace=syndesis
syndesis.config.url.suffix=192.168.64.2.nip.io
syndesis.config.ui.url=https://syndesis.192.168.64.2.nip.io
syndesis.config.ui.username=developer
syndesis.config.ui.password=developer
credentials.json
{
"twitter_listen": {
"service": "twitter",
"properties": {
"screenName": "************",
"consumerKey": "*************************",
"consumerSecret": "**************************************************",
"accessToken": "**************************************************",
"accessTokenSecret": "*********************************************"
}
},
"twitter_talky": {
"service": "twitter",
"properties": {
"screenName": "************",
"consumerKey": "*************************",
"consumerSecret": "**************************************************",
"accessToken": "**************************************************",
"accessTokenSecret": "*********************************************"
}
},
"salesforce": {
"service": "salesforce",
"properties": {
"instanceUrl": "https://developer.salesforce.com",
"loginUrl": "https://login.salesforce.com",
"clientId": "*************************************************************************************",
"clientSecret": "*******************",
"userName": "**********************",
"password": "*********"
}
},
"s3": {
"service": "s3",
"properties": {
"region": "********",
"accessKey": "********************",
"secretKey": "*****************************************"
}
},
"ftp": {
"service": "ftp",
"properties": {
"binary": "Yes",
"connectTimeout": "10000",
"disconnect": "No",
"host": "ftpd",
"maximumReconnectAttempts": "3",
"passiveMode": "Yes",
"password": "",
"port": "2121",
"reconnectDelay": "1000",
"timeout": "30000",
"username": "anonymous"
}
},
"QE Dropbox": {
"service": "dropbox",
"properties": {
"accessToken": "**************",
"clientIdentifier": "**************"
}
}
}
for ftp connection credentials: All values are just examples / proposals. Need to be updated in accordance with
For the test execution at least syndesis-rest
modules are required in current SNAPSHOT version.
cd <syndesis-project-dir>
./syndesis/tools/bin/syndesis build --init --batch-mode --backend --flash
There're three Maven profiles: all, rest, ui
to target the specific test suite.
mvn clean test // default all profile
mvn clean test -P ui
mvn clean test -P rest
mvn clean test -P ui -Dcucumber.options="--tags @integrations-sf-db-test"