Investigate porting existing tests to the new frontend environment

[Balazs Ree]

Spend 1h on looking at the existing tests and decide the best approach to take to utilize them in the new environment.

unit tests: are in QUnit, try out if it's easy to convert it to karma+jasmine.

e2e tests: try to run the tests if that's easy. Work out a method to convert them to protractor (or some other webdriver variant).

The goal of the task is not to do the conversion but experiment. Post results and findings here.

[Paul Everitt (paul-agendaless)]

Balazs, is there any more work to do on this?

[Balazs Ree (ree)]

Conclusion:

Actually all unittests are completely ported! There were ones that gave some errors, but mainly because of the multitude of technologies we applied during the history of the project. I believe I could find a balance which allowed me to copypaste most of the test code, but yet assure stable test runs of the legacy test libraries on top of the current newest frameworks.

I've also did fixes on the e2e runner environment. As part of the e2e migration experiment, I found a way in which we can first generate boilerplate code and then use it to manually convert into protractor code. This is more a manual process then what I succeeded with the unit tests, and yet has to be done in the future. We have the environment in place, and on top of that Paul has written tests that visit all principal urls of the site. To this, we can now migrate and add the old selenium tests.

I suggest to enter a separate task for migrating the remaining selenium tests.

[Paul Everitt (paul-agendaless)]

Balazs, sorry to bug you, but...it looks like this branch didn't get merged:

  https://github.com/karlproject/karl/commits/ree-porting-existing-tests-lp1377158

I'm sure it was my fault that it didn't get merged, and I apologize for asking you to put your thinking cap on and go back a year, but do you agree that I should merge this branch? (Once I make sure it still works without error.)