GitHub user 1ambda opened a pull request:

    https://github.com/apache/zeppelin/pull/2477

    [ZEPPELIN-2342] Improving Test Environment for zeppelin-web (e2e, coverage, 
..)

    ### What is this PR for?
    
    Improved testing environment for zeppelin-web
    
    - added `test:watch` command for continuous testing 
    - displaying coverage report in console
    - e2e testing in zeppelin-web (can be written easily compare to the 
zeppelin-server integration tests. For example, check [home.spec.js]())
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [x] - `test:watch`
    * [x] - displaying coverage reports in console
    * [x] - e2e testing in zeppelin-web
    
    ### What is the Jira issue?
    
    [ZEPPELIN-2342](https://issues.apache.org/jira/browse/ZEPPELIN-2342)
    
    ### How should this be tested?
    
    CI should be green
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? - NO
    * Is there breaking changes for older versions? - NO
    * Does this needs documentation? - YES, updated


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/1ambda/zeppelin 
ZEPPELIN-2342/differentiate-unit-and-integration-testing

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2477.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2477
    
----
commit e70281bad21ea1d66b21acd6b5e33c84bfcf720f
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T06:38:49Z

    feat: Use spec repoter and coverage

commit 39dc77e4f3b9aab90c101e29a02cecf9a5696c11
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T07:03:29Z

    chore: Add test:watch command

commit 15473de6b59f8941562f1b6ae10f4c8b13dbaad2
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T08:29:23Z

    test: Add a basic e2e test for home

commit 76f4f584f4624a63edd5ec4fae09e5d44332bd41
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T08:33:20Z

    docs: Update test section in zeppelin-web/README.md

commit b5a17a4baf112e89c747d4b18fbff33f6d4a6551
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T09:26:50Z

    chore: Bind browser e2e test into CI process

commit 742bb961a2691e35084120ceca28639a13671a2f
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T09:40:37Z

    chore: Exclude e2e specs from RAT

commit eb447ef8ef199b72c0a613ecfaef60f55062a48c
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T10:20:44Z

    WIP: add -X log to selenium profioe

commit 2ed397331007e1c4863d983519a30afab958fbc8
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T11:18:03Z

    fix: set gecko false for webdriver manager. See 
https://github.com/angular/webdriver-manager/issues/216

commit 0907d7286dedd83df6afb5bfc11a57b682479c7f
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T11:18:16Z

    chore: Ingnore protractor conf in RAT

commit 0c09727e95fd1216d6113b53865171466a776852
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T12:04:17Z

    fix: Remove -X option from selenium profile

commit ca2b17034cddbc398dfac7eff0474ba6d5423f8a
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T13:07:52Z

    WIP: add -e mvn option to the second profile

commit 0c2c1ecbfb4a4c304788177e7e52b95ed8c84757
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T13:20:07Z

    chore: Add web-e2e profile to mvn

commit 7703615bc41c3be40d1d9f3315c59a9e072f0760
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T14:01:21Z

    WIP: Add -X to the second travis profile

commit 40ac076ebc78f206cdaf11fe61c5fde220dbc59a
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T16:28:54Z

    chore: New profile for e2e test only

commit f90deb4bf3db57e36232c9c94ae3b07dfd7c2331
Author: 1ambda <1am...@gmail.com>
Date:   2017-07-10T16:53:11Z

    chore: Move web e2e into zeppelin-web

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to