@@ -297,9 +297,9 @@ Feature: JSON formatter
297297 When I run cypress
298298 Then it fails
299299 And there should be no JSON output
300- And the output should match
300+ And the output should contain
301301 """
302- Hook failures can't be represented in JSON reports, thus none is created for cypress[\\\/] e2e[\\\/]a\ .feature\ .
302+ Hook failures can't be represented in JSON reports, thus none is created for cypress/ e2e/a .feature.
303303 """
304304
305305 Scenario : failing beforeEach hook
@@ -323,9 +323,9 @@ Feature: JSON formatter
323323 When I run cypress
324324 Then it fails
325325 And there should be no JSON output
326- And the output should match
326+ And the output should contain
327327 """
328- Hook failures can't be represented in JSON reports, thus none is created for cypress[\\\/] e2e[\\\/]a\ .feature\ .
328+ Hook failures can't be represented in JSON reports, thus none is created for cypress/ e2e/a .feature.
329329 """
330330
331331 Scenario : failing afterEach hook
@@ -349,9 +349,9 @@ Feature: JSON formatter
349349 When I run cypress
350350 Then it fails
351351 And there should be no JSON output
352- And the output should match
352+ And the output should contain
353353 """
354- Hook failures can't be represented in JSON reports, thus none is created for cypress[\\\/] e2e[\\\/]a\ .feature\ .
354+ Hook failures can't be represented in JSON reports, thus none is created for cypress/ e2e/a .feature.
355355 """
356356
357357 Scenario : failing after hook
@@ -375,7 +375,7 @@ Feature: JSON formatter
375375 When I run cypress
376376 Then it fails
377377 And there should be no JSON output
378- And the output should match
378+ And the output should contain
379379 """
380- Hook failures can't be represented in JSON reports, thus none is created for cypress[\\\/] e2e[\\\/]a\ .feature\ .
380+ Hook failures can't be represented in JSON reports, thus none is created for cypress/ e2e/a .feature.
381381 """
0 commit comments