Closed Neroware closed 5 months ago
The above still applies, but I would propose to implement a new and improved test-suit. Verification is quite important in asynchronous programming but sadly I lack the time to properly introduce a working set of unit tests for all operators. Help wanted for this issue.
As long as there is no proper verification, the 'untested' will remain in README.md page.
I have implemented a new and improved test-suit. It should get the job done for now. (At least, it does not get a memory leak on exit.) Example tests are in "./reactivex/testing/tests/". I will close this issue for now and open a new one for the implementation of tests. Help wanted on that matter!
Unfortunately my test suit is not very good. It gets the job done to test a few observables but it is not pretty and a product of a lack of time and motivation. Currently, it always causes a memory leak on exit, even for simple observables like ReturnValue, which are pretty much safe to function properly.