Santiago Ferreira

When the assertion does not contain an associated assertion message, we add one. The message we're adding is not correct for some cases (assert.equal).

Instead of `foo bar got focused` just show a message that reads `Focus element` or something like that. We could test if the focused element is an input and say...

It would be great if we had an option to not show assertions when playing a test.

Right now we have implemented vertical scroll but we didn't implement the horizontal scroll for the mouse.

We reproduced this error in code corp test http://localhost:4200/tests?filter=Acceptance&nolint&testId=f154bb45&tellingStories It happens some times only.

See code corps test http://localhost:4200/tests?filter=Acceptance&nolint&testId=f154bb45&tellingStories

It raises an error because it tries to use the `player` but it's not created. It should not throw an error!

Add tests to the addon: * One for the installation blueprint * We can unit test some parts of the addon * Have some acceptance tests for sanity check

Github offers to generate website from /docs folder, can we read and show this documentation from the addon? Like showing an TOC and a way to navigate it? We could...

When inspecting an addon that was included by another addon it would be great to show a note indicating this. ``` * foo-addon included by: bar-addon ```