cloud_test 1.0.7

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 0e54f6db87dc6d73250de4fe7b8421047f82d27258c19ca183ba96d5b49fd223
+  data.tar.gz: f8bb10fb48dbdfd5f5bd92b340ce2cd849cf0883b2c6b474f4e01f048f4637ce
+SHA512:
+  metadata.gz: d49edd847bb9cd38ce64da6d3d00dd504155a47dbe01bc3359001703b85e16a0513454e679ea64cd5ee24e0724b23b18c061161b3642476ff1207b849eabcfe1
+  data.tar.gz: 00ae253946c212896116ec06e1700278f643a4bd927180cfedab4de39a4db37a1ee2941fc2c273c08cc6ccec1ee25055ea4cb58ff5b9d2fae883391d96bb427b

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/.idea/

data/.ruby-version

@@ -0,0 +1 @@
+2.5

data/.travis.yml

@@ -0,0 +1,7 @@
+---
+sudo: false
+language: ruby
+cache: bundler
+rvm:
+  - 2.5.0
+before_install: gem install bundler -v 2.0.1

data/CHANGELOG.md

@@ -0,0 +1,38 @@
+#Changelog
+
+## 1.0.7
+
+- bug fixes for browserstack
+## 1.0.6
+
+- rename `cloud_test start` to `cloud_test cucumber`
+- rename sample cucumber tag `@cloudtest` to `@cloud_test`
+- improve the upload api, make it more explicit with named params
+## 1.0.5
+
+- improve the README.md
+## 1.0.4
+
+- add CHANGELOG.md
+
+## 1.0.3
+
+- improve provider specific sample configuration
+
+## 1.0.2
+
+- some bug fixes in the crossbrowsertesting configuration sample file
+
+## 1.0.1
+
+- Bug fixes for crossbrowsertesting
+
+## 1.0
+
+- Github realese
+- add `cloud_test -v` command
+
+## 0.11.5
+
+- add `cloud_test generate -p PROVIDER` option
+- upload the fail status to crossbrowsertesting dashboard

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at philipp.haeusele@makandra.de. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in cloud_test.gemspec
+gemspec
+gem 'browserstack-local'
+gem 'cucumber', '~> 1.3.20'

data/Gemfile.lock

@@ -0,0 +1,83 @@
+PATH
+  remote: .
+  specs:
+    cloud_test (1.0.7)
+      capybara
+      cucumber
+      thor
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.6.0)
+      public_suffix (>= 2.0.2, < 4.0)
+    aruba (0.14.10)
+      childprocess (>= 0.6.3, < 1.1.0)
+      contracts (~> 0.9)
+      cucumber (>= 1.3.19)
+      ffi (~> 1.9)
+      rspec-expectations (>= 2.99)
+      thor (~> 0.19)
+    browserstack-local (1.3.0)
+    builder (3.2.3)
+    capybara (3.26.0)
+      addressable
+      mini_mime (>= 0.1.3)
+      nokogiri (~> 1.8)
+      rack (>= 1.6.0)
+      rack-test (>= 0.6.3)
+      regexp_parser (~> 1.5)
+      xpath (~> 3.2)
+    childprocess (1.0.1)
+      rake (< 13.0)
+    contracts (0.16.0)
+    cucumber (1.3.20)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.12)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.1.2)
+    diff-lcs (1.3)
+    ffi (1.11.1)
+    gherkin (2.12.2)
+      multi_json (~> 1.3)
+    mini_mime (1.0.2)
+    mini_portile2 (2.4.0)
+    minitest (5.11.3)
+    multi_json (1.13.1)
+    multi_test (0.1.2)
+    nokogiri (1.10.3)
+      mini_portile2 (~> 2.4.0)
+    public_suffix (3.1.1)
+    rack (2.0.7)
+    rack-test (1.1.0)
+      rack (>= 1.0, < 3)
+    rake (10.5.0)
+    regexp_parser (1.6.0)
+    rspec-expectations (3.8.4)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.2)
+    rubyzip (1.2.3)
+    selenium-webdriver (3.142.3)
+      childprocess (>= 0.5, < 2.0)
+      rubyzip (~> 1.2, >= 1.2.2)
+    thor (0.20.3)
+    xpath (3.2.0)
+      nokogiri (~> 1.8)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  browserstack-local
+  bundler (~> 2.0)
+  cloud_test!
+  cucumber (~> 1.3.20)
+  minitest (~> 5.0)
+  rake (~> 10.0)
+  selenium-webdriver
+
+BUNDLED WITH
+   2.0.2

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Philipp Häusele
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,184 @@
+# cloud_test
+
+cloud_test enables local Cloud-Testing for a number of providers:
+- Browserstack
+- CrossBrowserTesting
+- saucelabs
+- lambdatest
+
+The intention of this gem is to quickly enable Cloud-Testing with minimal setup required.
+It assumes your are using capybara and selenium.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'cloud_test'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install cloud_test
+## Configuration
+You can configure cloud_test in the
+
+    config/cloud_test.yml file 
+    
+The minimal config includes a 'key' and a 'user' value (which may be or not be
+ the login credentials for the chosen provider), as well
+as 'provider' value. 
+ Additional key/value pairs are possible, for example to configure the browser.
+
+- [Browserstack Configurator](https://www.browserstack.com/automate/capabilities)
+- [CrossBrowserTesting Capabilities](https://help.crossbrowsertesting.com/selenium-testing/getting-started/crossbrowsertesting-automation-capabilities/)
+- [Saucelabs Configurator](https://wiki.saucelabs.com/display/DOCS/Platform+Configurator#/)
+- [lambdatest Capability Generator](https://www.lambdatest.com/capabilities-generator/)
+
+You can generate the following example config file to the config folder with:
+
+    [bundle exec] cloud_test generate [-p PROVIDER]
+    
+Example cloud_test.config.yml:
+
+    #config/cloud_test.yml 
+    provider: "browserstack"
+    user: "username" # these may not be the login credentials
+    key: "password"
+    cloud_test_debug: false
+    common_caps:
+      "acceptSslCerts": true # allow self signed certificates
+    browserstack: #optional block
+      "browserstack.local": true
+      "browserstack.debug": true # Visual log
+    browsers:
+      IE:
+        "browser": "IE"
+        "browser_version": "11.0"
+        "os": "Windows"
+        "os_version": "7"
+      CHROME:
+        "browser": "chrome"
+        "browser_version": "75.0"
+        "os": "Windows"
+    cucumber_tag: "@cloudtest"
+
+You can choose a specific browser configuration by setting the CLOUD_TEST 
+env variable to your preconfigured browser settings by:
+    
+    export CLOUD_TEST=<BROWSER_CONFIG>
+    # or
+    CLOUD_TEST=<BROWSER_CONFIG> cucumber
+The _provider_ Hash can include specific configuration only for that provider,
+ common_caps and browser_caps are provider independent. 
+ 
+ NOTE: Theses capabilities may still be slightly different for each provider.
+If you set the cloud_test_debug key to true cloud_test will display some additional
+details.
+ 
+And these are the defaults and possible env variable settings:
+
+    [bundle exec] cloud_test list-default-caps PROVIDER
+    # will show something like this:
+
+    ENV['CLOUDTEST_PROJECT'] || # folder name
+    ENV['CLOUDTEST_BUILD'] ||  `git rev-parse HEAD` # HEAD commit hash
+    ENV['CLOUDTEST_NAME'] || `git log -1 --pretty=%B` # HEAD commit message
+    ENV['CLOUDTEST_OS'] || '10'
+    ENV['CLOUDTEST_PLATFORM'] || 'WINDOWS'
+    ENV['CLOUDTEST_BROWSER'] || 'CHROME'
+    
+Additionally you can do a dry run and show the "real" capabilities:
+
+    [bundle exec] cloud_test list-caps PROVIDER
+          
+## Usage
+You do need a config file, read the configuration section above first.
+You need to run the specific tunnel app for each provider in order to setup local testing.
+Links:
+
+- Browserstack tunnel should be installed as a 
+[gem](https://github.com/browserstack/browserstack-local-ruby),
+ so add gem 'browserstack-local' to your gemfile. ([Tunnel Binary](https://s3.amazonaws.com/browserStack/browserstack-local/BrowserStackLocal-linux-x64))
+- [CrossBrowserTesting tunnel](https://github.com/crossbrowsertesting/cbt-tunnel-nodejs/releases)
+- [Saucelabs tunnel](https://wiki.saucelabs.com/display/DOCS/Setting+Up+Sauce+Connect+Proxy)
+- [Lambdatest tunnel](https://s3.amazonaws.com/lambda-tunnel/LT_Linux.zip)
+
+Download the one for your provider and operating system.
+Extract the executable and run it. The command should be similar to:
+
+    ./<path_to>/<tunnel> -u <username> -k <password|apikey>
+
+To enable Cloud_Testing you need to set the ENV['CLOUD_TEST'] variable to any value. 
+
+    export CLOUD_TEST=IE
+    # or
+    CLOUD_TEST=IE cucumber 
+The value can be a browser_caps configuration key (e.g. IE, chrome, my_ie_browser_config), and must be defined in the config file.
+
+
+Additionally you need to require 'cloud_test' and set the capybara driver in the
+ features/support/cloud_test.rb file as follows, it can be generated automatically if you run:
+ 
+    [bundle exec] cloud_test generate [-p PROVIDER]
+ 
+
+    require 'cloud_test'
+ 
+    if CloudTest.enabled?
+      Before do
+        Capybara.current_driver = :cloud_test
+      end
+      After do |scenario|
+          if scenario.failed?
+              CloudTest.upload_status_to_provider true, page.driver.browser.session_id, scenario.exception
+          end
+        end
+    end
+NOTE: cloud_test registers a Capybara driver named ':cloud_test'.
+
+The After hook updates the status in the dashboard of your provider. 
+Currently this is implemented for browserstack and crossbrowsertesting.
+
+If you want to test your whether your login credentials work, you can use the
+following command:
+
+    [bundle exec] cloud_test test-connection
+    
+To automate things even further you can define a cucumber tag in the config file 
+(default: '@cloudtest'), tag all scenarios you wish to run and run the following command:
+
+    [bundle exec] cloud_test cucumber [-q]
+This command will run all tagged scenarios sequantially with all browser configurations
+defined in the 'browsers' list in your config file. It runs the following command for each browser:
+
+    CLOUD_TEST=<browser_config_name> bundle exec cucumber -t <cucumber_tag>
+You can also use the following command to execute your own test-command:
+
+    [bundle exec] cloud_test each [-q] <run> <your> <test-suite> 
+
+You can get a list of all available commands with a description if you run:
+    
+    [bundle exec] cloud_test
+    
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/makandra/cloud_test. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Cloudtest project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/cloud_test/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,10 @@
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/*_test.rb"]
+end
+
+task :default => :test