DataMonitor | Location Manager Monitor for Android Devices | Android library

wrapper is a collection in your code.

Instead of

You need to explicitly start your application before running database queries; mix tasks don't do that automatically.

Change:

though GenServer.cast/2 [...] how I can collect the responses

You cannot per se. Cast requests are asynchronous and return no response. The only way to collect the data from casts, would be to introduce a store (like an Agent, or ets, or whatever,) and store the values directly from casts. This solution has the obvious drawback: the workflow of it would be undetermined, one might not assume all the 10 responses are processed and stored at any time. That said, casts under some circumstances might even be lost and unprocessed and you have no chance to get notified about that. I have never met such a case, but it’s considered to be legit.

So, in this particular case, you probably should just use GenServer.call/2 instead of cast, and collect responses directly in the iteration with Enum.map/2:

You only mock objects that need to be controlled.

You should never ever mock simple collection instances. You simply pass around collection objects that carry the content required to make your code under test the expected path. In your case, you could simply pass an empty map to that class. And after invoking the method under test you check if that map contains the required content.

And to verify the content of a map you simply query the map for its content. For example by using the assertThat assert together with the hamcrest is matcher.

But just to be precise: you don't want to write tests that need to know about such implementation details. You should test the public contracts of your methods instead of exposing the fact that you are using a map to hold values.

Finally: it seems that you don't understand what mock objects are actually about. They are mocks that appear to be instances of a certain class. But they absolutely do not know anything about the real class. A mocked map doesn't store keys and values. The only thing that you can do is to specify respectively verify what method calls are expected to happen for that mock object.

Internet Explorer 11 should support matchMedia. Therefore, the most likely cause is that the document is being parsed in a non full standard mode. Probably because you did not specify a doctype at the top of your HTML, e.g.: