Commit 48398032 authored by intrigeri's avatar intrigeri
Browse files

Test suite: improve error output when the Unsafe Browser fails to start in some locale

Before 91674552, FindFailed inherited
from RuntimeError, but it now inherits from StandardError,
so we did not catch this exception anymore, and thus:

 - The scenario aborted immediately, instead of testing other locales.

 - We lacked the nice "Unsafe Browser failed to launch in the following
   locale(s): " message ⇒ need to read debug.log to figure out which
   locale failed.

This commit does *not* fix another problem though: if the Unsafe Browser did
start but the expected startup page is not visible, then we would
leave it open and testing the next language will fail.
parent 3ac74a0f
......@@ -38,7 +38,7 @@ Then /^the Unsafe Browser works in all supported languages$/ do
step "I start the Unsafe Browser in the \"#{lang}\" locale"
step "the Unsafe Browser has started in the \"#{lang}\" locale"
rescue RuntimeError
rescue StandardError
failed << lang
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment