[AngularJS Project] Add E2E tests

[dustin]

We need some capability to run end-to-end tests of the AngularJS frontend to avoid UI regressions and other issues that are not obvious in unit tests.

This should be done with the normal angularJS methodology, with protractor: ​https://docs.angularjs.org/guide/e2e-testing

What is necessary for e2e tests is:

• create a real buildbot master with a real configuration, which contains configuration for major use cases involving the UI. e.g force schedulers, authentication, etc

• Have protractor scenarios which acts like a user would, and verify that the UI behaves as expected.

• User authenticates in the UI
• User go to the list of builds for a builder
• User click on the forcescheduler button
• User adds some input in the modal dialog
• build is started, and there are updates in the UI

The idea should be to hook up the tests in the metabuildbot, and allow motivated developers to run them manually, but they need not be as easy to run as 'trial buildbot.test'.

Documentation on what are the steps to run that (probably easiest is to setup the deps in a dockerfile)

[MikeLing]

Replying to dustin:

Hello, I'm interested in this project and want to know more about it. And I found we have [AngularJS Project] in the title. Is it a independent project like metabbotcfg? Could you me where could I found more information about this project?

• create a real buildbot master with a real configuration, which contains configuration for major use cases involving the UI. e.g force schedulers, authentication, etc

I haven't catch the ideal of a real buildbot master with a real configuration actually. Because I'm new to buildbot, and the only thing I know about it is the codebase in here(​https://github.com/buildbot/metabbotcfg). So could you tell me something about how to configure buildbot and other related ideal about it?

Thank you :)

[tardyp]

@MikeLing? For this project, you will need to understand how the buildbot is working. You can start with the doc:

​http://docs.buildbot.net/latest/manual/introduction.html

and try to install it on your machine, create a custom configuration, run some builds via the UI.

Once you have done that manually, you can then find out how to run the same automatically for the e2e tests

[anonymous]

migrated to ​https://github.com/buildbot/buildbot/issues/2980