Paweł Pacana

```ruby def assert_items(actual_elements, expected_procs) assert_equal( expected_procs.length, actual_elements.length, "number of actual elements does not match expected" ) actual_elements.zip(expected_procs) do |actual, expected| expected.call(actual) end end ```

```ruby def assert_published(event_kind) event = event_store.read.of_type(event_kind).last assert_not_nil event yield event end def assert_not_published(event_kind) assert_nil event_store.read.of_type(event_kind).last end ```

https://github.com/RailsEventStore/rails_event_store/issues/659#issuecomment-515233231 ^^ that would be more of `assert_dispatched`, there no information about stream when dispatching to handlers

A few more samples from _the wild_: ```ruby def assert_equal_event(expected, checked, verify_id: false) if verify_id assert_equal expected.event_id, checked.event_id end assert_equal expected.class, checked.class assert_equal expected.data, checked.data end def assert_equal_events(expected, checked, verify_id:...

In the meantime I've rebased and merged PR with initial gem. See it at: https://github.com/RailsEventStore/rails_event_store/tree/master/contrib/minitest-ruby_event_store

Possibly knowing a platform (Heroku or AWS) could be helpful for us to optimize overall RES experience.

It could be useful to inspect database schema (if RDBMS present)

- with Skylight

- mention serializers/mappers - mention pluggability - mention not only rails - mention built-in browser - mention testing helpers/matchers (rspec)

@joelvh Feel free to put more intro `contrib/`. So far the common thing about it is that code there does not get released along "official" RES gems and does not...