Every acceptance test will run the initializer, but this is really just for global one time setup (not once for each app).
TBH, I prefer to avoid initializers for this kind of one time global setup (preferring one of the JS land contentFor hooks or app.import from a vendor shim). This allows unit and integration tests to use the modified code paths also (otherwise unit and integration tests ran before the first startApp call will not use ember-run-raf since initializers are not run in that context).
Every acceptance test will run the initializer, but this is really just for global one time setup (not once for each app).
TBH, I prefer to avoid initializers for this kind of one time global setup (preferring one of the JS land contentFor hooks or app.import from a vendor shim). This allows unit and integration tests to use the modified code paths also (otherwise unit and integration tests ran before the first startApp call will not use ember-run-raf since initializers are not run in that context).