Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
In Blueriq 12.8, we added the concept of Test Paths in order to be able to test multi-repository applications. These are applications that span multiple projects, by using Container type: AQ_Dashboard_ProjectWidget or Service call type: AQ_StartProject to start flows from different projects. One can imagine that when testing a feature branch of a project, you wouldn't want to have that same feature branch present in all other projects, especially when nothing has changed in those projects.
In Blueriq 12.9, we added support for test paths for Container type: AQ_ExternalFlow, Service call type: AQ_RestServiceClient and Service call type: AQ_SoapServiceClient.
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
When using this feature, keep the following in mind:
- Test Paths only work when the Runtime is in development mode
- Test Paths only work when using shortcuts to indicate the entry point of the project to start
- Test Paths only work for Studio projects, not for project exports or publisher exports.
When editing shortcuts, you can define Test Paths for that shortcut:
| Code Block | ||||
|---|---|---|---|---|
| ||||
blueriq.shortcut.ChildSupport.testPaths.feature1 = 0.0-FeatureBranch1
blueriq.shortcut.ChildSupport.testPaths.feature2 = 0.0-FeatureBranch2 |
This indicates that when the application is started with Test Path feature1, the project should use 0.0-FeatureBranch1 instead of the version indicated by blueriq.shortcut.ChildSupport.version.
If any Test Paths are configured, the development dashboard will display a selector for the Test Paths:
Selecting a Test Path will result in the following behavior:
- When the selected Test Path is defined for the shortcut, the corresponding version of the project is started instead of the default version.
- When the selected Test Path is not defined for the shortcut, the default version of the project is started.
- When the selected Test Path is defined, but the corresponding version doesn't exist in the project, an error is returned.
The selected Test Path will be propagated through the entire application, with the exception of AQ_SoapServiceClient/AQ_WebServiceClient and AQ_ExternalFlow.
The Test Path names, e.g. feature1 in the previous example, are identifiers that can be chosen freely (but limited to alphanumeric characters and underscores). You are encouraged to use Test Path names that describe the feature you are testing.
...
| Include Page | ||||
|---|---|---|---|---|
|
...
| Tip |
|---|
When working with shortcuts for the AQ_StartProject service, you need to think of security. On a production server you set the runtime to |
| UI Text Box | type |
|---|
| Info |
It is possible to leave the version of the application out of the URL or shortcut, in which case the latest version of the application is started. The latest version is determined as follows:
Example: 0.0-Wetwijziging
Since for all studio exports the major and minor version always are equal to 0, only the branch name is the discriminating factor. It is sorted in ascending order, meaning that a branch name starting with 'z' is considered later as a branch name starting with 'a'. In order to make effective use of this mechanism, we advice to use branch names which start with numbers, e.g. 001_4_FeatureBranch. |
| UI Text Box |
| Info | ||
|---|---|---|
It is possible to leave the name of the application out of the URL or shortcut, in which case the default application is started. The default application is determined by the Runtime, as being the shortcut that has the name 'default'.
|
...
Overview
Content Tools