I was wondering why you just move it on the top, and now I see. You basically did that in order to get the exception of Unsupported Application as first, but this is actually one of the issues we tried to solve introducing the module metadata in test file. We shouldn't rely on that, we should just add explicitly the metadata on top of the test file, like we have on the module file, that defines for which platform or version the test suite is supposed to run.

So, put it back, and add the module.metadata:

```js
'use strict';

module.metadata = {
  engines: {
    'Firefox': '*'
  }
}
```