test_workflow 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c53489fbc2c38d6b23e5862bf693db730ebcec33
+  data.tar.gz: c7c6408cf7d834de2c0695d1976d76f1361ca456
+SHA512:
+  metadata.gz: ad82e427ba320539336819fe7f3da69b975559c306168f4d22bb21b41c39306e3a9b8899973d0fd23fed92fe3993b5330fe98ce56494aa0b86121e3c4ddfda79
+  data.tar.gz: 1ca5acf697fd1c5ca8b44a2ff7a77abeedc491e8c555173def6fffc071d8947cec2b6cd0182f5ffda9a242c8f5789e46d958f73bad35499a61eb8305d3a58da5

data/.gitignore

@@ -0,0 +1,40 @@
+# Ruby-Specific
+
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+
+# Ouput-Specific
+
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+*.log
+*.tmp
+*.swp
+*.bak
+
+# IDE-Specific
+
+.idea
+.settings
+.project
+.classpath
+*.iws
+
+# Windows-Specific
+
+Thumbs.db
+
+# Mac OS-Specific
+
+*.DS_Store
+._*
+
+# Linux-Specific
+
+.directory
+.Trash-*

data/.hound.yml

@@ -0,0 +1,62 @@
+AllCops:
+  Exclude:
+    - test_workflow.gemspec
+    - test/*.rb
+    - spec/**/*
+
+# Removing need for frozen string literal comment.
+Style/FrozenStringLiteralComment:
+  Enabled: false
+
+# Removing the preference for string single quotes.
+Style/StringLiterals:
+  Enabled: false
+
+# Missing top-level module documentation comment.
+Style/Documentation:
+  Enabled: false
+
+# Prefer reduce over inject.
+Style/CollectionMethods:
+  PreferredMethods:
+    reduce: 'inject'
+
+# Use each_with_object instead of inject.
+Style/EachWithObject:
+  Enabled: false
+
+# Prefer fail over raise.
+Style/SignalException:
+  Enabled: false
+
+# This never works for validations.
+Style/AlignHash:
+  EnforcedLastArgumentHashStyle: ignore_implicit
+
+# Align multi-line params with previous line.
+Style/AlignParameters:
+  EnforcedStyle: with_fixed_indentation
+
+# Indent `when` clause one step from `case`.
+Style/CaseIndentation:
+  IndentOneStep: true
+
+# Don't force bad var names for reduce/inject loops.
+Style/SingleLineBlockParams:
+  Enabled: false
+
+# For method chains, keep the dot with the method name.
+Style/DotPosition:
+  EnforcedStyle: leading
+
+# Stop nesting so hard.
+Metrics/BlockNesting:
+  Max: 2
+
+# Encourage short methods.
+Metrics/MethodLength:
+  Max: 10
+
+# Encourage fewer parameters.
+Metrics/ParameterLists:
+  Max: 4

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,2 @@
+inherit_from:
+  - .hound.yml

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3.1
+before_install: gem install bundler -v 1.13.3

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 jeffnyman@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,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in test_workflow.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016 Jeff Nyman
+
+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,260 @@
+# TestWorkflow
+
+[![Gem Version](https://badge.fury.io/rb/test_workflow.svg)](http://badge.fury.io/rb/test_workflow)
+[![License](http://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/jnyman/test_workflow/blob/master/LICENSE.txt)
+
+TestWorkflow implements the idea of traversing a set of activities in the context of a user workflow.
+
+## Installation
+
+To get the latest stable release, add this line to your application's Gemfile:
+
+```ruby
+gem 'test_workflow'
+```
+
+And then include it in your bundle:
+
+    $ bundle
+
+You can also install TestWorkflow just as you would any other gem:
+
+    $ gem install test_workflow
+
+## Usage
+
+The core operation of the TestWorkflow is a path. A workflow can have different paths. A path is an array of actions. These actions consist of a class a method on that class. Parameters can also be passed to the methods. The idea here is that the class is acting as context object for test execution. That class may be a page object, a screen object, a service object, and so on.
+
+### Paths
+
+Here's an example of a workflow class with a path:
+
+```ruby
+PurchaseFromAmazon.paths = {
+  :default => [
+    [AmazonSearch, :search_for, "Star Wars"],
+    [AmazonProduct, :add_to_cart, "Vector Prime"],
+    [AmazonCart, :checkout]
+  ]
+}
+```
+
+Notice how some of the paths are passing arguments to the methods.
+
+Now to run that workflow up to the last point, you could do this:
+
+```ruby
+path_to(AmazonCart)
+```
+
+This would run the workflow _up to_ the AmazonCart, starting with AmazonSearch and moving on down the list. Note that the first argument is a context definition (i.e., AmazonSearch), the second is a method on that context definition (i.e., :search_for) and the the third item is an optional argument to pass to that method.
+
+Symbiote will always assume there is a default path, and will complain if there is not one. But you can have a different workflow as such:
+
+```ruby
+PurchaseFromAmazon.paths = {
+  :default => [
+    [AmazonSearch, :search_for, "Star Wars"],
+    [AmazonProduct, :add_to_cart, "Vector Prime"],
+    [AmazonCart, :checkout]
+  ],
+
+  :trekking => [
+    [AmazonSearch, :search_for, "Star Trek"],
+    [AmazonProduct, :add_to_cart, "Engines of Destiny"],
+    [AmazonCart, :checkout]
+  ]
+}
+```
+
+Now you can specify that you want to use that different path:
+
+```ruby
+path_to(AmazonCart, using: :trekking)
+```
+
+So what you can see here is that you can navigate to a particiular context traversing through all other contexts along the way. The use of the term "context" is deliberate because the workflow could be the traversal of a series of pages. Thus the contexts would be page objects. But the workflow could also be a series of API calls, which means the contexts might be service objects.
+
+### Examples
+
+Consider the following setup:
+
+```ruby
+require "test_workflow"
+
+class AmazonSearch
+  def search_for(product)
+    puts "AmazonSearch - search_for: #{product}"
+  end
+end
+
+class AmazonProduct
+  def add_to_cart(product)
+    puts "AmazonProduct - add_to_cart: #{product}"
+  end
+end
+
+class AmazonCart
+  def checkout
+    puts "AmazonCart - checkout"
+  end
+end
+
+class PurchaseFromAmazon
+  include TestWorkflow
+
+  def on(caller)
+    caller.new
+  end
+end
+```
+
+The `on` method here is critical. This is a part of the API that is exposed by TestWorkflow. What this means is that you should implement this method so that context calls can be made.
+
+You can then do the following:
+
+```ruby
+PurchaseFromAmazon.paths = {
+  :default => [
+          [AmazonSearch, :search_for, "Star Wars"],
+          [AmazonProduct, :add_to_cart, "Vector Prime"],
+          [AmazonCart, :checkout]
+      ]
+}
+
+testing = PurchaseFromAmazon.new
+testing.path_to(AmazonCart)
+```
+
+That would lead to output like this:
+
+    AmazonSearch - search_for: Star Wars
+    AmazonProduct - add_to_cart: Vector Prime
+
+You can see the logic is running up to the AmazonCart part of the path. That is by design. You could change that last line to this:
+
+```ruby
+testing.path_to(AmazonCart, from: AmazonProduct)
+```
+
+That would lead to this output:
+
+    AmazonProduct - add_to_cart: Vector Prime
+
+Here you are saying you want to run the path starting from a particular point in the path.
+
+Let's add a second path to the workflow:
+ 
+```ruby
+PurchaseFromAmazon.paths = {
+  :default => [
+          [AmazonSearch, :search_for, "Star Wars"],
+          [AmazonProduct, :add_to_cart, "Vector Prime"],
+          [AmazonCart, :checkout]
+      ],
+  :trekking => [
+          [AmazonSearch, :search_for, "Star Trek"],
+          [AmazonProduct, :add_to_cart, "Engines of Destiny"],
+          [AmazonCart, :checkout]
+      ]
+}
+
+testing = PurchaseFromAmazon.new
+testing.path_to(AmazonCart, from: AmazonProduct, using: :trekking)
+```
+
+The output from this would be:
+
+    AmazonProduct - add_to_cart: Engines of Destiny
+
+Here I'm not only running from a particular point on the path but I'm using a specific path as well.
+
+You can also override the method call. For example, try this:
+
+```ruby
+testing.path_to(AmazonProduct).add_to_cart('testing')
+```
+
+This would lead to this output:
+
+    AmazonSearch - search_for: Star Wars
+    AmazonProduct - add_to_cart: testing
+
+Notice here how the argument passed in is not the default one from the path but the one you specified.
+
+You can also run the entire path by doing this:
+
+```ruby
+testing.entire_path
+```
+
+You'll note here that I've defined the paths outside of the workflow class, but you can easily do otherwise, as such:
+
+You can also continue executing a path that you previously started. Consider this logic:
+
+```ruby
+testing = PurchaseFromAmazon.new
+
+testing.path_to(AmazonProduct)
+testing.current_context = AmazonProduct.new
+
+# Do some other logic here.
+puts "Other Logic Happens Here."
+
+testing.continue_path_to(AmazonCart)
+```
+
+The output would be:
+
+    AmazonSearch - search_for: Star Wars
+    Other Logic Happens Here.
+    AmazonProduct - add_to_cart: Vector Prime
+
+What this is showing you is that a path can be started, then other work can be done, and then the path can be re-entered at a particular starting point. Key to this is the use of `current_context` which you would want to define on any of your classes that include TestWorkflow. For example, with the above logic you would have:
+
+```ruby
+class PurchaseFromAmazon
+  include TestWorkflow
+
+  attr_accessor :current_context
+  # ...
+end
+```
+
+You have to maintain the `@current_context` instance variable which should always point to the current object in the workflow path. This gives you a minimal way to control the execution of paths by executing them up to a point, interleaving other activities you might want to perform, and then continuing on from where you left off.
+
+### Code Considerations
+
+From a code perspecive, `path_to` is a key method. It takes in a context as well as a path. That path will be a hash that contains two elements. One of the elements is the key :using. This is what is used to lookup the path to traverse. You can see that in the example above. This key will have a default value of :default. The second key that can be specified is :visit. This specifies whether the execution context should be specifically set up, as opposed to assuming that the context already exists. The default value of :visit is false.
+
+Another method to be aware of is `entire_path`, which was covered above. This is used to traverse through a complete workflow based on the paths, executing any methods specified.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec:all` 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`.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at [https://github.com/jnyman/test_workflow](https://github.com/jnyman/test_workflow). The testing ecosystem of Ruby is very large and this project is intended to be a welcoming arena for collaboration on yet another testing tool. As such, contributors are very much welcome but are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+To contribute to TestWorkflow:
+
+1. [Fork the project](http://gun.io/blog/how-to-github-fork-branch-and-pull-request/).
+2. Create your feature branch. (`git checkout -b my-new-feature`)
+3. Commit your changes. (`git commit -am 'new feature'`)
+4. Push the branch. (`git push origin my-new-feature`)
+5. Create a new [pull request](https://help.github.com/articles/using-pull-requests).
+
+## Author
+
+* [Jeff Nyman](http://testerstories.com)
+
+## Credits
+
+This code is loosely based upon the [PageNavigation](https://github.com/cheezy/page_navigation) gem. The rationale for a new version is that tying the project to "page navigation" in particular is limiting, particularly since workflow-based patterns (like journey and screenplay) are often much more effective from a testing standpoint.
+
+## License
+
+TestWorkflow is distributed under the [MIT](http://www.opensource.org/licenses/MIT) license.
+See the [LICENSE](https://github.com/jnyman/test_workflow/blob/master/LICENSE.txt) file for details.
+

data/Rakefile

@@ -0,0 +1,31 @@
+#!/usr/bin/env rake
+require "bundler/gem_tasks"
+require "rdoc/task"
+require "rubocop/rake_task"
+require "rspec/core/rake_task"
+
+RuboCop::RakeTask.new
+
+namespace :spec do
+  desc 'Clean all generated reports'
+  task :clean do
+    system('rm -rf spec/reports')
+  end
+
+  RSpec::Core::RakeTask.new(all: :clean) do |config|
+    options  = %w(--color)
+    options += %w(--format documentation)
+    options += %w(--format html --out spec/reports/unit-test-report.html)
+
+    config.rspec_opts = options
+  end
+end
+
+Rake::RDocTask.new do |rdoc|
+  rdoc.rdoc_dir = 'doc'
+  rdoc.main = 'README.md'
+  rdoc.title = "TestWorkflow #{TestWorkflow::VERSION}"
+  rdoc.rdoc_files.include('README*', 'lib/**/*.rb')
+end
+
+task default: ['spec:all', :rubocop]

data/bin/console

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "test_workflow"
+
+# 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.
+
+require "pry"
+Pry.start

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/test_workflow.rb

@@ -0,0 +1,108 @@
+require "test_workflow/version"
+
+require "data_builder"
+
+module TestWorkflow
+  module Paths
+    def paths
+      @paths
+    end
+
+    def paths=(path)
+      @paths = path
+      raise("You must provide a default workflow path") unless paths[:default]
+      @paths
+    end
+  end
+
+  def self.included(caller)
+    caller.extend Paths
+    @caller = caller
+  end
+
+  def self.caller
+    @caller
+  end
+
+  # Provides an execution path for a given workflow path, using a specific
+  # definition that is part of that workflow path.
+  def path_to(context, keys = { using: :default, visit: false }, &block)
+    keys[:using] = :default unless keys[:using]
+    keys[:visit] = false unless keys[:visit]
+
+    path, path_goal = path_trail(keys, context)
+
+    return on(context, &block) if path_goal == -1
+
+    path_start = keys[:from] ? path_start_point(path, keys) : 0
+    execute_path(path[path_start..path_goal], keys[:visit])
+
+    on(context, &block)
+  end
+
+  alias path_up_to     path_to
+  alias workflow_to    path_to
+  alias workflow_up_to path_to
+
+  # Provides an execution path that starts execution of a given path
+  # from the standpoint of the "current context", which is something
+  # that must be set as part of execution logic.
+  def continue_path_to(context, keys = { using: :default }, &block)
+    path = workflow_path_for(keys)
+    path_start = find_index_for(path, @current_context.class)
+    path_end = find_index_for(path, context) - 1
+
+    if path_start == path_end
+      execute_path([path[path_start]], false)
+    else
+      execute_path(path[path_start..path_end], false)
+    end
+
+    on(context, &block)
+  end
+
+  # Provides an execution path for an entire workflow path.
+  def entire_path(keys = { using: :default, visit: false })
+    path_workflow = workflow_path_for(keys)
+    execute_path(path_workflow[0..-1], keys[:visit])
+  end
+
+  alias run_entire_path entire_path
+  alias run_full_path   entire_path
+
+  private
+
+  def path_trail(keys, context)
+    path = workflow_path_for(keys)
+    goal = find_index_for(path, context) - 1
+    [path, goal]
+  end
+
+  def path_start_point(path, keys)
+    path.find_index { |item| item[0] == keys[:from] }
+  end
+
+  def workflow_path_for(keys)
+    path = TestWorkflow.caller.paths[keys[:using]]
+    raise("The path named '#{keys[:using]}' was not found.") unless path
+    path
+  end
+
+  def execute_path(path, visit)
+    path.each do |definition, action, *args|
+      context = visit ? visit(definition) : on(definition)
+      visit = false
+
+      unless context.respond_to?(action)
+        raise("Path action '#{action}' not defined on '#{definition}'.")
+      end
+
+      context.__send__ action unless args
+      context.__send__ action, *args if args
+    end
+  end
+
+  def find_index_for(path, context)
+    path.find_index { |item| item[0] == context }
+  end
+end

data/lib/test_workflow/version.rb

@@ -0,0 +1,3 @@
+module TestWorkflow
+  VERSION = "0.1.0".freeze
+end

data/test_workflow.gemspec

@@ -0,0 +1,35 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'test_workflow/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "test_workflow"
+  spec.version       = TestWorkflow::VERSION
+  spec.authors       = ["Jeff Nyman"]
+  spec.email         = ["jeffnyman@gmail.com"]
+
+  spec.summary       = %q{Chains classes and methods as a path to execute in a workflow.}
+  spec.description   = %q{Chains classes and methods as a path to execute in a workflow.}
+  spec.homepage      = "https://github.com/jnyman/test_workflow"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |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.13"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+  spec.add_development_dependency "rubocop"
+  spec.add_development_dependency "pry"
+
+  spec.post_install_message = %{
+(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
+  TestWorkflow #{TestWorkflow::VERSION} has been installed.
+(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
+  }
+end

metadata

@@ -0,0 +1,131 @@
+--- !ruby/object:Gem::Specification
+name: test_workflow
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Jeff Nyman
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2016-10-19 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.13'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.13'
+- !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'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: pry
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Chains classes and methods as a path to execute in a workflow.
+email:
+- jeffnyman@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".hound.yml"
+- ".rspec"
+- ".rubocop.yml"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/test_workflow.rb
+- lib/test_workflow/version.rb
+- test_workflow.gemspec
+homepage: https://github.com/jnyman/test_workflow
+licenses:
+- MIT
+metadata: {}
+post_install_message: "\n(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)\n
+  \ TestWorkflow 0.1.0 has been installed.\n(::) (::) (::) (::) (::) (::) (::) (::)
+  (::) (::) (::) (::)\n  "
+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.1
+signing_key: 
+specification_version: 4
+summary: Chains classes and methods as a path to execute in a workflow.
+test_files: []