Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for testingbot #77

Closed
occupant23 opened this issue Mar 26, 2019 · 3 comments
Closed

Support for testingbot #77

occupant23 opened this issue Mar 26, 2019 · 3 comments
Assignees
@wurzelkuchen @occupant23
Labels
bug codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop feature Medium Priority
Milestone
v3.2.x

Comments

@occupant23
Copy link
Contributor

We want to enable our users to use also testingbot beside saucelabs as a test environment.
@occupant23 occupant23 modified the milestones: backlog, v3.1.x Mar 26, 2019
@occupant23 occupant23 added docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop Medium Priority labels Mar 26, 2019
occupant23 pushed a commit that referenced this issue Mar 26, 2019
#77 - added screen-resolution key in browser configuration for tesingbot
c72f7e4
@wurzelkuchen
Copy link
Contributor

Currently the chorme emulation profiles do not work with testingbot/saucelabs.
The MetaData states that goog:chromeOptions and args are empty.

occupant23 pushed a commit that referenced this issue Apr 17, 2019
Merge branch 'develop' into #77-support-for-testingbot
8398f88
occupant23 pushed a commit that referenced this issue Apr 18, 2019
#77 - fixed an issue that prevented chrome device emulation in test e…
9782f0e 
…nvironments
@occupant23 occupant23 added the codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there label Apr 18, 2019
@occupant23
Copy link
Contributor Author

merged back into develop, ready for test

occupant23 pushed a commit that referenced this issue Apr 23, 2019
#77 - fixed an issue that now prevented chrome device emulation in lo…
511c3f9 
…cal environments
@wurzelkuchen wurzelkuchen added the codeDone The issue is rechecked for development branch label Apr 23, 2019
@wurzelkuchen
Copy link
Contributor

rechecked feature

@occupant23 occupant23 added the bug label Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wurzelkuchen wurzelkuchen

@occupant23 occupant23

Labels
bug codeDone The issue is rechecked for development branch codeReadyForRecheck The issue is fixed/implemented AND merged into development, but needs to be rechecked there docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop feature Medium Priority
Projects
None yet
Milestone
v3.2.x
Development

No branches or pull requests
2 participants
@wurzelkuchen @occupant23