rspec_multi_env 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 64eba1573f751be9b6d7c2f11794223faecdb4f3
+  data.tar.gz: 6d9a81243528d3b751276383ade1b589652f08b0
+SHA512:
+  metadata.gz: 3ad016b210ae04119274931ad8eec8b2b47b8e6c7b36e86aee4891ed3733aec7ba9baae93fe328a2b878be93c11ffcd7266323f59d0e9b625ef2308a7fc9b10f
+  data.tar.gz: 87cd64eda77720633ed05bcf1191222600e176bf61fa02e1a34aba489e965c477fe0fc2ccc3af3df938eec957e9cc58eee8ef3c472ac85c1b99b26050b94de96

data/.gitignore

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

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 sohan39@gmail.com. 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"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in rspec_multi_env.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,20 @@
+PATH
+  remote: .
+  specs:
+    rspec_multi_env (1.0.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    rake (10.5.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.17)
+  rake (~> 10.0)
+  rspec_multi_env!
+
+BUNDLED WITH
+   1.17.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 smsohan
+
+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,71 @@
+# RspecMultiEnv
+
+If you're using RSpec as your technology for testing an app in
+multiple environments, you'll likely need a uniform way to configure
+the environment specific variable within your tests. This gem
+simplifies the process with a DSL.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'rspec_multi_env'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install rspec_multi_env
+
+## Usage
+
+```ruby
+describe 'Your Test' do
+  before(:all) do
+    environment :sandboxed do
+      #... custom code/configuration
+    end
+
+    environment :staging do
+      #... custom code/configuration
+    end
+  end
+
+  # rest of your tests that use the env specific config
+end
+```
+
+```bash
+$ RSPEC_ENV=sandboxed bin/rspec
+$ RSPEC_ENV=staging bin/rspec
+```
+
+## Features
+
+1. Works with parallel_tests, just pass the same `RSPEC_ENV`
+   variable.
+2. If an environment is missing in a spec, the tests are marked pending
+   when the suite is executed.
+
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. 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/smsohan/rspec_multi_env. 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 RspecMultiEnv project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/rspec_multi_env/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "rspec_multi_env"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/rspec_multi_env/dsl.rb

@@ -0,0 +1,10 @@
+module RspecMultiEnv
+  module DSL
+    def environment(env_name)
+      EnvironmentConfiguration.instance.register env_name
+      if EnvironmentConfiguration.instance.current?(env_name)
+        yield
+      end
+    end
+  end
+end

data/lib/rspec_multi_env/environment_configuration.rb

@@ -0,0 +1,30 @@
+module RspecMultiEnv
+  class EnvironmentConfiguration
+    include Singleton
+    attr_accessor :environments
+
+    def reset
+      @environments = []
+    end
+
+    def register(name)
+      @environments << name
+    end
+
+    def registered?(name)
+      @environments.include?(name)
+    end
+
+    def current?(env)
+      current == env.to_sym
+    end
+
+    def current_environment_registered?
+      registered?(current)
+    end
+
+    def current
+      ENV['RSPEC_ENV'].to_sym
+    end
+  end
+end

data/lib/rspec_multi_env/hooks.rb

@@ -0,0 +1,15 @@
+RSpec.configure do |config|
+  config.include RspecMultiEnv::DSL
+
+  config.before(:all) do
+    RspecMultiEnv::EnvironmentConfiguration.instance.reset
+  end
+
+  config.around(:example) do |example|
+    if RspecMultiEnv::EnvironmentConfiguration.instance.current_environment_registered?
+      example.run
+    else
+      example.skip
+    end
+  end
+end

data/lib/rspec_multi_env/version.rb

@@ -0,0 +1,3 @@
+module RspecMultiEnv
+  VERSION = "1.0.0"
+end

data/lib/rspec_multi_env.rb

@@ -0,0 +1,7 @@
+require "rspec_multi_env/version"
+require "rspec_multi_env/environment_configuration"
+require "rspec_multi_env/dsl"
+require "rspec_multi_env/hooks"
+
+module RspecMultiEnv
+end

data/rspec_multi_env.gemspec

@@ -0,0 +1,37 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "rspec_multi_env/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "rspec_multi_env"
+  spec.version       = RspecMultiEnv::VERSION
+  spec.authors       = ["smsohan"]
+  spec.email         = ["sohan39@gmail.com"]
+
+  spec.summary       = %q{Allows the same set of tests to run against multiple environments}
+  spec.description   = %q{If you want to run a suite of tests against multiple sets of environments, you can use this gem to simplify the setup}
+  spec.homepage      = "https://github.com/smsohan/rspec_multi_env"
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  if spec.respond_to?(:metadata)
+    spec.metadata["allowed_push_host"] = "https://rubygems.org"
+
+    spec.metadata["homepage_uri"] = spec.homepage
+    spec.metadata["source_code_uri"] = "https://github.com/smsohan/rspec_multi_env"
+  end
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.17"
+  spec.add_development_dependency "rake", "~> 10.0"
+end

metadata

@@ -0,0 +1,91 @@
+--- !ruby/object:Gem::Specification
+name: rspec_multi_env
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- smsohan
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2018-11-20 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.17'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.17'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+description: If you want to run a suite of tests against multiple sets of environments,
+  you can use this gem to simplify the setup
+email:
+- sohan39@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/rspec_multi_env.rb
+- lib/rspec_multi_env/dsl.rb
+- lib/rspec_multi_env/environment_configuration.rb
+- lib/rspec_multi_env/hooks.rb
+- lib/rspec_multi_env/version.rb
+- rspec_multi_env.gemspec
+homepage: https://github.com/smsohan/rspec_multi_env
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+  homepage_uri: https://github.com/smsohan/rspec_multi_env
+  source_code_uri: https://github.com/smsohan/rspec_multi_env
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.5.2.1
+signing_key: 
+specification_version: 4
+summary: Allows the same set of tests to run against multiple environments
+test_files: []