sorry, but this test is kind of silly. :)

instead of testing the api, test the behavior and tell a story. actually just focus on telling stories and that will help you focus on testing the behavior :)

in this case the story that you care about is that by instantiating the class you get an object with a property `log` set to an empty array.

```js
it('should create an object with log property set to an empty array', () => {
  var reporter = new MockReporter();
  expect(reporter.log).toEqual([]);
});
```

note: note that I didn't use before each to instantiate the reporter, this is because my experience on writing thousands of tests for angular taught me that beforeEach is more often than not abused and results in hard to read and hard to maintain tests. beforeEach optimizes the test writing at the cost of reading and maintaining.

if you use beforeEach, then when a test starts failing you need to first check what the beforeEach is doing and if there is any other beforeEach above the current beforeEach that is relevant. This is time consuming and not worth the time.

Additionally, in 6 months you might need to add a argument to the constructor and will need to write some tests that use the argument during instantiation and others that don't. then you'll need to redo all of the tests which is often painful and makes you consider cheating (e.g. ignoring the instance created in beforeEach and instead overwriting it with a new instance created in a test).