Daven

Looking at this blog post too https://dockyard.com/blog/2019/02/13/understanding-test-concurrency-in-elixir specifically at Ecto.Sandbox's [shared mode](https://hexdocs.pm/ecto_sql/Ecto.Adapters.SQL.Sandbox.html#module-shared-mode), but it looks like test are already using that https://github.com/papercups-io/papercups/blob/master/test/support/conn_case.ex#L38. This isnt a big deal tho, since doesn't...

~~Hmm when testing the `slack_controller_test.exs`, we only want to tests the controller right, and not the `Conversations.Notification` which calls `Conversations.Notification.notify/1`, which contains the call to `Task.start`~~ ~~What if we mock...

Ok I have a [branch](https://github.com/papercups-io/papercups/compare/master...fmterrorf:silence_ecto_errors) that removes these errors  It uses Mock's [setup_with_mocks](https://github.com/jjh42/mock#setup_with_mocks---configure-all-tests-to-have-the-same-mocks) to mock the calls to `notify` functions (that calls Task.start). The downside is...

I noticed the default Firefox stylesheet have this code `resource://gre-resources/html.css` ```css h5, :is(article, aside, nav, section) :is(article, aside, nav, section) :is(article, aside, nav, section) :is(article, aside, nav, section) h1 {...

I can also attempt to put up a fix if you want. Im thinking of just using `npx cypress` to run the cypress bin as a fix

> @fmterrorf by all means, we welcome community PRs! I'll make sure it gets reviewed right away +1 I might have to skip on this. I can't figure how to...