Configurations sets

[ikalinin1]

In order to simplify the management of multiple configuration sets in the same project, we need to introduce a mechanism to 'switch' active configuration.

For an example currently it could be solved via comments:

configuration.properties

## Android/Staging/Smoke
configuration.profiles=mobile_app/android
configuration.environments=staging
configuration.suites=smoke

## iOS/Regression/Prod
#configuration.profiles=mobile_app/ios
#configuration.environments=prod
#configuration.suites=regression

To simplify this we might support 'active' configuraiton

configuration-android-smoke-staging.properties

configuration.profiles=mobile_app/android
configuration.environments=staging
configuration.suites=smoke

configuration-ios-regression-prod.properties

configuration.profiles=mobile_app/ios
configuration.environments=prod
configuration.suites=regression

User will specify via test run arguments active configuration file, for example, ios-regression-prod will point VIVIDUS to load configuration-ios-regression-prod.properties configuration file.

[ikalinin1]

configuration-set.active=android-staging-smoke

Android/Staging/Smoke

configuration-set.android-staging-smoke.profiles=mobile_app/android
configuration-set.android-staging-smoke.environments=staging
configuration-set.android-staging-smoke.suites=smoke

iOS/Regression/Prod

configuration-set.ios-regression-prod.profiles=mobile_app/ios
configuration-set.ios-regression-prod.environments=prod
configuration-set.ios-regression-prod.suites=regression