soaspec 0.1.5 → 0.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 4a5dcd5cdd343b6810ee2db2355f21e54f656d0c
-  data.tar.gz: 34e57ec477e54a15732b2c2b790450f2c27fc758
+SHA256:
+  metadata.gz: 1e6f5ddf18a44208e620f9c1e4c11721260af6e065dadc234cced8975c07d39e
+  data.tar.gz: 521bc07ba5261761a53cd5d9e701af4a16768f3bcb0f0dbe4de039c7ba7e92f5
 SHA512:
-  metadata.gz: a42cbc94cebdb981b04414e77ea422860776fbe78c85068e2168500164a2bb64609bec8a88e070e41a049148cad0faa78d94a323a892cc15e989617112441196
-  data.tar.gz: 6e90d5d6d7ef41900b2c1a1361ae6790a253521a0f3b298f8b4c35109a745410de4ac8fef3c48d25e6ec81b0325d543cd85ab1544bc07bb82600d5c1d9b2a6d8
+  metadata.gz: 27e4cbfd225fb28720df84062cc232443bcd4cae64e45d361cd5104c24083f40452272f1d558bf71a11ff4ac39a6efcb356a4138c7ad92a93e4af8d58c665f15
+  data.tar.gz: 606453ce3a72c8c8e3e7d8cd84bb88b75b6c7ce4f537ebb47fd5f82e6dd0187f0f31a0cb0b6b4936ef0e7587c3b292779072efdf52b31442db6bcb1665e0cbc5

data/.gitignore

@@ -1,15 +1,15 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/logs/
-/pkg/
-/spec/reports/
-/tmp/
-/.idea/
-Gemfile.lock
-coverage
-
-# rspec failure tracking
-.rspec_status
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/logs/
+/pkg/
+/spec/reports/
+/tmp/
+/.idea/
+Gemfile.lock
+coverage
+
+# rspec failure tracking
+.rspec_status

data/.gitlab-ci.yml

@@ -1,49 +1,49 @@
-before_script:
-  - apt-get update -qq && apt-get install -y -qq sqlite3 libsqlite3-dev nodejs
-  - ruby -v
-  - which ruby
-  - gem install bundler rake --no-ri --no-rdoc
-  - bundle install --jobs $(nproc)  "${FLAGS[@]}"
-
-rspec:
-  stage: test
-  script:
-    - bundle exec rake spec
-  artifacts:
-    paths:
-      - coverage/
-
-cucumber:
-  stage: test
-  script:
-    - bundle exec cucumber
-
-code_quality:
-  image: docker:stable
-  variables:
-    DOCKER_DRIVER: overlay2
-  allow_failure: true
-  services:
-    - docker:stable-dind
-  script:
-    - export SP_VERSION=$(echo "$CI_SERVER_VERSION" | sed 's/^\([0-9]*\)\.\([0-9]*\).*/\1-\2-stable/')
-    - docker run
-        --env SOURCE_CODE="$PWD"
-        --volume "$PWD":/code
-        --volume /var/run/docker.sock:/var/run/docker.sock
-        "registry.gitlab.com/gitlab-org/security-products/codequality:$SP_VERSION" /code
-  artifacts:
-    paths: [gl-code-quality-report.json]
-
-pages:
-  stage: deploy
-  dependencies:
-    - rspec
-  script:
-    - mv coverage/ public/
-  artifacts:
-    paths:
-      - public
-    expire_in: 30 days
-  only:
+before_script:
+  - apt-get update -qq && apt-get install -y -qq sqlite3 libsqlite3-dev nodejs
+  - ruby -v
+  - which ruby
+  - gem install bundler rake --no-ri --no-rdoc
+  - bundle install --jobs $(nproc)  "${FLAGS[@]}"
+
+rspec:
+  stage: test
+  script:
+    - bundle exec rake spec
+  artifacts:
+    paths:
+      - coverage/
+
+cucumber:
+  stage: test
+  script:
+    - bundle exec cucumber
+
+code_quality:
+  image: docker:stable
+  variables:
+    DOCKER_DRIVER: overlay2
+  allow_failure: true
+  services:
+    - docker:stable-dind
+  script:
+    - export SP_VERSION=$(echo "$CI_SERVER_VERSION" | sed 's/^\([0-9]*\)\.\([0-9]*\).*/\1-\2-stable/')
+    - docker run
+        --env SOURCE_CODE="$PWD"
+        --volume "$PWD":/code
+        --volume /var/run/docker.sock:/var/run/docker.sock
+        "registry.gitlab.com/gitlab-org/security-products/codequality:$SP_VERSION" /code
+  artifacts:
+    paths: [gl-code-quality-report.json]
+
+pages:
+  stage: deploy
+  dependencies:
+    - rspec
+  script:
+    - mv coverage/ public/
+  artifacts:
+    paths:
+      - public
+    expire_in: 30 days
+  only:
     - master

data/.rspec

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

data/.rubocop.yml

@@ -1,2 +1,2 @@
-Metrics/LineLength:
-  Max: 154
+Metrics/LineLength:
+  Max: 154

data/CODE_OF_CONDUCT.md

@@ -1,74 +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 samuel.garratt@integrationqa.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/
+# 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 samuel.garratt@integrationqa.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/ChangeLog

@@ -1,401 +1,405 @@
-Version 0.1.5
-* Enhancements
-  * Package spec changes status after a post is made. Help to illustrate scenario where status changes
-  * Record last exchange made for debugging purposes in 'last_exchange'
-
-Version 0.1.4
-* Enhancements
-  * create_file method create folders automatically if necessary
-  * Package spec to help learn testing for items in a list
-  * Added docs for soaspec-virtual-server
-
-Version 0.1.3
-* Enhancements
-  * Ability to set template folder
-  * Json Path handle multiple paths separated by commas
-
-Version 0.1.1
-* Enhancements
-  * Added ability to turn off logs (helpful if making a lot of API calls)
-
-Version 0.1.0
-* Enhancements
-  * Cleaned up unit tests for WSDL generator. Won't bother for SOAP ComplexType for now as I'm not needing this and it looks like Savon 3 will create example requests anyway
-  * Put SOAP Basic Auth in Example
-  * Added template handling for REST handler
-
-Version 0.0.89
-* Enhancements
-  * Move more functionality out of soaspec exe and into WsdlGenerator. Started unit tests for it
-
-Version 0.0.88
-* Bug Fix
-  * Corrected '_format' variable name that was breaking failing to find rest element
-
-Version 0.0.87
-* Bug Fix
-  * Fixed incorrect logging for when 'debug_oauth' is off
-
-Version 0.0.86
-* Enhancements
-  * 'debug_oauth' attribute used to toggle showing params used in retrieving access token
-
-Version 0.0.85
-* Enhancements
-  * Interpret XML and JSON better so that JSON with XML in it's tags is catered for
-
-Version 0.0.84
-* Enhancements
-  * 'strip_namespaces' defined in exchange handlers not globally which makes more sense
-  * Created 'to_hash' method for Exchange that returns a Hash of XML or JSON response (primarily for REST)
-
-Version 0.0.83
-* Enhancements
-  * Handle BOM or other characters that could be at start of xml of json response string
-
-Version 0.0.82
-* Enhancements
-  * Fixed namespace handling for REST
-
-Version 0.0.81
-* Enhancements
-  * SoapHandler - define exchange method for each SOAP operation. See `one_off_spec` for example
-
-Version 0.0.80
-* Enhancements
-  * `values_from_path` method on `RestHandler` to easily extract multiple values for an xpath or json path
-* Bug fix
-  * Support response that has white space surrounding message
-
-Version 0.0.79
-* Enhancements
-  * `values_from_path` method on `SoapHandler` to easily extract multiple values for an xpath
-  * If `id` is specified on associated factory, FactoryBot will populate the primary factory with that id. See `rest/factory_spec` for eg
-
-Version 0.0.78
-* Enhancements
-  * Use 'thor' for `soaspec generate`, allowing less prompt and more options through command line. Added tests for it
-
-Version 0.0.77
-* Enhancements
-  * Use 'thor' for soaspec-init binary changing it to be `soaspec init`. Will update `soaspec-generate` in next version
-  * Put pause of 1/2 a second for each API retry. Often retry is too quick otherwise
-
-Version 0.0.76
-* Bug fix
-  * Fixed BLZService scenario on soaspec-virtual-server
-  * Fixed return value for retry_for_success failure
-* Enhancements
-  * Added method to indicate a factory create should actually return a failure status
-
-Version 0.0.75
-* Enhancements
-  * For Factory created methods, set retry_for_success to true. Allow for this to be set at Exchange class level
-
-Version 0.0.74
-* Enhancements
-  * RestHandler, enable api username to be set upon initialisation
-
-Version 0.0.73
-* Enhancements
-  * Added 'default_handler' method with which define an exchange_handler to be created when an exchange is initialized
-* Refactoring
-  * Use `@exchange_handler` instead of `@api_class` which is more consistent
-
-Version 0.0.72
-* Enhancements
-  * Add ability to convert XML response to lower case for simpler xpath searching
-
-Version 0.0.71
-* Bug fix
-  * Got exe 'soaspec-virtual-server' working
-
-Version 0.0.70
-* Enhancements
-  * Added api_username method to REST handler to change user for an API during runtime
-
-Version 0.0.69
-* Enhancements
-  * Calculate base_url ERB at time of handler's first request (Rather than when initialised).
-    - Important for where base url uses ERB and so does oauth whose user may change
-  * Demonstrate using oauth via spec
-  * Demonstrate using basic auth via spec
-
-Version 0.0.68
-* Enhancements
-  * Use ERB to calculate base_url for dynamic bases
-
-Version 0.0.67
-* Enhancements
-  * Handle scenario where Request key is unconventional and not PascalCase key snakecase convert would break it
-    - if first character of key is captial, PascalCase conversion is ignored
-
-Version 0.0.66
-* Enhancements
-  * Added method to convert REST request keys to 'PascalCase' if 'pascal_keys' is set to true
-  * This also converts paths obtaining elements to 'PascalCase' if they're simple and have no starting '//' or '$..'
-
-Version 0.0.65
-* Enhancements
-  * Added ability to set 'suburl' and 'method' in Exchange accessor. Will be used in FactoryBot later
-
-Version 0.0.64
-* Enhancements
-  * Got FactoryBot working for RestHandler. See specs for example
-  * Add element? method to exchange to make it easier to check element is at path
-  * Define 'element_name?' created when element is defined on ExchangeHandler
-
-Version 0.0.63
-* Enhancements
-  * Interpret ERB for oauth credentials within oauth response. Needed for when params like 'username' can change in runtime
-
-Version 0.0.62
-* Enhancements
-  * Use q parameter to simply to query parameters on REST requests
-
-Version 0.0.61
-* Enhancements
-  * Retrieving oauth response try 3 times (to bypass intermittent errors)
-
-Version 0.0.60
-* Enhancements
-  * Allow for factory_bot with automatic setting of missing setter methods
-
-Version 0.0.59
-* Enhancements
-  * Perform ERB in headers to make using access_token using 'headers' possible
-  * Try better way of testing `soaspec-init`.
-
-Version 0.0.58
-* Enhancements
-  * Add method to set parts of the request body through `exchange[key]= 'value'`
-  * Added example of Cucumber feature demonstrating this
-
-Version 0.0.56
-* Bug fix
-  * Handle creating of traffic.log file within lib properly
-
-Version 0.0.55
-* Enhancements
-  * Made `soaspec-virtual-server` exe to handle self served test server. Will be used in wiki tutorial
-
-Version 0.0.54
-* Enhancements
-  * Make 'headers' accessor for setting headers on RestHandler easier
-
-Version 0.0.53
-* Enhancements
-  * Make attribute possible for REST methods as well (as they can use XML too)
-  * For non XML, non JSON responses, handle with regex or key for a Hash
-
-Version 0.0.52
-* Enhancements
-  * Now have 'attribute' accessor making it easy to access an attribute from a response
-
-Version 0.0.51
-* Enhancements
-  * Allow for 'default_hash=' method to be used in RestHandler. See 'many_calls_one_method_spec' for example
-  * Got 'element' accessor working correctly (See soap/hash_spec.rb + 'blz_service' for example)
-
-Version 0.0.50
-* Enhancements
-  * Able to use ERB in oauth parameters and extract oauth hash with 'oauth_response' method defined by 'oauth_file'
-
-Version 0.0.47
-* Bug Fix
-  * Using 'Strip namespace' handle both namespace or not dependent if used
-
-Version 0.0.47
-* Enhancements
-  * 'success scenarios' shared eg and 'retry_for_success' exchange method's status codes include 200..299, not just 200.
-
-Version 0.0.46
-* Enhancements
-  * 'include_key?' method use 'value_from_path'. Iterating through Hashes with 'include_key?' wouldn't work as expected with some JSON bodies with my current implementation
-
-Version 0.0.45
-* Enhancements
-  * No need to use 'name' when creating SoapHandler and RestHandler. Default is ClassName
-
-Version 0.0.44
-* Enhancements
-  * Test Server log to logs/test_server.log
-  * Simplify ExchangeHandler storing and retrieving values (see soap/hash_spec.rb)
-  * Make setting SoapHandler operation and other params possible through object instantiation. Less code needed
-
-Version 0.0.43
-* Bug fix
-  * Remove Environment namespace from 'soaspec-generate'
-* Enhancements
-  * Convenience methods for REST calls in which you can call something like 'ClassInheritingRestHandler.get(params)' See 'spec/soaspec/rest/one_off_spec.rb' for details
-
-Version 0.0.42
-* Enhancements
-  * Set Soaspec.api_handler work class is created. No need to call '.to_s' method
-
-Version 0.0.41
-* Bug fix
-   * soaspec-generate not designed to work with virtual service. Rakefile not try to set that up
-
-Version 0.0.40
-* Enhancements
-  * soaspec-generate now handle a wsdl without parameters in the operation and rather look up input element type
-  * test_server virtual service now handle scenario where bank is not found and test made for that
-
-Version 0.0.39
-* Spec
-  * Create task to use soaspec-init to create test structure and test it.
-* Enhancements
-  * Take away need to use Environment namespace
-  * Added response headers to REST response log
-  * Now using virtual Web Service for SOAP
-
-Version 0.0.38 
-* Bug fix
-   * Fixed error in soaspec-generate. TODO: Test this in CI
-
-Version 0.0.37 / 2018-3-16
-* Enhancements
-  * Made retry_for_success method to keep making request until 200 status code if set on exchange
-  * If '$' not included for json_path, by default a '$..' is added for convenience
-
-Version 0.0.36 / 2018-3-15
-* Bug fix
-   * Make test name log in correct place
-* Enhancements
-  * Made accessor 'mandatory_json_values' to make it easier to share mandatory json path - value pairs
-  * Created 'store' method for handler through which one can store a value and use it later on it in the same context
-* Deprecated
-  * Removed old 'mandatory_elements', 'mandatory_xpath_values' overridden way of handling data for favor of new way of it setting 'expected_mandatory_elements'
-
-Version 0.0.35 / 2018-3-13
-* Enhancements
-  * Handle array of JSON hashes starting with '['
-  * Handle patch and put methods with data for REST
-
-Version 0.0.34 / 2018-3-12
-* Enhancements
-  * Add oauth2 and oauth2_file methods to make it easy to load oauth2 parameters. Still a work in progress to handle all oauth2 variations
-
-Version 0.0.33 / 2018-3-9
-* Enhancements
-  * Use 'jsonpath' instead of dig to check JSON responses. Much better for finding complex paths
-
-Version 0.0.32 / 2018-3-9
-* Enhancements
-  * Made :body key in hash that can be used to use JSON.generate for a payload when using rest_handler exchanges
-
-Version 0.0.31 / 2018-3-8
-* Enhancements
-  * Compacted unit tests for exchange handler
-  * Implemented include_key? and find via xpath for REST handler. See specs
-
-Version 0.0.30 / 2018-3-6
-* Bug fix
-   * Made generated class file name in soaspec-generate snakecase (was CamelCase)
-
-Version 0.0.29 / 2018-3-6
-* Refactorings
-   * Base 'test' class from 'Tester' to 'ExhangeHandler'
-   * Made default Soap Handler class 'SoapHandler' and making use of 'BasicSoapHandler' deprecated
-
-Version 0.0.28 / 2018-3-6
-* Enhancements
-  * Added not_found matcher and used in spec example
-  * Only call request upon first need of an Exchange response. This means test request is made as part of 'it' rather than in describe
-
-Version 0.0.27 / 2018-3-5
-* Bug fix
-  * Fixed log file not present error
-  * Updated exe binaries to use latest format
-
-Version 0.0.26 / 2018-3-5
-* Refactorings
-   * Using methods to define mandatory_elements, mandatory_xpath_values, root_attributes, base_url. Please see specs. This is shorter to type and clearer
-
-Version 0.0.25 / 2018-2-25
-* Enhancements
-  * Updated rest_handler to convert JSON and XML into Hash and use it in 'contain_value'. This still needs work.
-  * Showed example of workflow using 'pet' url
-
-Version 0.0.24 / 2018-2-25
-* Enhancements
-  * Added to soaspec-generate more types when creating YAML with data (int, boolean, double and custom enumeration).
-  * Binaries use common module (exe-helper) to reduce repeatability
-* TODO: soaspec-generate read xsd's mentioned to import in WSDL schema
-
-Version 0.0.23 / 2018-2-23
-* Enhancements
-  * Created RestHandler class (Very messy and ugly still) to handle REST requests using style used for SOAP using Rest Client resource
-
-Version 0.0.22 / 2018-2-15
-* Enhancements
-  * Created new 'include_in_body' matcher to find value anywhere in response body (which could be a substring of an element)
-
-Version 0.0.21 / 2018-1-29
-* Enhancements
-  * Added soaspec-generate - still in POC mode to generate files from a WSDL.
-  * Added test_wsdl to start at validating xml according to WSDL. Still needs polishing
-
-Version 0.0.20 / 2018-1-26
-* Enhancements
-  * Added ability to strip namespaces 'Soaspec::Environment.strip_namespaces = true'. See spec for example
-* Fixes
-  * Made custom error and used it to make 'have_element_at_xpath' work when negated
-
-Version 0.0.19 / 2018-1-25
-* Enhancements
-   * Added own shared examples to init script and to in built specs
-
-Version 0.0.18 / 2018-1-25
-* Fixes
-  * Updated 'soaspec-init' so that it works again.
-* Enhancements
-  * Added example showing representing data for request in YAML
-
-Version 0.0.17 / 2018-1-25
-* Fixes
-  * Updated hash search so that it handles Array
-
-Version 0.0.16 / 2018-1-23
-* Fixes
-  * Corrected logic of auto convert to hash. Previous version did not handle test specific values correctly
-
-Version 0.0.15 / 2018-1-23
-* Fixes
-  * Updated code to convert string key in Savon request to key automatically by default before passing to Savon. This saves
-    the user doing the conversion themselves.
-
-Version 0.0.14 / 2018-1-23
-* Fixes
-  * Updated 'xml_to_yaml_file' exe to clean up YAML more. No more array for Hash value. Indenting needs work though.
-    Now it's more like something you can read and pass into Savon request.
-
-Version 0.0.13 / 2018-1-23
-* Enhancements
-  * Executable to create xml file from yaml
-
-Version 0.0.12 / 2018/1-22
-* Enhancements
-  * Example name added to log file
-
-Version 0.0.10 / 2018-1-21
-* Enhancements
-  * Added [] method to perform xpath assertion
-  * Using Savon xpath. No need to explicitly provide namespace for xpath
-
-Version 0.0.9 / 2018-1-20
-* Refactoring
-  * class_options -> savon_options - More specific
-  * default_operation -> operation - Not default anymore so better not in name
-* Enhancements
-  * Made mandatory_xpath_values method to add to 'success scenarios' shared example
-
-Version 0.0.8 / 2018-1-19
-* Enhancements
-  * Added root_attributes method to add attribute to the root class
-
-Version 0.0.7 / 2018-1-19
-* Enhancements
-  * Added contain_key matcher
+Version 0.1.6
+* Enhancements
+  * Bind localhost to 0.0.0.0 so service is accessible outside localhost
+
+Version 0.1.5
+* Enhancements
+  * Package spec changes status after a post is made. Help to illustrate scenario where status changes
+  * Record last exchange made for debugging purposes in 'last_exchange'
+
+Version 0.1.4
+* Enhancements
+  * create_file method create folders automatically if necessary
+  * Package spec to help learn testing for items in a list
+  * Added docs for soaspec-virtual-server
+
+Version 0.1.3
+* Enhancements
+  * Ability to set template folder
+  * Json Path handle multiple paths separated by commas
+
+Version 0.1.1
+* Enhancements
+  * Added ability to turn off logs (helpful if making a lot of API calls)
+
+Version 0.1.0
+* Enhancements
+  * Cleaned up unit tests for WSDL generator. Won't bother for SOAP ComplexType for now as I'm not needing this and it looks like Savon 3 will create example requests anyway
+  * Put SOAP Basic Auth in Example
+  * Added template handling for REST handler
+
+Version 0.0.89
+* Enhancements
+  * Move more functionality out of soaspec exe and into WsdlGenerator. Started unit tests for it
+
+Version 0.0.88
+* Bug Fix
+  * Corrected '_format' variable name that was breaking failing to find rest element
+
+Version 0.0.87
+* Bug Fix
+  * Fixed incorrect logging for when 'debug_oauth' is off
+
+Version 0.0.86
+* Enhancements
+  * 'debug_oauth' attribute used to toggle showing params used in retrieving access token
+
+Version 0.0.85
+* Enhancements
+  * Interpret XML and JSON better so that JSON with XML in it's tags is catered for
+
+Version 0.0.84
+* Enhancements
+  * 'strip_namespaces' defined in exchange handlers not globally which makes more sense
+  * Created 'to_hash' method for Exchange that returns a Hash of XML or JSON response (primarily for REST)
+
+Version 0.0.83
+* Enhancements
+  * Handle BOM or other characters that could be at start of xml of json response string
+
+Version 0.0.82
+* Enhancements
+  * Fixed namespace handling for REST
+
+Version 0.0.81
+* Enhancements
+  * SoapHandler - define exchange method for each SOAP operation. See `one_off_spec` for example
+
+Version 0.0.80
+* Enhancements
+  * `values_from_path` method on `RestHandler` to easily extract multiple values for an xpath or json path
+* Bug fix
+  * Support response that has white space surrounding message
+
+Version 0.0.79
+* Enhancements
+  * `values_from_path` method on `SoapHandler` to easily extract multiple values for an xpath
+  * If `id` is specified on associated factory, FactoryBot will populate the primary factory with that id. See `rest/factory_spec` for eg
+
+Version 0.0.78
+* Enhancements
+  * Use 'thor' for `soaspec generate`, allowing less prompt and more options through command line. Added tests for it
+
+Version 0.0.77
+* Enhancements
+  * Use 'thor' for soaspec-init binary changing it to be `soaspec init`. Will update `soaspec-generate` in next version
+  * Put pause of 1/2 a second for each API retry. Often retry is too quick otherwise
+
+Version 0.0.76
+* Bug fix
+  * Fixed BLZService scenario on soaspec-virtual-server
+  * Fixed return value for retry_for_success failure
+* Enhancements
+  * Added method to indicate a factory create should actually return a failure status
+
+Version 0.0.75
+* Enhancements
+  * For Factory created methods, set retry_for_success to true. Allow for this to be set at Exchange class level
+
+Version 0.0.74
+* Enhancements
+  * RestHandler, enable api username to be set upon initialisation
+
+Version 0.0.73
+* Enhancements
+  * Added 'default_handler' method with which define an exchange_handler to be created when an exchange is initialized
+* Refactoring
+  * Use `@exchange_handler` instead of `@api_class` which is more consistent
+
+Version 0.0.72
+* Enhancements
+  * Add ability to convert XML response to lower case for simpler xpath searching
+
+Version 0.0.71
+* Bug fix
+  * Got exe 'soaspec-virtual-server' working
+
+Version 0.0.70
+* Enhancements
+  * Added api_username method to REST handler to change user for an API during runtime
+
+Version 0.0.69
+* Enhancements
+  * Calculate base_url ERB at time of handler's first request (Rather than when initialised).
+    - Important for where base url uses ERB and so does oauth whose user may change
+  * Demonstrate using oauth via spec
+  * Demonstrate using basic auth via spec
+
+Version 0.0.68
+* Enhancements
+  * Use ERB to calculate base_url for dynamic bases
+
+Version 0.0.67
+* Enhancements
+  * Handle scenario where Request key is unconventional and not PascalCase key snakecase convert would break it
+    - if first character of key is captial, PascalCase conversion is ignored
+
+Version 0.0.66
+* Enhancements
+  * Added method to convert REST request keys to 'PascalCase' if 'pascal_keys' is set to true
+  * This also converts paths obtaining elements to 'PascalCase' if they're simple and have no starting '//' or '$..'
+
+Version 0.0.65
+* Enhancements
+  * Added ability to set 'suburl' and 'method' in Exchange accessor. Will be used in FactoryBot later
+
+Version 0.0.64
+* Enhancements
+  * Got FactoryBot working for RestHandler. See specs for example
+  * Add element? method to exchange to make it easier to check element is at path
+  * Define 'element_name?' created when element is defined on ExchangeHandler
+
+Version 0.0.63
+* Enhancements
+  * Interpret ERB for oauth credentials within oauth response. Needed for when params like 'username' can change in runtime
+
+Version 0.0.62
+* Enhancements
+  * Use q parameter to simply to query parameters on REST requests
+
+Version 0.0.61
+* Enhancements
+  * Retrieving oauth response try 3 times (to bypass intermittent errors)
+
+Version 0.0.60
+* Enhancements
+  * Allow for factory_bot with automatic setting of missing setter methods
+
+Version 0.0.59
+* Enhancements
+  * Perform ERB in headers to make using access_token using 'headers' possible
+  * Try better way of testing `soaspec-init`.
+
+Version 0.0.58
+* Enhancements
+  * Add method to set parts of the request body through `exchange[key]= 'value'`
+  * Added example of Cucumber feature demonstrating this
+
+Version 0.0.56
+* Bug fix
+  * Handle creating of traffic.log file within lib properly
+
+Version 0.0.55
+* Enhancements
+  * Made `soaspec-virtual-server` exe to handle self served test server. Will be used in wiki tutorial
+
+Version 0.0.54
+* Enhancements
+  * Make 'headers' accessor for setting headers on RestHandler easier
+
+Version 0.0.53
+* Enhancements
+  * Make attribute possible for REST methods as well (as they can use XML too)
+  * For non XML, non JSON responses, handle with regex or key for a Hash
+
+Version 0.0.52
+* Enhancements
+  * Now have 'attribute' accessor making it easy to access an attribute from a response
+
+Version 0.0.51
+* Enhancements
+  * Allow for 'default_hash=' method to be used in RestHandler. See 'many_calls_one_method_spec' for example
+  * Got 'element' accessor working correctly (See soap/hash_spec.rb + 'blz_service' for example)
+
+Version 0.0.50
+* Enhancements
+  * Able to use ERB in oauth parameters and extract oauth hash with 'oauth_response' method defined by 'oauth_file'
+
+Version 0.0.47
+* Bug Fix
+  * Using 'Strip namespace' handle both namespace or not dependent if used
+
+Version 0.0.47
+* Enhancements
+  * 'success scenarios' shared eg and 'retry_for_success' exchange method's status codes include 200..299, not just 200.
+
+Version 0.0.46
+* Enhancements
+  * 'include_key?' method use 'value_from_path'. Iterating through Hashes with 'include_key?' wouldn't work as expected with some JSON bodies with my current implementation
+
+Version 0.0.45
+* Enhancements
+  * No need to use 'name' when creating SoapHandler and RestHandler. Default is ClassName
+
+Version 0.0.44
+* Enhancements
+  * Test Server log to logs/test_server.log
+  * Simplify ExchangeHandler storing and retrieving values (see soap/hash_spec.rb)
+  * Make setting SoapHandler operation and other params possible through object instantiation. Less code needed
+
+Version 0.0.43
+* Bug fix
+  * Remove Environment namespace from 'soaspec-generate'
+* Enhancements
+  * Convenience methods for REST calls in which you can call something like 'ClassInheritingRestHandler.get(params)' See 'spec/soaspec/rest/one_off_spec.rb' for details
+
+Version 0.0.42
+* Enhancements
+  * Set Soaspec.api_handler work class is created. No need to call '.to_s' method
+
+Version 0.0.41
+* Bug fix
+   * soaspec-generate not designed to work with virtual service. Rakefile not try to set that up
+
+Version 0.0.40
+* Enhancements
+  * soaspec-generate now handle a wsdl without parameters in the operation and rather look up input element type
+  * test_server virtual service now handle scenario where bank is not found and test made for that
+
+Version 0.0.39
+* Spec
+  * Create task to use soaspec-init to create test structure and test it.
+* Enhancements
+  * Take away need to use Environment namespace
+  * Added response headers to REST response log
+  * Now using virtual Web Service for SOAP
+
+Version 0.0.38 
+* Bug fix
+   * Fixed error in soaspec-generate. TODO: Test this in CI
+
+Version 0.0.37 / 2018-3-16
+* Enhancements
+  * Made retry_for_success method to keep making request until 200 status code if set on exchange
+  * If '$' not included for json_path, by default a '$..' is added for convenience
+
+Version 0.0.36 / 2018-3-15
+* Bug fix
+   * Make test name log in correct place
+* Enhancements
+  * Made accessor 'mandatory_json_values' to make it easier to share mandatory json path - value pairs
+  * Created 'store' method for handler through which one can store a value and use it later on it in the same context
+* Deprecated
+  * Removed old 'mandatory_elements', 'mandatory_xpath_values' overridden way of handling data for favor of new way of it setting 'expected_mandatory_elements'
+
+Version 0.0.35 / 2018-3-13
+* Enhancements
+  * Handle array of JSON hashes starting with '['
+  * Handle patch and put methods with data for REST
+
+Version 0.0.34 / 2018-3-12
+* Enhancements
+  * Add oauth2 and oauth2_file methods to make it easy to load oauth2 parameters. Still a work in progress to handle all oauth2 variations
+
+Version 0.0.33 / 2018-3-9
+* Enhancements
+  * Use 'jsonpath' instead of dig to check JSON responses. Much better for finding complex paths
+
+Version 0.0.32 / 2018-3-9
+* Enhancements
+  * Made :body key in hash that can be used to use JSON.generate for a payload when using rest_handler exchanges
+
+Version 0.0.31 / 2018-3-8
+* Enhancements
+  * Compacted unit tests for exchange handler
+  * Implemented include_key? and find via xpath for REST handler. See specs
+
+Version 0.0.30 / 2018-3-6
+* Bug fix
+   * Made generated class file name in soaspec-generate snakecase (was CamelCase)
+
+Version 0.0.29 / 2018-3-6
+* Refactorings
+   * Base 'test' class from 'Tester' to 'ExhangeHandler'
+   * Made default Soap Handler class 'SoapHandler' and making use of 'BasicSoapHandler' deprecated
+
+Version 0.0.28 / 2018-3-6
+* Enhancements
+  * Added not_found matcher and used in spec example
+  * Only call request upon first need of an Exchange response. This means test request is made as part of 'it' rather than in describe
+
+Version 0.0.27 / 2018-3-5
+* Bug fix
+  * Fixed log file not present error
+  * Updated exe binaries to use latest format
+
+Version 0.0.26 / 2018-3-5
+* Refactorings
+   * Using methods to define mandatory_elements, mandatory_xpath_values, root_attributes, base_url. Please see specs. This is shorter to type and clearer
+
+Version 0.0.25 / 2018-2-25
+* Enhancements
+  * Updated rest_handler to convert JSON and XML into Hash and use it in 'contain_value'. This still needs work.
+  * Showed example of workflow using 'pet' url
+
+Version 0.0.24 / 2018-2-25
+* Enhancements
+  * Added to soaspec-generate more types when creating YAML with data (int, boolean, double and custom enumeration).
+  * Binaries use common module (exe-helper) to reduce repeatability
+* TODO: soaspec-generate read xsd's mentioned to import in WSDL schema
+
+Version 0.0.23 / 2018-2-23
+* Enhancements
+  * Created RestHandler class (Very messy and ugly still) to handle REST requests using style used for SOAP using Rest Client resource
+
+Version 0.0.22 / 2018-2-15
+* Enhancements
+  * Created new 'include_in_body' matcher to find value anywhere in response body (which could be a substring of an element)
+
+Version 0.0.21 / 2018-1-29
+* Enhancements
+  * Added soaspec-generate - still in POC mode to generate files from a WSDL.
+  * Added test_wsdl to start at validating xml according to WSDL. Still needs polishing
+
+Version 0.0.20 / 2018-1-26
+* Enhancements
+  * Added ability to strip namespaces 'Soaspec::Environment.strip_namespaces = true'. See spec for example
+* Fixes
+  * Made custom error and used it to make 'have_element_at_xpath' work when negated
+
+Version 0.0.19 / 2018-1-25
+* Enhancements
+   * Added own shared examples to init script and to in built specs
+
+Version 0.0.18 / 2018-1-25
+* Fixes
+  * Updated 'soaspec-init' so that it works again.
+* Enhancements
+  * Added example showing representing data for request in YAML
+
+Version 0.0.17 / 2018-1-25
+* Fixes
+  * Updated hash search so that it handles Array
+
+Version 0.0.16 / 2018-1-23
+* Fixes
+  * Corrected logic of auto convert to hash. Previous version did not handle test specific values correctly
+
+Version 0.0.15 / 2018-1-23
+* Fixes
+  * Updated code to convert string key in Savon request to key automatically by default before passing to Savon. This saves
+    the user doing the conversion themselves.
+
+Version 0.0.14 / 2018-1-23
+* Fixes
+  * Updated 'xml_to_yaml_file' exe to clean up YAML more. No more array for Hash value. Indenting needs work though.
+    Now it's more like something you can read and pass into Savon request.
+
+Version 0.0.13 / 2018-1-23
+* Enhancements
+  * Executable to create xml file from yaml
+
+Version 0.0.12 / 2018/1-22
+* Enhancements
+  * Example name added to log file
+
+Version 0.0.10 / 2018-1-21
+* Enhancements
+  * Added [] method to perform xpath assertion
+  * Using Savon xpath. No need to explicitly provide namespace for xpath
+
+Version 0.0.9 / 2018-1-20
+* Refactoring
+  * class_options -> savon_options - More specific
+  * default_operation -> operation - Not default anymore so better not in name
+* Enhancements
+  * Made mandatory_xpath_values method to add to 'success scenarios' shared example
+
+Version 0.0.8 / 2018-1-19
+* Enhancements
+  * Added root_attributes method to add attribute to the root class
+
+Version 0.0.7 / 2018-1-19
+* Enhancements
+  * Added contain_key matcher
   * mandatory_elements method created for SoapHandler - can be used to add tests to success scenarios (see example get_weather_web_service class for details)