most-subject async() doesn't work with most-test

[marcusradell]

Webpackbin reproduced bug: http://www.webpackbin.com/VyTK1Nv8M

It seems like most-test works without the subject, but with the subject, not even the initial state sent to .scan works.

Without subject, I get 1 event and I expect 1.
With subject, I get 0 events and I expect 3 (initial state, press, press delayed 500ms).

[TylorS]

This is because most-subject makes use of the defaultScheduler provided by most.js and not the scheduler used by most-test

[axefrog]

@TylorS how hard would it be to switch to the scheduler specified by the run() call once it becomes available? You could switch back to the default scheduler if the active stream graph is disposed.

[TylorS]

I'm not too sure yet, but I'm going to have to rethink most-subject to work with @most/core to deal with schedulers, as there is no default scheduler anymore.