Feature/testing infrastructure

[mauriciovieira]

Following Rocket.Chat testing infrastructure.

What I have now is an end-to-end test using chimp.js that opens a browser and tests the login page. The test is currently flaky, not returning positive answer all times.

I would also like to make it to run in Travis, but it'd be better as a new task.

[mauriciovieira]

End-to-end tests for login page working:

But it requires the application to be running on other terminal.

Rocket.chat solves it in travis-ci with xfvb

[brylie]

Clean up unused code (comments)?

[mauriciovieira]

After trying for a few weeks, I coudn't reliably test the Branding page following the official docs.

What I am trying to do here is to create a basic set of end to end tests inspired by Rocket.Chat tests.

Then, I will test the Branding page to close #1506.

@ashakunt @brylie Notice that we'll still have to run the end2end tests on travis, probably also following the Rocket.Chat example.

These e2e tests can add some regression tests on basic behavior, but we'll need a solution for testing the REST API as well as other server side methods (covered by #1714).

[mauriciovieira]

@brylie @ashakunt I added documentation on an initial suite of end to end tests. In order to run, it is necessary to have a meteor server running and also google chrome.

Please review.

This PR closes #2615

[mauriciovieira]

@brylie I fixed your requests

[mauriciovieira]

Closes #2622 as well

[as33ms]

Looking into it during today.

[mauriciovieira]

@wuder4 please also take a look.

[as33ms]

I reviewed this branch using my browser today (ideally, would have wanted to run stuff locally); and oh boy, wasn't it pain to review such a large chunk in Chrome.

In principle, I think its Ok to merge. However, a few things I would like to bring to notice: The testing team is looking forward to write the E2E tests in Robot + Selenium because they are easy to learn, write and run. So at this point, most of our test assets will start to be shown in that framework (at least all what will be contributed by @wuder4, unless, he is willing to learn chimp and already start with that?

IMHO, we should merge this to develop and try to develop our test assets using either CHIMP or ROBOT, what ever is preferred by the test writer. My personal fav is ROBOT because of its simplicity to read and write. Comments welcome.

[mauriciovieira]

@brylie @wuder4 do you have comments?

Changes already done.