Add basic tests for frontend

[garatortiz]

Closes #10

[coveralls]

Pull Request Test Coverage Report for Build 135

• 7 of 7 (100.0%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+20.7%) to 46.821%

---

Totals
Change from base Build 133:	20.7%
Covered Lines:	143
Relevant Lines:	264

---

💛 - Coveralls

[fvictorio]

Is the array necessary here?

[garatortiz]

Maybe not... I used it only for the first expect

expect(wrapper.find('div.footer')).toHaveLength(1)
expect(wrapper.find('div div.logo-container')).toHaveLength(1)
expect(wrapper.find('div div.logo-container p')).toHaveLength(1)
expect(wrapper.find('div div.logo-container a.poa-logo')).toHaveLength(1)
expect(wrapper.find('div div.logo-container div.social-container')).toHaveLength(1)
expect(wrapper.find('div div.logo-container div.social-container a.social-item')).toHaveLength(3)

[fvictorio]

I'm not asking why did you add the class. I'm saying that this is the only place where an array is used instead of just listing the arguments. We should use the API consistently even if glamorous accepts different ways of specifying the parameters.

But maybe there was a reason to use it this way here, that was the question.

[garatortiz]

Ok, now I understand the question. Based on what I read about Glomorous, I understood that the way to indicate two or more classes is with an array, and when it is only one class it can be listed or use an array.

[fvictorio]

I can't find anything about that in the documentation. Can you give me a link?

[garatortiz]

I don't remember where I had read it, or if I just tried and it worked... but I only did it for that test... in any case we can remove it if you think so.