-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Selenium test for PR 26979 #27057
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
individual-it
wants to merge
18
commits into
owncloud:master
from
individual-it:selenium-test-for-PR-26979
Closed
Selenium test for PR 26979 #27057
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
4655413
added facebook selenium webdriver
individual-it 014465a
setup selenium tests env.
individual-it f1b4fa4
make travis run the selenium tests
individual-it 8d45e08
set propper test name
individual-it 28e52d9
user global namespace for WebDriverBy
individual-it a26ac55
run selenium tests ony when sauce connector is configured
individual-it ed4dc56
Whitespace
4cba2a9
restore admin file and folder to default
individual-it 6dcd270
Merge branch 'selenium-implementation' of https://github.com/individu…
individual-it 71936fd
adminLogin() for selenium tests
individual-it 2661d96
selenium test for PR #26979
individual-it 151375c
adminLogin description
8612a48
make the selenium test a travis testcase
individual-it 4399bab
add webdriver bindings as composer dependency
individual-it fbd00f0
update composer.lock for facebook webdriver
individual-it 3e3302d
better way of waiting
individual-it 13fbc37
fix code style & indent
individual-it 0387df5
Merge pull request #8 from individual-it/selenium-better-waiting
individual-it File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
run selenium tests ony when sauce connector is configured
only run the selenium tests whe SAUCE_USERNAME & SAUCE_ACCESS_KEY are configured. That way a PR from an external, that does not have access to the sauce env., will not trigger the selenium tests
- Loading branch information
commit a26ac5501ecfa3ad55fe43624eb75de2143e3624
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add this as a test case just like we do with caldav, carddav.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is to prevent the tests to run if a PR comes from a remote fork.
So if we make it a test-case by setting TEST_SELENIUM=1 and the sauce_connector is setup in owncloud/core and I make a fork to individual-it/core commit something and make a PR. Travis would try to build that PR but the selenium tests would fail because $SAUCE_USERNAME & $SAUCE_ACCESS_KEY are not set
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that part - we can still make this work (somehow ;-) )
But on travis I'd like to see an explicit job with TC=selenium listed