Merge pull request #206 from bugsnag/tms/maze-v10

Use Maze Runner v10

Author: twometresteve

.buildkite/unity.2020.full.yml

@@ -12,9 +12,8 @@ steps:
         key: build-macos-fixture-2020
         depends_on: build-artifacts
         agents:
-          queue: macos-14
+          queue: macos-14-2
         env:
-          XCODE_VERSION: 15.3.0
           UNITY_PERFORMANCE_VERSION: *2020
         plugins:
           'artifacts#v1.9.0':
@@ -45,7 +44,7 @@ steps:
               - upm-package.zip
             upload:
               - features/fixtures/mazerunner/build/Windows-2020.zip
-              - features/fixtures/build_windows.log
+              - build_windows.log
         commands:
           - features/scripts/import_package.sh --windows
           - features/scripts/build_windows.sh release
@@ -102,6 +101,7 @@ steps:
         timeout_in_minutes: 10
         key: build-ios-fixture-2020
         depends_on: generate-fixture-project-2020
+        # macOS 14 used here due to build issues specifically for iOS/Unity 2020 in macOS 15
         agents:
           queue: macos-14-isolated
         env:

.buildkite/unity.2021.yml

@@ -42,7 +42,7 @@ steps:
               - upm-package.zip
             upload:
               - features/fixtures/mazerunner/build/Windows-2021.zip
-              - features/fixtures/build_windows.log
+              - build_windows.log
         commands:
           - features/scripts/import_package.sh --windows
           - features/scripts/build_windows.sh release

.buildkite/unity.2022.full.yml

@@ -42,7 +42,7 @@ steps:
               - upm-package.zip
             upload:
               - features/fixtures/mazerunner/build/Windows-2022.zip
-              - features/fixtures/build_windows.log
+              - build_windows.log
         commands:
           - features/scripts/import_package.sh --windows
           - features/scripts/build_windows.sh release

.buildkite/unity.6000.full.yml

@@ -42,7 +42,7 @@ steps:
               - upm-package.zip
             upload:
               - features/fixtures/mazerunner/build/Windows-6000.zip
-              - features/fixtures/build_windows.log
+              - build_windows.log
         commands:
           - features/scripts/import_package.sh --windows
           - features/scripts/build_windows.sh release

.gitignore

@@ -32,3 +32,6 @@ features/fixtures/mazerunner/Assets/Bugsnag
 features/fixtures/mazerunner/.vscode
 .DS_Store
 maze_output.zip
+maze_output/
+bugsnag-unity-performance.iml
+.idea/

Gemfile

@@ -6,7 +6,7 @@ gem 'danger'
 
 unless Gem.win_platform?
   # Use official Maze Runner release
-  gem 'bugsnag-maze-runner', '~> 9.0'
+  gem 'bugsnag-maze-runner', '~> 10.0'
 
   # Use a specific Maze Runner branch
   #gem 'bugsnag-maze-runner', git: 'https://github.com/bugsnag/maze-runner', branch: 'master'

docker-compose.yml

@@ -2,7 +2,7 @@ version: '3.6'
 services:
 
   maze-runner:
-    image: 855461928731.dkr.ecr.us-west-1.amazonaws.com/maze-runner-releases:latest-v9-cli
+    image: 855461928731.dkr.ecr.us-west-1.amazonaws.com/maze-runner-releases:latest-v10-cli
     environment:
       DEBUG:
       BUILDKITE:

features/app_start_spans.feature

@@ -5,7 +5,7 @@ Feature: App Start
 
   Scenario: Full App Start
     When I run the game in the "AppStartFull" state
-    And I wait for 4 spans
+    And I wait to receive at least 4 spans
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Sent-At" header matches the regex "^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d\.\d\d\dZ$"
@@ -29,7 +29,7 @@ Feature: App Start
 
 Scenario: App Start Start Only
     When I run the game in the "AppStartStartOnly" state
-    And I wait for 4 spans
+    And I wait to receive at least 4 spans
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Sent-At" header matches the regex "^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d\.\d\d\dZ$"
@@ -51,23 +51,23 @@ Scenario: App Start Start Only
 
 Scenario: App Start Off
     When I run the game in the "AppStartOff" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Span-Sampling" header equals "1:1"
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "AppStartOff"
 
 Scenario: App Start Customisation
     When I run the game in the "AppStartCustomisation" state
-    And I wait for 4 spans
+    And I wait to receive at least 4 spans
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Span-Sampling" header equals "1:4"
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.3.name" equals "[AppStart/UnityRuntime]ColdStart"
 
 Scenario: App Start Clear Customisation
     When I run the game in the "AppStartClearCustomisation" state
-    And I wait for 4 spans
+    And I wait to receive at least 4 spans
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Span-Sampling" header equals "1:4"

features/callbacks.feature

@@ -5,7 +5,7 @@ Feature: Custom Attributes
 
   Scenario: Callback Smoke Tests
     When I run the game in the "CallbackSmokeTests" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
     * the trace "Bugsnag-Sent-At" header matches the regex "^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d\.\d\d\dZ$"

features/configuration.feature

@@ -5,7 +5,7 @@ Feature: Configuration tests
 
   Scenario: Custom Release Stage
     When I run the game in the "CustomReleaseStage" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace "Bugsnag-Sent-At" header matches the regex "^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d\.\d\d\dZ$"
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
@@ -14,7 +14,7 @@ Feature: Configuration tests
 
   Scenario: Enabled Release Stage
     When I run the game in the "EnabledReleaseStages" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace "Bugsnag-Sent-At" header matches the regex "^\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\d\.\d\d\dZ$"
     And the trace "Bugsnag-Api-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
@@ -37,31 +37,31 @@ Feature: Configuration tests
 
   Scenario: App Version
     When I run the game in the "AppVersion" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "AppVersion"
     * the trace payload field "resourceSpans.0.resource" string attribute "service.version" equals "1.2.3_AppVersion"
 
   @cocoa_only
   Scenario: Bundle Version
     When I run the game in the "BundleVersion" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "BundleVersion"
     * the trace payload field "resourceSpans.0.resource" string attribute "bugsnag.app.bundle_version" equals "1.2.3_BundleVersion"
 
   @android_only
   Scenario: Android Specifics
     When I run the game in the "VersionCode" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "VersionCode"
     * the trace payload field "resourceSpans.0.resource" string attribute "bugsnag.app.version_code" equals "123"
     * the trace payload field "resourceSpans.0.resource" string attribute "bugsnag.device.android_api_version" exists
 
   Scenario: Custom Service Name
     When I run the game in the "CustomServiceName" state
-    And I wait for 1 span
+    And I wait to receive at least 1 span
     Then the trace Bugsnag-Integrity header is valid
     * the trace payload field "resourceSpans.0.scopeSpans.0.spans.0.name" equals "CustomServiceName"
     * the trace payload field "resourceSpans.0.resource" string attribute "service.name" equals "custom.service.name"