Writing marble tests

[jmfayard]

Hello, what I lack when testing rx java things is the ability to quickly produce input observables.

RxJs has super cool functions to produce those

cold("--a--b--#"): On frame 20 emit a, on frame 50 emit b, and on frame 80, error`

hot("-a-^-b--|"): In a hot observable, on frame -20 emit a, then on frame 20 emit b, and on frame 50, complete.

https://github.com/ReactiveX/rxjs/blob/master/doc/writing-marble-tests.md

something like that in kotlin would be super valuable

[RubyLichtenstein]

Looks interesting, thank you.

[RubyLichtenstein]

Hi @jmfayard

Do you want to work on this feature?

[jmfayard]

@RubyLichtenstein I can contribute what I already did. I fear I don't understand enough rxjava to make it right by myself though

[RubyLichtenstein]

Great, so please fork the project and add what you all ready done

What about porting the JavaScript code to kotlin code?

[jmfayard]

We should steal their ideas, not their code. A lot of how it's implemented rely on how javascript works. e.g you don't have dynamic types on the JVM.

[RubyLichtenstein]

I think we should take what we can from the js code. We shouldn't do work that already done Its not stealing if its open source :)

[RubyLichtenstein]

https://github.com/ReactiveX/rxjs/blob/master/src/internal/testing/TestScheduler.ts

[RubyLichtenstein]

Most of the code should be the same

[jmfayard]

I meant stealing in a positive sense, like T.S. Eliott quote Good artists copy; great artists steal.

[jmfayard]

https://github.com/RubyLichtenstein/RxTest/pull/19

[RubyLichtenstein]

Great job!

I'll review it as soon as I have time

[RubyLichtenstein]

So the work you did is not based on the js implementation?

[jmfayard]

no, I didn't have the code of the js implementation at that time.