GitHub user soralee reopened a pull request:

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

    [ZEPPELIN-2661] Test: personalized mode action

    ### What is this PR for?
    Adding to personalized mode action case on Selenium test.
    Here is for checking scenario.
    
    1. (admin) login, create a new note, run a paragraph with 'Before' text, 
turn on personalized mode, logout.
               > checkpoint : result of paragraph is 'Before'.
    
    2. (user1) login, make sure it is on personalized mode and 'Before' in 
result of paragraph, logout.
               > checkpoint 1 : enabling personalized mode
               > checkpoint 2 : result of paragraph is 'Before'.
    
    3. (admin) login, run after changing paragraph contents to 'After', check 
result of paragraph, logout.
               > checkpoint : changed from 'Before' to 'After' in paragraph 
result.
    
    4. (user1) login, check whether result of paragraph is 'Before' or not.
               > checkpoint : result of paragraph is 'Before', 'After' means 
test fail.
    
    
    ### What type of PR is it?
    [ Test ]
    
    
    ### What is the Jira issue?
    * [ZEPPELIN-2661](https://issues.apache.org/jira/browse/ZEPPELIN-2661)
    
    ### How should this be tested?
    - build zeppelin with `mvn clean package -DskipTests'
    - execute `TEST_SELENIUM="true" mvn test -pl 'zeppelin-server' --am 
-DfailIfNoTests=false -Dtest=PersonalizeActionsIT#testActionPersonalizedMode`
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


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

    $ git pull https://github.com/soralee/zeppelin personalize_mode_test

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

    https://github.com/apache/zeppelin/pull/2415.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 #2415
    
----
commit 38e467c12397985303af372d6bd98319fdc93bdf
Author: soralee <sora0...@zepl.com>
Date:   2017-06-16T03:32:27Z

    personalize mode integration test

commit 2752104cc3ee46dd7b1b17a4551fbe7b773c007e
Author: soralee <sora0...@zepl.com>
Date:   2017-06-16T05:34:02Z

    test: add to check point about being turned on personalized mode in user1

commit 2ddfd8cbbfb1a874fb5e4f9857bc51d9ef986c06
Author: soralee <sora0...@zepl.com>
Date:   2017-06-16T05:41:43Z

    style: added new line

commit 8d17a64c5af9bb6b7ef0551b5e7f981a97fb1596
Author: soralee <sora0...@zepl.com>
Date:   2017-06-16T06:15:23Z

    style: [minor] modify annotation

commit 8690eb28144f4c70ba9b28b20cac60be0ece42ab
Author: soralee <sora0...@zepl.com>
Date:   2017-06-16T06:34:26Z

    style: modify method name

commit 7d9be043bc3101198fcf7fa434b7c3b540fa0ecc
Author: soralee <sora0...@zepl.com>
Date:   2017-06-19T08:56:14Z

    fix: using minimum 'sleep' method

----


---
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