run e2e tests over https

Dan Skinner · Dan Skinner · commit 99b22a6f8957 · 2024-11-25T16:19:40.000Z
diff --git a/test/browser/features/angular.feature b/test/browser/features/angular.feature
@@ -5,7 +5,7 @@
 Feature: Angular
 
     Scenario: Angular route change spans are automatically instrumented
-        Given I navigate to the test URL "/angular/dist"
+        Given I navigate to the test URL "/docs/angular/dist"
         And the element "customers" is present
         And I click the element "customers"
         When I wait to receive 1 trace
@@ -25,7 +25,7 @@ Feature: Angular
             | bugsnag.browser.page.route_change.trigger | stringValue  | imperative             |
 
     Scenario: Route with a custom URL matcher
-        Given I navigate to the test URL "/angular/dist"
+        Given I navigate to the test URL "/docs/angular/dist"
         And the element "customMatching" is present
         And I click the element "customMatching"
         When I wait to receive 1 trace
diff --git a/test/browser/features/custom-attributes.feature b/test/browser/features/custom-attributes.feature
@@ -1,7 +1,7 @@
 Feature: Custom attributes
 
     Scenario: Custom attributes can be added to spans
-        Given I navigate to the test URL "/custom-attributes"
+        Given I navigate to the test URL "/docs/custom-attributes"
         And I wait for 1 span
 
         Then a span named "Custom/CustomAttributesScenario" contains the attributes: 
diff --git a/test/browser/features/device-id.feature b/test/browser/features/device-id.feature
@@ -2,7 +2,7 @@ Feature: Device ID persistence
 
   Scenario: persisted device ID is used if present
     # load the page and persist an ID
-    Given I navigate to the test URL "/retry-scenario"
+    Given I navigate to the test URL "/docs/retry-scenario"
     And I wait to receive a sampling request
     And I store the device ID "c1234567890abcdefghijklmnop"
 
diff --git a/test/browser/features/enabled-release-stages.feature b/test/browser/features/enabled-release-stages.feature
@@ -1,11 +1,11 @@
 Feature: Configuration
 
   Scenario: Delivery is prevented when releaseStage is not in enabledReleaseStages
-    Given I navigate to the test URL "/enabled-release-stages-disabled"
+    Given I navigate to the test URL "/docs/enabled-release-stages-disabled"
     Then I should receive no traces
 
   Scenario: Delivery is allowed when releaseStage is present in enabledReleaseStages
-    Given I navigate to the test URL "/enabled-release-stages"
+    Given I navigate to the test URL "/docs/enabled-release-stages"
     And I wait to receive at least 1 trace
     Then the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "Custom/Should send"
     And the trace payload field "resourceSpans.0.resource" string attribute "deployment.environment" equals "test"
diff --git a/test/browser/features/error-correlation.feature b/test/browser/features/error-correlation.feature
@@ -1,15 +1,15 @@
 Feature: Error Correlation
 
   Scenario: Error does not include the correlation property when no spans are open
-    Given I navigate to the test URL "/error-correlation"
+    Given I navigate to the test URL "/docs/error-correlation"
     And I wait to receive a sampling request
     And I click the element "send-error"
     And I wait to receive an error
     Then the error is a valid browser payload for the error reporting API
     And the error payload field "events.0.correlation" is null
 
   Scenario: Reported errors include the current trace and span id
-    Given I navigate to the test URL "/error-correlation"
+    Given I navigate to the test URL "/docs/error-correlation"
     And I wait to receive a sampling request
     Then I click the element "start-span"
     And I wait for 1 second
@@ -33,7 +33,7 @@ Feature: Error Correlation
     And the error payload field "events.0.correlation.traceId" equals the stored value "traceId"
 
   Scenario: Reported errors do not include the trace and span id if the span is not the current context
-    Given I navigate to the test URL "/error-correlation"
+    Given I navigate to the test URL "/docs/error-correlation"
     And I wait to receive a sampling request
     Then I click the element "start-span"
     And I wait for 1 second
diff --git a/test/browser/features/fixed-sampling-probability.feature b/test/browser/features/fixed-sampling-probability.feature
@@ -1,7 +1,7 @@
 Feature: Fixed Sampling Probability
 
   Scenario: Uses configured sampling probability
-    Given I navigate to the test URL "/fixed-sampling-probability"
+    Given I navigate to the test URL "/docs/fixed-sampling-probability"
     And I enter unmanaged traces mode
     When I click the element "send-span"
     And I wait to receive 1 trace
diff --git a/test/browser/features/lib/url-generator.rb b/test/browser/features/lib/url-generator.rb
@@ -5,7 +5,7 @@ def initialize(maze_uri, fixtures_uri)
   end
 
   def for_path(path)
-    uri = URI.join(@maze_uri, "/docs#{path}")
+    uri = URI.join(@maze_uri, path)
     config_query_string = "endpoint=#{@maze_uri}/traces&logs=#{@maze_uri}/logs&api_key=#{$api_key}&notify=#{@maze_uri}/notify&sessions=#{@maze_uri}/sessions"
 
     if uri.query
diff --git a/test/browser/features/manual-spans.feature b/test/browser/features/manual-spans.feature
@@ -1,7 +1,7 @@
 Feature: Manual creation of spans
 
   Scenario: Manual spans can be logged
-    Given I navigate to the test URL "/manual-span"
+    Given I navigate to the test URL "/docs/manual-span"
     And I wait to receive a sampling request
     Then I click the element "send-span"
     And I wait for 1 span
@@ -23,7 +23,7 @@ Feature: Manual creation of spans
     And the trace payload field "resourceSpans.0.resource" string attribute "service.name" equals "manual-span"
 
   Scenario: isFirstClass span option can be set to false
-    Given I navigate to the test URL "/manual-span?isFirstClass=false"
+    Given I navigate to the test URL "/docs/manual-span?isFirstClass=false"
     And I wait to receive a sampling request
     Then I click the element "send-span"
     And I wait for 1 span
@@ -46,7 +46,7 @@ Feature: Manual creation of spans
 
   @chromium_only @local_only
   Scenario: userAgentData is included in custom span
-    Given I navigate to the test URL "/manual-span"
+    Given I navigate to the test URL "/docs/manual-span"
     And I wait to receive a sampling request
     When I click the element "send-span"
     And I wait for 1 span
@@ -62,7 +62,7 @@ Feature: Manual creation of spans
       | Unknown |
 
   Scenario: Spans can be logged before start
-    Given I navigate to the test URL "/pre-start-spans"
+    Given I navigate to the test URL "/docs/pre-start-spans"
     When I wait to receive at least 1 trace
     Then a span name equals "Custom/Post Start"
     And a span name equals "Custom/Pre Start Span 0"
diff --git a/test/browser/features/navigation-changes.feature b/test/browser/features/navigation-changes.feature
@@ -2,7 +2,7 @@
 Feature: Navigation changes
     @skip_span_time_validation
     Scenario: Batch is sent when navigating to a new page by clicking an anchor tag
-        Given I navigate to the test URL "/navigation-changes"
+        Given I navigate to the test URL "/docs/navigation-changes"
         When I click the element "add-span-to-batch"
         And I click the element "add-span-to-batch"
 
@@ -18,7 +18,7 @@ Feature: Navigation changes
 
     @skip_span_time_validation
     Scenario: Batch is sent when navigating to a new page by entering a new URL
-        Given I navigate to the test URL "/navigation-changes"
+        Given I navigate to the test URL "/docs/navigation-changes"
         When I click the element "add-span-to-batch"
         And I click the element "add-span-to-batch"
         And I click the element "add-span-to-batch"
@@ -36,7 +36,7 @@ Feature: Navigation changes
 
     @minimises_window
     Scenario: Batch is sent when the window is minimised
-        Given I navigate to the test URL "/navigation-changes"
+        Given I navigate to the test URL "/docs/navigation-changes"
         When I click the element "add-span-to-batch"
         And I click the element "add-span-to-batch"
         And I click the element "add-span-to-batch"
diff --git a/test/browser/features/nested-spans.feature b/test/browser/features/nested-spans.feature
@@ -1,7 +1,7 @@
 Feature: Nested spans
 
   Scenario: Spans are nested under the correct parent context
-    Given I navigate to the test URL "/nested-spans"
+    Given I navigate to the test URL "/docs/nested-spans"
     And I wait for 5 spans
 
     # Root span should have no parent
diff --git a/test/browser/features/network-spans.feature b/test/browser/features/network-spans.feature
@@ -1,7 +1,7 @@
 Feature: Network spans
 
     Scenario: Manual network spans
-        Given I navigate to the test URL "/manual-span"
+        Given I navigate to the test URL "/docs/manual-span"
         When I click the element "send-network-span"
         And I wait to receive 1 trace
 
@@ -14,7 +14,7 @@ Feature: Network spans
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" integer attribute "http.status_code" equals 200
 
     Scenario: Network spans are automatically instrumented for completed XHR requests
-        Given I navigate to the test URL "/network-spans"
+        Given I navigate to the test URL "/docs/network-spans"
         When I click the element "xhr-success"
         And I wait to receive 1 trace
 
@@ -23,11 +23,11 @@ Feature: Network spans
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "bugsnag.browser.page.title" equals "Network spans"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "bugsnag.browser.page.url" equals the stored value "bugsnag.browser.page.url"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.method" equals "GET"
-        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^https:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0$"
+        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^http(s)?:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0$"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" integer attribute "http.status_code" equals 200
 
     Scenario: Network spans are automatically instrumented for completed fetch requests
-        Given I navigate to the test URL "/network-spans"
+        Given I navigate to the test URL "/docs/network-spans"
         When I click the element "fetch-success"
         And I wait to receive 1 trace
 
@@ -36,40 +36,40 @@ Feature: Network spans
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "bugsnag.browser.page.title" equals "Network spans"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "bugsnag.browser.page.url" equals the stored value "bugsnag.browser.page.url"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.method" equals "GET"
-        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^https:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0$"
+        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^http(s)?:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0$"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" integer attribute "http.status_code" equals 200
 
     Scenario: Network spans are not instrumented for failed requests
-        Given I navigate to the test URL "/network-spans"
+        Given I navigate to the test URL "/docs/network-spans"
         When I click the element "failed-requests"
         Then I should have received no spans
 
     Scenario: Attributes can be modified by networkRequestCallback using fetch
-        Given I navigate to the test URL "/network-span-control"
+        Given I navigate to the test URL "/docs/network-span-control"
         When I click the element "fetch-modified-url"
         And I wait to receive 1 trace
         
         Then the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "[HTTP/GET]"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.method" equals "GET"
-        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^https:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0&not-your-ordinary-url=true$"
+        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^http(s)?:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0&not-your-ordinary-url=true$"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" integer attribute "http.status_code" equals 200
 
     Scenario: Attributes can be modified by networkRequestCallback using xhr
-        Given I navigate to the test URL "/network-span-control"
+        Given I navigate to the test URL "/docs/network-span-control"
         When I click the element "xhr-modified-url"
         And I wait to receive 1 trace
         
         Then the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "[HTTP/GET]"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.method" equals "GET"
-        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^https:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0&not-your-ordinary-url=true$"
+        And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" string attribute "http.url" matches the regex "^http(s)?:\/\/.+:\d{4}\/reflect\?status=200\&delay_ms=0&not-your-ordinary-url=true$"
         And the trace payload field "resourceSpans.0.scopeSpans.0.spans.0" integer attribute "http.status_code" equals 200
 
     Scenario: Delivery of spans can be prevented by networkRequestCallback using fetch
-        Given I navigate to the test URL "/network-span-control"
+        Given I navigate to the test URL "/docs/network-span-control"
         When I click the element "fetch-prevented"
         Then I should have received no spans
 
     Scenario: Delivery of spans can be prevented by networkRequestCallback using xhr
-        Given I navigate to the test URL "/network-span-control"
+        Given I navigate to the test URL "/docs/network-span-control"
         When I click the element "xhr-prevented"
         Then I should have received no spans
diff --git a/test/browser/features/page-load-spans.feature b/test/browser/features/page-load-spans.feature
@@ -1,7 +1,7 @@
 @requires_performance_navigation_timing
 Feature: Page Load spans
     Scenario: Page load spans are automatically instrumented
-        Given I navigate to the test URL "/page-load-spans"
+        Given I navigate to the test URL "/docs/page-load-spans"
         # click a button to record a first input delay metric
         And I click the element "stop-clock"
         And I wait to receive 1 trace
@@ -100,7 +100,7 @@ Feature: Page Load spans
             | bugsnag.phase                             | stringValue  | TLS                   |
 
     Scenario: Page load spans can have attributes dropped by sendPageAttributes config
-        Given I navigate to the test URL "/network-span-control"
+        Given I navigate to the test URL "/docs/network-span-control"
         When I click the element "page-load-no-attributes"
         And I wait to receive 1 trace
 
@@ -109,7 +109,7 @@ Feature: Page Load spans
         And a span named "[FullPageLoad]/docs/network-span-control/" does not contain the attribute "bugsnag.browser.page.referrer"
 
     Scenario: Page load spans inherit parent context from traceparent meta tag if present
-        Given I navigate to the test URL "/traceparent-meta"
+        Given I navigate to the test URL "/docs/traceparent-meta"
         And I wait to receive 1 trace
 
         Then a span named "[FullPageLoad]/docs/traceparent-meta/" has the following properties:
diff --git a/test/browser/features/react-router.feature b/test/browser/features/react-router.feature
@@ -4,7 +4,7 @@
 Feature: React router
 
     Scenario: React route change spans are automatically instrumented
-        Given I navigate to the test URL "/react-router"
+        Given I navigate to the test URL "/docs/react-router"
         And I click the element "change-route"
         When I wait to receive 1 span
         Then a span named "[RouteChange]/contacts/:contactId" contains the attributes: 
diff --git a/test/browser/features/resource-load-spans.feature b/test/browser/features/resource-load-spans.feature
@@ -25,7 +25,7 @@ Feature: Resource Load Spans
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1.name" matches the regex "^\[ResourceLoad\]https:\/\/.*:[0-9]{4}\/docs\/favicon.png$"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1.parentSpanId" equals the stored value "parent_span_id"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1" string attribute "bugsnag.span.category" equals "resource_load"
-    And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1" string attribute "http.url" matches the regex "^https:\/\/.*:[0-9]{4}\/docs\/favicon\.png\?height=100&width=100$"
+    And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1" string attribute "http.url" matches the regex "^http(s)?:\/\/.*:[0-9]{4}\/docs\/favicon\.png\?height=100&width=100$"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1" string attribute "http.flavor" equals "1.1"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.1" double attribute "bugsnag.sampling.p" equals 0.999999
 
@@ -61,6 +61,6 @@ Feature: Resource Load Spans
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2.name" matches the regex "^\[ResourceLoad\]https:\/\/.*:[0-9]{4}\/docs\/favicon.png$"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2.parentSpanId" equals the stored value "parent_span_id"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2" string attribute "bugsnag.span.category" equals "resource_load"
-    And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2" string attribute "http.url" matches the regex "^https:\/\/.*:[0-9]{4}\/docs\/favicon\.png\?height=100&width=100$"
+    And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2" string attribute "http.url" matches the regex "^http(s)?:\/\/.*:[0-9]{4}\/docs\/favicon\.png\?height=100&width=100$"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2" string attribute "http.flavor" equals "1.1"
     And the trace payload field "resourceSpans.0.scopeSpans.0.spans.2" double attribute "bugsnag.sampling.p" equals 0.999999
diff --git a/test/browser/features/retries.feature b/test/browser/features/retries.feature
@@ -1,7 +1,7 @@
 Feature: Retries
 
     Scenario Outline: Batch is retried with specified status codes
-        Given I navigate to the test URL "/retry-scenario"
+        Given I navigate to the test URL "/docs/retry-scenario"
         And I wait to receive a sampling request
         And I set the HTTP status code for the next "POST" request to <status>
         
@@ -29,7 +29,7 @@ Feature: Retries
             | 500    | Connection Error              |
 
     Scenario: Batch is retried with connection failure
-        Given I navigate to the test URL "/connection-failure"
+        Given I navigate to the test URL "/docs/connection-failure"
 
         When I click the element "send-span"
         And I wait for 10 seconds
@@ -42,7 +42,7 @@ Feature: Retries
         And a span name equals "Custom/Span 2"
 
     Scenario Outline: Batch is not retried with specified status codes
-        Given I navigate to the test URL "/retry-scenario"
+        Given I navigate to the test URL "/docs/retry-scenario"
         And I wait to receive a sampling request
         And I set the HTTP status code for the next "POST" request to <status>
         
@@ -66,7 +66,7 @@ Feature: Retries
     # Status code 408 cannot be tested on certain browsers as it
     # is automatically retried and does not behave as expected
     Scenario Outline: Oldest batch is removed when max retry queue size is exceeded
-        Given I navigate to the test URL "/oldest-batch-removed"
+        Given I navigate to the test URL "/docs/oldest-batch-removed"
         And I wait to receive a sampling request
         And I set the HTTP status code for the next 2 "POST" requests to <status>
 
diff --git a/test/browser/features/route-change-spans.feature b/test/browser/features/route-change-spans.feature
@@ -1,7 +1,7 @@
 Feature: Route change spans
 
     Scenario: Route change spans are automatically instrumented
-        Given I navigate to the test URL "/route-change-spans"
+        Given I navigate to the test URL "/docs/route-change-spans"
         And I click the element "change-route"
         When I wait to receive 1 trace
 
@@ -15,7 +15,7 @@ Feature: Route change spans
             | bugsnag.browser.page.route_change.trigger | stringValue  | pushState                                    |
 
     Scenario: Hyperlinks within a page
-        Given I navigate to the test URL "/route-change-spans"
+        Given I navigate to the test URL "/docs/route-change-spans"
         And I click the element "go-to-anchor"
         When I wait to receive 1 trace
 
diff --git a/test/browser/features/server-responses.feature b/test/browser/features/server-responses.feature
diff --git a/test/browser/features/span-batching.feature b/test/browser/features/span-batching.feature
diff --git a/test/browser/features/trace-propagation.feature b/test/browser/features/trace-propagation.feature
diff --git a/test/browser/features/vue-router.feature b/test/browser/features/vue-router.feature
