Rename fixtures files (batch 2) (#2621)

* Rename csp fixture

* Rename delivery fixture

* Rename device fixture files

---------

Co-authored-by: Steve Kirkland <steve.kirkland@smartbear.com>

Author: twometresteve

test/browser/features/csp.feature

@@ -2,5 +2,5 @@
 Feature: Compatibility with a Content Security Policy
 
 Scenario: notifer does not crash for CSP violations
-  When I navigate to the test URL "/csp/script/a.html"
+  When I navigate to the test URL "/csp/script/no_crash.html"
   Then I let the test page run for up to 10 seconds

test/browser/features/delivery.feature

@@ -3,8 +3,7 @@ Feature: Delivery of errors
   @skip_ie_10
   Scenario: Delivery is attempted oversized payloads
     When I set the HTTP status code for the next "POST" request to 400
-    And I navigate to the test URL "/delivery/script/a.html"
-    And I wait for 5 seconds
+    And I navigate to the test URL "/delivery/script/oversized.html"
     Then I wait to receive an error
 
     # Check that Bugsnag is discarding the event

test/browser/features/device.feature

@@ -2,7 +2,7 @@
 Feature: Browser device data
 
 Scenario: Device data is included by default
-  When I navigate to the test URL "/device/script/a.html"
+  When I navigate to the test URL "/device/script/enabled.html"
   And I wait to receive an error
   Then the error is a valid browser payload for the error reporting API
   And the event "device.time" is not null
@@ -12,7 +12,7 @@ Scenario: Device data is included by default
   And the event device ID is valid
 
 Scenario: Device ID is not collected when the config option is disabled
-  When I navigate to the test URL "/device/script/b.html"
+  When I navigate to the test URL "/device/script/disabled.html"
   And I wait to receive an error
   Then the error is a valid browser payload for the error reporting API
   And the event "device.time" is not null
@@ -23,17 +23,19 @@ Scenario: Device ID is not collected when the config option is disabled
 
 @skip_if_local_storage_is_unavailable
 Scenario: Device ID is read from local storage
-  When I navigate to the test URL "/device/script/c.html"
+  When I navigate to the test URL "/device/script/store_id.html"
   And I wait to receive an error
   Then the error is a valid browser payload for the error reporting API
   And the event device ID is "cabcdefghijklmnopqrstuvwx"
-  When I navigate to the test URL "/device/script/a.html"
-  # This is 2 requests because the first request still counts (i.e. it's only 1 _new_ request)
-  And I wait to receive 2 errors
+  And I discard the oldest error
+
+  When I navigate to the test URL "/device/script/enabled.html"
+  And I wait to receive an error
   Then the error is a valid browser payload for the error reporting API
   And the event device ID is "cabcdefghijklmnopqrstuvwx"
-  When I navigate to the test URL "/device/script/a.html"
-  # This is 3 requests because the first 2 requests still count
-  And I wait to receive 3 errors
+  And I discard the oldest error
+
+  When I navigate to the test URL "/device/script/enabled.html"
+  And I wait to receive an error
   Then the error is a valid browser payload for the error reporting API
   And the event device ID is "cabcdefghijklmnopqrstuvwx"