Changes between Initial Version and Version 1 of Ticket #3452


Ignore:


Timestamp:
Feb 14, 2016, 1:48:33 PM (4 years ago)
Author:
tardyp
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3452 – Description

    initial v1  
    11We 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.
    22
    3 This should be done as much as possible in the "normal" node / AngularJS mode, so perhaps with mocha-phantomjs or even selenium.  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'.
     3This should be done with the normal angularJS methodology, with protractor:
     4https://docs.angularjs.org/guide/e2e-testing
     5
     6What is necessary for e2e tests is:
     7
     8- 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
     9
     10- Have protractor scenarios which acts like a user would, and verify that the UI behaves as expected.
     11
     12- User authenticates in the UI
     13- User go to the list of builds for a builder
     14- User click on the forcescheduler button
     15- User adds some input in the modal dialog
     16- build is started, and there are updates in the UI
     17
     18The 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'.
     19
     20Documentation on what are the steps to run that (probably easiest is to setup the deps in a dockerfile)