Add ability to use tunneling at story level#5890
Conversation
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
62a6d10 to
3ac28dc
Compare
3ac28dc to
e2afe28
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5890 +/- ##
============================================
- Coverage 97.74% 97.73% -0.01%
- Complexity 7226 7472 +246
============================================
Files 996 996
Lines 20993 20998 +5
Branches 1381 1381
============================================
+ Hits 20519 20522 +3
- Misses 363 364 +1
- Partials 111 112 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
e2afe28 to
0b2ceab
Compare
|
| a|Enables https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy[Sauce Connect Proxy] | ||
|
|
||
| The https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy[Sauce Connect Proxy] can also be enabled at story level by using `@tunnel` meta tag. |
There was a problem hiding this comment.
| a|Enables https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy[Sauce Connect Proxy] | |
| The https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy[Sauce Connect Proxy] can also be enabled at story level by using `@tunnel` meta tag. | |
| a|Enables https://docs.saucelabs.com/secure-connections/[Sauce Connect Proxy] | |
| https://docs.saucelabs.com/secure-connections/[Sauce Connect Proxy] can also be enabled at story level by using `@tunnel` meta tag. |
| getRunningStory().map(RunningStory::getName).ifPresent(testNameConsumer); | ||
| } | ||
|
|
||
| protected Optional<RunningStory> getRunningStory() |
There was a problem hiding this comment.
| protected Optional<RunningStory> getRunningStory() | |
| private Optional<RunningStory> getRunningStory() |
| protected abstract void setCapability(DesiredCapabilities capabilities, Meta meta); | ||
| protected void setCapability(DesiredCapabilities capabilities, Meta meta) | ||
| { | ||
| // Nothing to do |
There was a problem hiding this comment.
not a good default implementation, it's better to keep empty methods per enum entry
| public void configure(DesiredCapabilities desiredCapabilities) | ||
| { | ||
| Validate.isTrue(!hasControllingMetaTag(ControllingMetaTag.TUNNEL), | ||
| "ExecutionCloud doesn't support tunneling capabilities."); |
There was a problem hiding this comment.
| "ExecutionCloud doesn't support tunneling capabilities."); | |
| "ExecutionCloud does not support tunnelling"); |
| Validate.isTrue(!hasControllingMetaTag(ControllingMetaTag.TUNNEL), | ||
| "LambdaTest doesn't support tunneling capabilities."); |
There was a problem hiding this comment.
| Validate.isTrue(!hasControllingMetaTag(ControllingMetaTag.TUNNEL), | |
| "LambdaTest doesn't support tunneling capabilities."); | |
| Validate.isTrue(!hasControllingMetaTag(ControllingMetaTag.TUNNEL), | |
| "LambdaTest does not support tunnelling"); |
| for profile in "${profiles[@]}"; do | ||
| ./gradlew :vividus-tests:debugStories -Pvividus.configuration.environments=system/saucelabs \ | ||
| -Pvividus.configuration.suites=health_check \ | ||
| -Pvividus.configuration.suites=health_check/extended \ |
There was a problem hiding this comment.
no reason to check if tunnelling works for each browser, it's enough to have one browser only



No description provided.