- Ensure selenium related errors are always reported 706
- Fix issue where the incorrect
buildIdwas being pulled fromMaze.driver.session_capabilities707
- Catch AWS IP invalid response error and attempt to retry 704
- Add iOS 13,14 and 18 mobile browsers on BrowserStack 705
- Fix incorrect access of error captor class 703
- Removed deprecated safari 15 & 16 from BitBar configuration, added safari 17 & 18 701
- Handle failing appium session better 696
- Disable automatic attempts to acquire test device logs in appium scenarios 702
- Add extra guard for stopping running apps in case of remote server error 694
- Pin "uri" dependency to avoid v1.0.0 release bug 700
- Ignore system generated ANRs on Android 699
- Add Android 15 to the available BrowserStack devices 697
- Do not set
acceptInsecureCertscapability with IE 698
- Add https support for document servers 695
- Ensure all values are floating points before comparison 693
- Add support for iOS 18 on BrowserStack and remove deprecated devices 680
- Add dependencies for modules no longer present in Ruby standard lib for v3.3+ 678
- Fix issues with loading maze-runner commands from file 679
- Remove deprecated close_app usage 681
- Add the ability to override the
--fail-fastoption via an environment variable 674 - Add support for defining custom validation blocks in configuration
- Add client mode configuration option 677
- Add support for command line options files 676
- Repeat trace requests using the API key as the subdomain 670
- Add tool to find failed BitBar sessions and save them to a CSV file 665
- Add regex-based variants of steps for checking platform-dependent values 667
- Add better appium driver exits on server error 666
- Bump
curbdependency to 1.0.5 664
- Move iOS 15 BrowserStack tests from iPhone 11 Pro to iPhone 13 662
- Reinstate publishing of legacy CLI Docker image 663
- add support for comparing double and array attributes in spans 661
- Add Android 14 to the available BrowserStack devices 658
- Update appium server to remove command vulnerability 653
- Improve handling of Selenium
ServerErrors 6553
- Adds step to allow testing of a set of properties in a named span 651
- Update AWS SAM functionality to work with a newer version of SAM CLI 652
- Adds further retries for 'unknown errors' received by appium attempting to start a test session.645
- Use deviceGroupId capability to acquire device in BitBar tests where appropriate 646
- Serve documents from
/docson primary port 650
- Ensure appium:options are in the correct place for each version of appium 647
- Allow command servlet to respond appropriately when given UUID from previous test 643
- Only zip maze_output if file_log is on #644
- Add bugsnag middleware to group ambiguous errors differently 640
- Remove various unsupported BrowserStack devices 641
- Update reflective server to store and output received requests 639
- Forward port 8.19.0 to 8.20.1 to v9 638
- Remove blanket check on
service.versionin trace requests 637
- Add new span validation steps 630
- Add CodeQL fixes 632
- Ensure app_id is set correctly on BrowserStack test runs 633
- Add missing retry logic for appium downstream proxy error 636
- Fall back to
close_appifterminate_appfails 631
- Add additional symbol file upload endpoint 629
- Forward port 8.17.0 to 8.18.0 to v9 fork 625
- Remove use of deprecated
Maze.driver.resetin BitBar Appium tests 607 - Clear request lists while the app is stopped 619
- Ensure app_id is set correctly on BrowserStack test runs 634
- Add missing retry logic for appium downstream proxy error 635
- Add exit code for app-hang errors occurring in appium 628
- Re-enable bugsnag reporting test failures when MAZE_SCENARIO_BUGSNAG_API_KEY environment variable is present 626
- Allow Appium version to be set on BitBar 624
- Move appium session information to at_exit block to always run, even on maze-runner crash 623
- Split logging into STDOUT and File loggers, for more information during test runs 618
- Retry BitBar device session creation for
Appium Settings app is not runningerror 622
- Add method to allow pulling of files via appium client 617
- Add
--app-packageand--app-activityoptions (used for BitBar Appium tests only) 616
- Use Buildkite retry count correctly in BitBar test run names 614
- Add idempotent command endpoints 613
- Set
autoAcceptAlertsin iOS Appium tests 611
- Increase
uiautomator2ServerLaunchTimeoutto 60s on BitBar 610
- Modify retry logic for app upload failures and BitBar appium failures 608
- Work around Event Machine issues on ARM macOS 606
- Add appium options to the base capabilities dictionary 606
- Notify errors that occur in Appium or Browser hooks 605
- Write received sampling requests to
maze_outputfolder 604
- Fix crash when logging message for invalid requests 602
- Fix crash when BUILDKITE_JOB_ID is not set 603
- Correct error handling logic on BrowserStack 601
- Add appium options in more than one place to work with older appium servers 599
- Selectively retry creation of BitBar Appium sessions depending on the error encountered 600
- Reinstate
retry_start_driver?inLocalClient598
- Allow BB browser versions to be set via the command line 593
- Set default test timeout on BitBar selenium runs to 900 seconds 595
- Add the Buildkite job URL to the metadata reported to Bugsnag 597
- Avoid shell interpretation of characters in file names in
Maze::MacosUtils.capture_screen594 - Upgrade APT packages used within the Docker images to fix several vulnerabilities reported by AWS ECR scanning 596
- Add iOS 17 to the available BS devices 592
- Increase
uiautomator2ServerInstallTimeoutto 60s on BitBar 590
- Internal reporting and logging improvements 587
- Incorporate reporting of internal errors to BugSnag 586
- Use
BITBAR_ACCESS_KEYuniversally (only affectspurge-projectsentry point) 585
- Return specific exit code for Appium session creation failures 584
- Improve grouping and presentation of BugSnagged errors 583
- Set
appium:as the default prefix when running BitBar tests for appium 2.0 compatibility 582
- Allow
Bugsnag-Uncompressed-Content-Lengthin CORS header policy 581
- Allow
FileManager.write_app_filetarget location to be overwritten for Android 580
- Move the
maze_output.zipfile to themaze_outputfolder once created 579
- Add received span steps to allow greater flexibility in performance tests 571 572
- Check that required trace headers are present and valid 573
- Create zip archive of
maze_outputfolder 575
- Replace deprecated BrowserStack Samsung Galaxy S8 Plus device with Samsung Galaxy S8 576
- Add mechanism to allow hooks before scenario has completed in full 569
- Add additional sourcemap endpoints 570
- Correct logic for HTTP response codes to session requests 567
- Include traces in request types to set the HTTP response code for 566
- Only set HTTP response code for specific request types 565
- Sensible timeout for BitBar Appium sessions 564
- Fixes and enhancements to logging of received requests 558
- Fix order of assertion parameters 559
- Fix delete project function in
purge-projectscommand 560 - Do not reset driver with Appium 1.15/1.16 561
- Correct implementation of
the error is a valid browser payload for the error reporting API555
- Command line options reviewed for consistency 533
- Upgrade Docker image to Ruby 3 534
- Update logger to provide a real TRACE level 536
- Filter sampling requests into their own
RequestList537 - Shorten BrowserStack Android device names for consistency 538
- Reword header to
is presentrather thanis null540 - Rename BrowserStack mobile browsers to OS and version format 545
- Set
--expandCucumber option by default 548 - Add step
I set the device orientation to {orientation}551 - Avoid the need for quotes around integer lists 550 552
- Add standalone
purge-projectsexecutable 546
- Add iOS 16 and an up to date Android device browsers to the available BS devices 544
- Output received traces to stdout when a scenario fails 543
- Set BitBar dashboard project and test run for browser tests 542
- Add
Maze.config.receive_requests_slow_thresholdto warn for slow receipt of requests 541
- Only enforce Bugsnag integrity header on session, error and trace requests 539
- Correct setting of headers on repeated requests 532
- Update appium capabilities for appium 2.0 compatibility 512
- Add support for Edge latest on BrowserStack 528
- Only use separate BitBar accounts on CI 526
- Ensure BitBar apiKey is provided when using the tunnel 527
- Correct setting of
newCommandTimeoutcapability for BitBar Appium sessions 529
- Provide access to document server via AWS public IP addresses 525
- Allow BitBar Selenium server URL to be configured 524
- Improve JSON schema validation failure messages 516
- Refactor schema validation and add it to span expectation step 520
- Remove absolute browser versions no longer supported by BitBar 523
- Fix crash when trying to retry browser tests 515
- Fix crash when BitBar credentials cannot be fetched 513
- Allow JS to access the sampling header 517
- Fail upload-app with non-zero exit code if access key not given 518
- Ensure ids for apps uploaded to BitBar can be read from file 519
- Fix crash in Selenium
LocalClientcaused by unimplemented method 521
- Add step to assert parent-child span relationships 510
- Fix issue causing nil access errors in some span steps 514
- Add logic for step
a span field {string} equals {int}501 - Update upload-app script to allow BitBar uploads 504
- Add Datadog StatsD metric reporting for BitBar devices 503
- Add Datadog StatsD metric reporting appium test amounts 505
- Add logged links for selenium test sessions 507
- Improve logging when calculating BitBar dashboard project and test run 501
- Use
URI.opendirectly instead ofKernel.open508
- Add extra step to test if a particular span exists in a set a of trace payloads 499
- Fix wait for the SBSecureTunnel stopping 495
- Add missing passthrough for the initial sampling value trace payload 496
- Add Edge 80, Firefox 60 & Safari 11 to BrowserStack browser list 493
- Add further validation for trace payloads 489
- Add 'latest' versions of Chrome, Firefox & Edge to BitBar browser list 490
- Fix integer attribute step looking at stringValue 487
- Set all headers present when repeating requests to Bugsnag 488
- Start the document server after client hooks run so the document root can be set with other Maze Runner configuration 484
- Add missing Bugsnag-Span-Sampling header to Access-Control-Allow-Headers 485
- Add --list-devices option for BitBar devices and device groups
- Add BitBar browsers to those currently available 483
- Firefox 78
- Chrome 43 and 72
- Remove support for all Android 4 to 6 devices on BrowserStack 482
- Add link to BitBar dashboard for each Appium session 470
- Set Appium capabilities for the BitBar dashboard 471
- Clean exit for user readable errors 474
- Allow
--deviceto specify a device (rather than device group) on BitBar 475
- Set capabilities needed for iOS devices on BitBar (with Appium 1.22) 466
- Tidy capabilities for BitBar devices 473
- Correct logic for step
a span field {string} matches the regex {string}476
- Add iOS 11 and 12 browsers on BrowserStack. 469
- Associate
--devicewith device groups on BitBar and remove the need to provide--os/--os-versionoptions. 465 - Acquire device capabilities each time a driver start is attempted. Add Randomness to device selection to reduce likelihood of race conditions. 467
- Remove use of the TMS for BitBar Appium sessions on CI 464
- Add support for non-JSON content types to the reflective servlet 463
- Set
newCommandTimoutto 0 for BitBar Appium sessions 462
- Set missing CORS headers for OPTIONS requests in reflective servlet 461
- Added a step to assert that no spans have been received 460
- Only push test fixture config file on mobile and not in legacy mode 459
- Push test fixture config file containing Maze Runner address for Appium tests 456 458
- Add reflective servlet to main mock server 457
- Generate and use a single "run UUID" throughout the app 451
- Add
--aws-public-ipoption 452 - Get device logs for failed scenarios 453
- Add steps for verifying traces and spans 454
- Only set
projectandbuildcapabilities for BrowserStack 450
- Add support for
docker compose cpcommands 445 - Add steps for checking floating point values in error payloads 448
- Fix legacy mode for browser testing 449
- Refactor Selenium framework code into new class hierarchy in
Maze::Client::Selenium444 - Refactor starting of Appium client
Maze::Client::Appium446
- Correct capabilities for Safari 16 on BrowserStack 441
- Add
--tunnel(and--no-tunnel) option 431 - Add support for running
docker compose execcommands 425 - Add steps for checking an event has a specific number of breadcrumbs, or no breadcrumbs at all 433
- Simplify logger format 437
- Add
--repeateroption 438 - Add Safari 16 on BrowserStack 440
- Relax check on React Native Notifier name 432
- Add missing assertion against the breadcrumb name in "the event has a {string} breadcrumb named {string}" step 435
- Refactor schema validation to use JSON-schemer 436
- Retry BrowserStack app upload on
Net::ReadTimeout439
- Use
docker composeinstead ofdocker-compose429 - Bump BitBar browsers to those currently available 430
- Firefox 102 to 107
- Chrome 103 to 108
- Edge 101 to 106
- Safari 15 to 16
- Add additional step for breadcrumb tests, and refactor old steps for consistency 428
- Add schema validation for endpoints based on json-schema 416
- Allow HTTP response codes to be set for a series of requests 424
- Allow sampling probability header to be set for a series of requests 426
- Refactor response delay steps to use
Maze::Generator427
- Add
/traceendpoint 402 - Add steps to set sampling probably response header 419
- Log device UDID on BrowserStack 418
- Add support for iOS 16 on BrowserStack 422
- Provide more intuitive message for Maze.check.match failures 417
- Correct setting of Maze.config.os_version in W3C mode 415
- Reinstate support for JSON-WP with BrowserStack browsers 414
- Various fixes having updated bugsnag-android 413
- Add error code handling for pipeline management 406
- Add step
I wait to receive at least {int} {word}411
- Remove support for Google Pixel-8.0 on BrowserStack (deprecated by them) 412
- Add steps to enable specific status codes for given payload type 409
- Ensure appium-lib-core is restricted to
5.4.*while ongoing issues are present in5.5.*408
- Ensure
Stringpatterns behave as expected when callingMaze.check.match407
- Fix browser and appium drivers crashing when running without any capabilities 405
- Add step to sort received requests by specific field 402
- Fix local mode, broken in v7 refactor 403
- Improve docs structure 388
- Forward-port v6.23.0 to v6.26.0 to v7 stream 395
- Allow use of legacy Appium/Selenium clients 400
- Remove assert_* methods no longer needed to avoid a breaking change 387
- Fix support for BitBar to work with W3C capabilities 394
- Fix
RequestListinterface to avoid ambiguity 398 - Release BitBar account and stop tunnel on exit 401
- Update appium_lib (v12) and selenium-webdriver (v4), enforcing W3C 364
- Remove support for Sauce Labs 376
- Add support for Android 13 and iOS 16 Beta on BrowserStack 393
- Handle nil device list for
--farm=local392
- Attach UUIDs to command payloads for better tracking 389
- Add support for Android 13 Beta on BrowserStack 386
- Update BrowserStack target definitions 383
- Display scenario locations in grey 381
- Add driver restart and retry to browser navigation step 377
- Include scenario locations in folding log line 378
- Add support for connecting appium driver to BitBar 282
- Add automatic retries when Selenium driver fails to start 372
- Update
Maze::Helper.get_current_platformto supportbrowser373
- Add support for delivering and saving maze-runner reports 370
- Allow access to pids created by the Runner 371
- Update start-driver retry logic to enable device lists 366
- Capture macos screen when scenario fails 369
- Allow appium driver start failures to be retried within 60s 359
- Add
Maze.config.captured_invalid_requeststo allow invalid requests to be ignored on specific endpoints 362
- Allow BrowserStack credentials to be set separately for devices and browsers 358
- Stop BrowserStack tunnel after browser test runs 357
- Add dynamic retries 356
- Add Chrome 40, 42 and iPhone 62 (iOS 9), iPhone 13 (iOS 15.4) support 355
- Allow
--os-versionto be omitted when--farm=local345
- Correct Maze.check.match implementation to allow message to be provided 354
- Add Chrome 30, 32, 34, 36, 38, 40, 42 and Android 4.4, 5.0, 6.0 support 353
- Defaults the read size to 1 MB for the terminating server 352
- Retry failed BrowserStack app uploads each minute for 10 minutes #350
- Add method to download device logs from BrowserStack #344
- Only report to Bugsnag on genuine errors, not test failures #347
- Add support for CrossBrowserTesting #342
- Add server for terminating http connections early #343
- Correct BrowserStack capability to
disableAnimations#323
- Fix received errors match step #346
- Add retry to BrowserStack app upload #338
- Add the
--colorarg to cucumber a default option #340
- Correct retry pluging to allow
--retryto have an effect #337
- Make sure valid requests are output with correct JSON formatting #336
- Ensure invalid request logging works correctly in CI mode #335
- Add
/commandendpoint #332
- Add
Maze.timersand Appium operation timing summary #329
- Set Appium capabilities to speed up iOS App Hang tests locally #330
- Add step
I send the app to the background#326
- Set Appium capabilities for improved performance on Sauce Labs #325
- Fix killing deadlocked Mac fixtures #320
- Fix support for Sauce Labs #318
- Ensure
--osand--os-versionare provided for Sauce Labs #319
- Bump BrowserStackLocal from 8.0 to 8.4 #317
- Add Safari 14 and 15 #316
- Make sure device logic isn't run in BrowserStack browser mode #315
- All
--appto be specified in a file using@prefix #312 - Allows multiple
--deviceoptions to be specified #314 - Add automatic reporting to Bugsnag on test failure #313
- Use
refreshwhen Browser driver can retry scenario #311
- Add Android 12 and addition Android 7 devices #308
- Correct command line option for
--enable-retries#307
- Align Appium versions for iOS devices with latest BrowserStack offering #305
- Add entry for iOS 15 device on BrowserStack #304
- Add LLVM to Docker image (and upgrade to Debian 11) #302
- Add further Selenium errors for which a scenario retry can be allowed #301
- Upgrade to Cucumber 7 #300
- Adds retry functionality on specific selenium/appium errors or on
@retrytags #295
- Improvements to payload step failure messages #296
- Expose
window_sizeonMaze::Driver::Appium#293
- Add reflective servlet to
DocumentServer#291
- Add the follow steps #289
the {word} payload field {string} equals the stored value {string} ignoring casethe {word} payload field {string} does not equal the stored value {string} ignoring case
- Ensure 'noReset' capability is present when running iOS appium tests locally #287
- Pin Docker images on Debian 10 (Buster) #286
- Remove blanket rescue for macOS in step
I click the element {string}#285
- Support running with Ruby 3 #284
- Add
/sourcemapand/react-native-sourcemapendpoints toMaze::Server#281
- Add Appium driver no-element send_keys method #278
- Add support for running tests against local browsers #279
- Add document server (
--document-server-rootand associated options) #274
- Pin RubyZip to avoid possible breakage from RubyZip 3.0 #275
- Call after_configuration hooks even if farm is
:none#276
- Pin RubyZip to avoid possible breakage under Ruby #275
- Add
/uploadsendpoint for receiving upload requests #271 - Add 'the {word} {string} header is null' step #272
- Correct guard for platform-dependent value steps #270
- Only start macOS apps when using Appium #269
- Add multipart parsing steps usable for any payload types #261
- Add
--file-logoption to write received requests to files #262 - Add additional BrowserStack Android 10 devices #264
- Remove short form from all command line options #263
- Add
--always-logoption #258
- Add support for macOS running on ARM #259
- Add Android 9.0 Pixel 2 variant for unity testing #256
- Enable locally running appium server to log to a file #252
- Log file defaults to
appium_server.log - Can be overwritten using
--appium-logfileoption
- Log file defaults to
- Remove use of unlicensed Boring gem #251
- Correct wording of failure message for Cucumber step
I should receive no {word}#254 - Fix
osnot being present for platform-dependent comparisons outside of device farms #255
- User interface refinements and improved validation #249
- Integration with Sauce Labs device farm #246
- Enhances for running Android tests with Appium 1.20.2 #244
- Use Appium 1.20.2 for BrowserStack devices where possible
- Add
--start-appiumoption for running with local devices, defaulting to true - Add
Maze::Driver::Appium.set_rotation
- Always log version number #247
- Add stress-test step asserting a minimum amount of requests received #239
- Add option to not log received requests on a test failure #238
- Loosen requirements on Lambda responses #237
- Add click_element_if_present to Appium driver #236
- Do not set explicit default for mock server bind address #234
- Update endpoint steps and ensure Maze::Network is available by default #235
- Stop BrowserStackLocal binary at end of run without hanging #233
- Stop BrowserStackLocal binary at end of run #232
- Only expand
--appoption when uploading to BrowserStack (complete fix) #226
- Add steps to delay the response to the next received HTTP request #224
- Only expand
--appoption when uploading to BrowserStack (incomplete fix) #225
- Add additional CLI and file verification steps #221
- Add integration with AWS SAM CLI to test Lambda functions #223
- Add steps to check interactive CLI STDOUT logs using a regex #220
- Expand file paths for
--appand--bs-localoptions #219
- Log BrowserStack link for browser builds #218
- Correct processing of
/logsendpoint requests #216 - Set
disableAnimationscapability on BrowserStack devices #217
- Add
/logsendpoint for receiving log messages #214 - Add
/buildsendpoint for receiving build requests #213
- Use the standard library rather than
curlfor app uploads and handle error responses #215
- Add root
/endpoint for use in connectivity checks #211
- Remove unnecessary delay between scenarios #212
- Add in-built appium server control for local testing #202
- Allow the use of @null and @non-null in platform-dependent assertion tables#210
- Ensure received requests are in order by sent time #209
- Platform-dependent steps made payload independent #208
- Corrections for Browser automation #207
- Further Android 4.4 and 5.0 devices added #206
- Sort received requests by Bugsnag-Sent-At header #209
- Additional device options added for Android 4.4 and 5.0 #204
- Logging corrections and improvements #203
- Mock server and steps updated to receive different request types on separate endpoints #186
- Ensure environment variables cannot leak through --help dialogue #198
- Strip ANSI escape codes from interactive CLI output to improve reliability #197
- Fix broken link to BrowserStack dashboard #196
- Only run Docker compose to stop all services if any have been started #195
- Clear request arrays after each scenario instead of beforehand #190
- Add
--capabilitiesoption #177 - Add support for macOS devices using AppiumForMac #178
- Enforce presence of
Bugsnag-Integritybased on MazeRunner.config.enforce_bugsnag_integrity #179 #180 - Add steps for running interaction shells #185
- Enabled specific configuration options to be set using environment variables. #188
- Fix ordering issue with docker exit code/output #175
- Allow timezone offsets in timestamps #174
- Refactor of request steps and additional multipart/form-data steps #163
- Add full range of iOS 11 devices on BrowserStack to test against #166
- Add the Bugsnag-Integrity header to Access-Control-Allow-Headers #167
- Fix always false comparison when checking the simple digest #170
- Add Cucumber steps for checking Bugsnag-Integrity headers, in addition to automatically verifying digests on all received requests when the header is present. #159
- Reinstate environment clearing between scenarios #164
- Fix
I clear the element {string}step. #165
- Make use of ResilientAppiumDriver optional #159
- Fix Appium version for iOS devices to 1.15.0. #161
- Add steps for setting the HTTP status code to be returned to incoming requests #157
- Run docker-compose commands attached rather than detached. #158
- Provide ability to locate elements by accessibility id #151
- Add command line option to set Appium version #152
- New steps for running Docker service with multiline commands and checking values are of certain types. #155
- Explicitly set Appium version for use with BrowserStack devices. #154
- Do not clear environment between scenarios (introduced in v2.6.0). #149
- Push released Docker images to their own repository to avoid deletion. #146
- BrowserStack specific elements separated from AppAutomateDriver (now simply AppiumDriver), providing the ability to use MazeRunner with local devices. #139
- Logging improvements when starting Appium driver (including BrowserStack link) #141
- Resolve logged BrowserStackLocal errors by moving to Ubuntu base image #140
- Allow BrowserStackLocal path to be provided in environment. #137
- Allow URLs to be provided for app location to avoid duplicate uploads. #136
- Addition of ResilientAppiumDriver to catch and restart broken Appium sessions. #134 #138
- Added option to start a new Appium session for every scenario. #133
- Correct Android version for device entry Galaxy Tab S3 #135
- Table-based assertions on requests, including option to specify expected values with Regexps. #131
- Clear environment at start of scenarios #130
- Range of additional Android 6, 8.0 and 8.1 device options provided, together with Android 11 and iOS 14. #127
- Ability to run an HTTP/S proxy added #128
- Retry starting of the mock server in cases of failure #120
- Cucumber hooks consolidated into one file #121
- Notifier builds automatically triggered against new versions of
master#122 - Use BRANCH_NAME throughout instead of BUILDKITE_BRANCH #123
- Remove explicit setting of Appium versions on individual
DEVICE_TYPEs, introduced in 2.3.0. #119
- Fix module load order by requiring Servlet and Logger from Server class #118
- Fix error when parsing request with no body #118
- Update platform comparison step to allow skipping via keywords #109
- Update platform comparison steps to target different parameter types #110
- Add reset_with_timeout method to improve flake resilience #114
- Add Appium restart logic to wait_for_element and reset when Appium errors occur #116
- Correct passing of defaulted parameter. #107
- Add ability to clear text from an element. #104
- Provide new step to allow a timeout to be set when waiting for an element to be available. #105
- Provide new step to allow different expected values on different platforms #103
- Make --retry and --fail-fast play nicely together by bumping Cucumber to 3.1.2.
- Account for --retry being provided when adding --strict option (to allow flaky tests).
- Run Cucumber with strict mode, unless any strict/no-strict option has been set.
- Log all received requests when a Scenario fails.
- Auto-collapse log output for passing scenarios when run using Buildkite.
Major new version focused on using Buildkite to run tests on real devices using BrowserStack.
Addition of HTTP version steps.
Various changes have been made since the 1.0.0 release, but no specific versioning strategy was employed. This minor release encapsulates those changes and no further significant changes to the v1 series is expected (v2 already exists and should be used in preference).
Initial release