dtf 0.2.1 → 0.2.2

data/.gitignore

@@ -0,0 +1,44 @@
+.project
+*~
+.config
+pmip/**/*
+.idea/**/*
+*.log
+pkg
+.yardoc
+dtf.sublime-workspace
+_yardoc
+tmp
+Thumbs.db
+*.bak
+.iws
+pmip
+.DS_Store
+*.rbc
+.svn/
+/db/config.yml
+*.gem
+InstalledFiles
+Gemfile.lock
+rdoc
+dtf.sublime-project
+*.swp
+lib/bundler/man
+.bundle
+~*
+coverage
+.*proj
+*.iml
+.idea/
+*.patch
+spec/reports
+.idea
+node_modules/
+/db/*.sqlite3
+.classpath
+target/
+.settings/
+test/version_tmp
+*.diff
+.ipr
+test/tmp

data/.rspec

@@ -0,0 +1 @@
+-r turnip/rspec --color

data/.rvmrc

@@ -0,0 +1,52 @@
+#!/usr/bin/env bash
+
+# This is an RVM Project .rvmrc file, used to automatically load the ruby
+# development environment upon cd'ing into the directory
+
+# First we specify our desired <ruby>[@<gemset>], the @gemset name is optional,
+# Only full ruby name is supported here, for short names use:
+#     echo "rvm use 1.9.3" > .rvmrc
+environment_id="ruby-1.9.3-p194@dtf"
+
+# Uncomment the following lines if you want to verify rvm version per project
+rvmrc_rvm_version="1.14.1 (master)" # 1.10.1 seams as a safe start
+eval "$(echo ${rvm_version}.${rvmrc_rvm_version} | awk -F. '{print "[[ "$1*65536+$2*256+$3" -ge "$4*65536+$5*256+$6" ]]"}' )" || {
+  echo "This .rvmrc file requires at least RVM ${rvmrc_rvm_version}, aborting loading."
+  return 1
+}
+
+# First we attempt to load the desired environment directly from the environment
+# file. This is very fast and efficient compared to running through the entire
+# CLI and selector. If you want feedback on which environment was used then
+# insert the word 'use' after --create as this triggers verbose mode.
+if [[ -d "${rvm_path:-$HOME/.rvm}/environments"
+  && -s "${rvm_path:-$HOME/.rvm}/environments/$environment_id" ]]
+then
+  \. "${rvm_path:-$HOME/.rvm}/environments/$environment_id"
+  [[ -s "${rvm_path:-$HOME/.rvm}/hooks/after_use" ]] &&
+    \. "${rvm_path:-$HOME/.rvm}/hooks/after_use" || true
+  if [[ $- == *i* ]] # check for interactive shells
+  then echo "Using: $(tput setaf 2)$GEM_HOME$(tput sgr0)" # show the user the ruby and gemset they are using in green
+  else echo "Using: $GEM_HOME" # don't use colors in non-interactive shells
+  fi
+else
+  # If the environment file has not yet been created, use the RVM CLI to select.
+  rvm --create use  "$environment_id" || {
+    echo "Failed to create RVM environment '${environment_id}'."
+    return 1
+  }
+fi
+
+# If you use bundler, this might be useful to you:
+# if [[ -s Gemfile ]] && {
+#   ! builtin command -v bundle >/dev/null ||
+#   builtin command -v bundle | GREP_OPTIONS= \grep $rvm_path/bin/bundle >/dev/null
+# }
+# then
+#   printf "%b" "The rubygem 'bundler' is not installed. Installing it now.\n"
+#   gem install bundler
+# fi
+# if [[ -s Gemfile ]] && builtin command -v bundle >/dev/null
+# then
+#   bundle install | GREP_OPTIONS= \grep -vE '^Using|Your bundle is complete'
+# fi

data/.travis.yml

@@ -0,0 +1,16 @@
+rvm:
+  - 1.9.3
+before_script:
+  - RAILS_ENV='development' bundle exec thor dtf_setup:config
+  - RAILS_ENV='development' bundle exec rake db:migrate
+  - RAILS_ENV='development' bundle exec gem list
+script: RAILS_ENV='development' bundle exec rspec spec --format doc
+language: ruby
+notifications:
+  irc:
+    channels:
+      - "irc.freenode.org#dtf-gems"
+  email:
+    recipients:
+      - me@deryldoucette.com
+    on_failure: change

data/Gemfile

@@ -0,0 +1,26 @@
+# -*- coding: UTF-8 -*-
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in dtf.gemspec
+group :development, :test do
+  #gem "pry", :git => "https://github.com/pry/pry.git"
+  #gem "pry-doc", :git => "https://github.com/pry/pry-doc.git"
+  #gem "method_source", :git => "https://github.com/banister/method_source.git"
+  gem 'pry'
+  gem 'pry-doc'
+  gem 'pry-debugger'
+  gem "pry-git"
+  gem "pry-developer_tools"
+  gem "pry-syntax-hacks"
+  gem "pry-editline"
+  gem "pry-highlight"
+  gem "pry-buffers"
+  gem "pry-stack_explorer"
+  gem "pry-exception_explorer"
+  gem "jist"
+  gem "pry-theme"
+  gem 'simplecov'
+end
+
+gemspec

data/History.md

@@ -0,0 +1,75 @@
+
+0.2.2 / 2012-08-08 
+==================
+
+  * Fixed up included baseline pry and related gems. Now using pry-debugger which uses debugger gem.
+  * Forgot to add doc/.gitkeep so that git retains the (currently) empty directory
+  * Removed doc directory from .gitignore since we plan on storing docs here
+  * Added /db/config.yml and /db/*.sqlite3 to .gitignore file
+  * We run thor dtf_setup:config so no need to put the config there ahead of time.
+  * Defaulted the gem to RAILS_ENV='production'. Modified .travis.yml to set this to 'development' before running commands. This affects ActiveRecord database selection, and whether testing gems are available.
+  * Updated associations to include dependent destroy and autosave
+  * Added entry to TODO to remember to change ENV['RAILS_ENV'] to production upon gem release. Also put TODO note in environment.rb [ci skip]
+  * Added config.ymla nd dtf-setup
+  * Added dtf-setup script to do setup
+  * Forgot to add require 'thor' for tasks
+  * Forgot to remove pry-coolline from environment.rb as well. sigh
+  * Forgot to commit Gemfile without pry-coolline. It breaks a lot of core functionality features in pry which uses readline instead, so tab completion and the like are busted.
+  * Added bundle exec gem list to before_script for travis. Travis doesn't output a list of gems used, and since this is itself a gem there is no Gemfile.lock committed. So this is the only way to see what versions of dependencies are being installed since the version isn't locked down within the gemspec.
+  * Incorrect numbering of tests. Really just these 2 files should be numbered because they should run before all other tests. The reasoning is that by testing basic model creation, and basic core associations first then all other tests should succeed so run them first.
+  * Added additional steps definitions and feature for testing basic model associations
+  * Removed auto-fabrication of a verification suite for fabricated analysis cases as that will cause problems in testing.
+  * Updated migrations to reflect changeout of HABTM for has_many :through. Deleted HABTM join table migration.
+  * Changed out HABTM association from models for belongs_to and has_many :through
+  * Just adding dep for pry-theme so I can use different color coding. No code changes. [ci skip]
+  * Fixed the matcher thanks to workmad3 explaining what I was doing wrong. Bad matcher.
+  * Split out to :association as workmad3 was indicating. But for some reason its not finding the step anymore. Getting 'No such step' on user ownership tracking through verification_suites.
+  * Broke CI testing because pry is not being loaded. Forgot to add :test group to Gemfile
+  * bin directory should have contents +755.
+  * Added RVM version check to .rvmrc file. Moved Pry development dependencies to Gemfile from gemspec because gemspec does not support using :git with dependencies. Gemfile does.
+  * For some reason git marked bin/.gitkeep chmod 755. NO, bad git
+  * Added a dependency on vcr gem. dtf will contain the core of the connection API which each sub-module gem extends for its portion. In order to be able to replay with exactness, I decided to try out 'vcr'.
+  * Last bit of ordering on case_test
+  * Reordering associations
+  * Fix association ordering in models
+  * Added notes for going forward to TODO list. [ci skip]
+  * Modified rspec model tests to ensure Models are properly created, and persisted.
+  * Added RSpec steps for '0001_create_basic_models.feature' using fabrication of each of the base models
+  * Added core models and ownership directions test, as a turnip feature
+  * Fixed .travis.yml config. Forgot to add thor dtf_setup:config for copying db/config.yml
+  * Added travis-ci.org .travis.yml configuration file for public CI testing
+  * Fixed fabricators as they had bad var names and logic. Fixed and added specs for each model. Tests and Fabricators PASS
+  * Added RSpec and Turnip infrastructure, and a basic User spec
+  * Added lib/config/environment.rb for environmental control. Updated .gitignore to remove config dir
+  * Added fabrication gem to gemspec. Created Fabricators for each model
+  * Added logic to lib/dtf/rb to load the model files so that require 'dtf' autoloaded them
+  * Renamed incorrectly named AnalysisSuite to AnalysisCase and renamed associated migration. Fixed typo in AnalysisCase and CaseTest validations. Added additional deps for pry to dtf.gemspec for development mode. Added corrected db/schema.rb
+  * Fixed formatting of schema.rb
+  * Fixed typos in migrations and added db/schema.rb to repo
+  * Mode change on dtf-create_vs script
+  * Updated dependencies for Active(Record|Model|Support) and json(_pure) to gemspec
+  * Added models and migrations for User, Verification Suite, Analysis Case, and Case Test with associations migration
+  * Added basic outline of dtf-* management scripts
+  * Added bin directory as this is where the control/management scripts will live.
+  * Added db/.gitkeep and db/migrate/.gitkeep to ensure directory structure stays even if empty
+  * Renamed database.yml to config.yml for standalone_migrations. renamed examples/config to examples/db to coincide with destination dir names
+  * db/migrations is deprecated for d/migrate so changed the dirname and related thor tasks
+  * Added example sqlite3 dtf_*.sqlite3 database.yml file. This gets copied by thor dtf_setup:config
+  * Added directory logic to the thor install and config options because the copy operatins are copying files relative to the gem to places relative to the user's project, so the paths have to change.
+  * Changed thor task class to DtfSetup to isolate namespace
+  * Added db/migrations directory and updated setup.thor with install and config tasks
+  * Updated .gitignore to ignore config/ and added examples directory with config subdir for thor setup:install task
+  * Added thor setup task
+  * Incorrect rspec version currently
+  * Updated gemspec to rely on rspec 2.10.1 or higher, and am changing to using thor for task management
+  * Added .idea and pmip to gitignore
+  * Added a TODO file for tracking forward movement
+  * Added .idea and pmip directories to .gitignore file.
+  * Needlessly added dependency. Calling gem 'rspec' pulls in rspec-core, rspec-expectations, and rspec-mocks so no need to explicitly declare rspec-expectations
+  * Added standalone_migrations tasks call to Rakefile
+  * Added rspec and turnip infrastructure directories
+  * Added .rspec file to connect turnip
+  * Development dependency reordering
+  * Added pry and related gems, plus rspec-expectations, and standalone_migrations development dependencies
+  * Extended description of gem to better define gem contents and function
+  * Initial commit of DTF's dtf infrastructure gem

data/LICENSE

@@ -1,13 +1,22 @@
-Copyright (c) 2011 Michal Papis
+Copyright (c) 2012 Deryl R. Doucette
 
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
+MIT License
 
-    http://www.apache.org/licenses/LICENSE-2.0
+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:
 
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
+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

@@ -1,66 +1,88 @@
 # Deryls Testing Framework
 
-DTF is a pluggable framework for testing shell scripts (at least now).
-DTF also is an umbrella which incorporates (eventually) multiple gems, each of which provides additional functionality
-to DTF. DTF is the skeleton upon which all other dtf-* gems build.
+DTF is designed to be a modular framework for testing everything from shell scripts, to Ruby, to Rails apps.
 
+DTF is an umbrella which is designed to incorporate multiple sub-gems, each of which provides additional
+functionality to DTF. DTF is the master skeleton within which all other dtf-* gems integrate.
 
-## Usage
+## Internal architecture
 
-    $ gem install dtf
-    $ dtf <path/to/file>_comment_test.sh
+DTF is designed in such a way that, with the master skeleton in place, one has only to load additional plugins
+from any available DTF extension gem to add additional functionality. This can be anything ranging from
+additional languages such as Ruby, Python, C, C++, etc, to testing methods and methodologies.
 
-## Comment tests
+## Current Status
 
-Filename has to end with _comment_test.sh
+DTF is 100% Alpha quality right now. For those that don't know what that means, generally this means DTF is
+    comprised of code with a vastly high potential for buggy code that may or may not even run. Consider DTF
+    to be experimental until further notice. This README will be updated to reflect when DTF reaches a
+    'stable' quality.
 
-Example test file:
+    DTF will gladly, and willingly, review any Pull Requests sent to us, and incorporate them as they fit with
+    the mission goal of DTF. Please bear in mind that DTF is a rolling Project. This means that the definition
+    of what DTF is, and how that is implemented is not firmly etched in stone yet, so both of those can, and
+    most likely will, change as time passes. If you can deal with that, please, by all means, feel free to
+    contribute.
 
-    ## User comments start with double #
-    ## command can be writen in one line with multiple tests:
-    true # status=0; match=/^$/
-    ## or tests can be placed in following lines:
-    false
-    # status=1
+    **NOTE: DTF was originally released with a soon-to-be 100% different codebase, and gemified. This version
+    will be gemified as well, _but_ in order to ensure that we can continue to use the 'dtf' name on
+    rubygems.org we have to bump the version number by .1 and go from there. So, that changes our new
+    numbering scheme a bit. The next release of 'dtf' that will be 100% the _new_ codebase will be 0.2.2. The
+    last 'dtf' that is the original code base is: dtf-0.2.1 on rubygems.org. Thanks for bearing with DTF while
+    the codebase change is swapped over.
 
-### Matchers
+## Branches
 
-The test can be negated by replacing `=` with `!=`
+    DTF has a branching and tagging topology as follows, and applies to DTF and _all_ sub-module gems:
+
+    * master - This branch on the DTF control gem, and _all_ dtf-<blah> sub-module gems is for **development**
+    
+    * stable - This branch on the DTF gem, and _all_ dtf-<blah> sub-modules, is 'stable' or 'production'
+    quality. Anything on this branch is to be considered safe and usable for everyday stuff.
+
+    * hotfix/>blah> branches are **stable** quality only. These are for running fixes to a particular stable
+    branch and will usually result in generating a new version tag. For example, if the hotfix was applied
+    against v2.3.4, then a tag of v2.3.5 would be generated once that hotfix was proven to be tested and
+    stable.
+
+    * feature/<blah> branches are **development** quality only. This is for work on individual new features
+    that _will_ be rolled into DTF or sub-module gems.
+
+    * playground/<blah> branches are **alpha** quality only. These are for developers to work out either
+    feasibilty of way-in-the-future ideas or to try something out that may, or may not, be incorporated into
+    the DTF or its sub-modules. _These are 100% to9 be considered throw-aways. They could disappear at any
+    moment, and any user of the DTF framework that relies on these branches is on their own. NO SUPPORT will
+    be provided of any kind for these branches_ so everyone is clear on that.
+
+    * All 'stable' production releases will be tagged. Only those releases will be tagged starting with a v,
+    and a series like #.#.#  where the first '#' starts with 1 going to whatever, in progressive order. This
+    represents an industry standard versioning format. NOTE: v0.#.# is NOT considered a 'stable' release!
+    This is normal in the industry for Projects just starting out. When a version is reached that we believe
+    to be of sufficient quality to be denoted, and tagged, as our first Stable release, it will be marked as
+    v1.#.# and NOT v0.#.#. The remaining '#' in the example denote our Minor, and Change '#' levels. For
+    example, #.#.# is Major.Minor.Change_Number_within_Minor. This means the following. Given a 'v2.3.4' tag,
+    this would denote:
+    
+      * The 2nd official 'stable' release.
+      * The 3rd Minor change to the 2.x series
+      * The 4th applied change within the 3rd Minor series.
 
-- status=<number> - check if command returned given status (0 is success)
-- match=/<regexp>/ - regexp match command output
-- env[<var_name>]=/<regexp>/ - regexp match the given environment variable name
+Until such time as the first official stable release is made, all v0.#.# tags up to but not including v0.5.0
+are of Alpha quality. Tags v0.5.# up to but not including v1.0.0 are to be considered Beta quality. This gives
+us plenty of room for Alpha _and_ Beta work before an official 'stable' release within the numbering system.
+** This applies to the DTF control gem, and _all_ dtf-<blah> sub-module gems! Please bear this in mind! **
 
-## Example
+We are making this a uniform policy across all levels of DTF to ensure that what you think something is,
+really is when it comes to version numbers and what they mean. This _will_ be a _strictly_ enforced policy.
 
-    $ bin/dtf example_tests/comment/*
-    F..
-    ##### Processed commands 2 of 2, success tests 2 of 3, failure tests 1 of 3.
-    $ false
-    # failed: status = 0 # was 1
-    
-    $ bin/dtf example_tests/comment/* --text
-    ##### starting test failure.
-    $ false
-    # failed: status = 0 # was 1
-    ##### starting test success.
-    $ true
-    # passed: status = 0
-    # passed: status != 1
-    ##### Processed commands 2 of 2, success tests 2 of 3, failure tests 1 of 3.
 
-## Internal architecture
+## Installation
 
-Framework will load plugins from any available gem and local `lib/` path, for example:
+To Be Announced
 
-    lib/plugins/dtf/text_output.rb
-    lib/plugins/dtf/status_test.rb
-    lib/plugins/dtf/comment_test_input.rb
 
-The search pattern is:
+## Usage
 
-    lib/plugins/dtf/*.rb
+To Be Announced
 
-And plugins are selected with:
 
-    lib/plugins/dtf/*_{input,test,output}.rb

data/Rakefile

@@ -0,0 +1,9 @@
+#!/usr/bin/env rake
+require "bundler/gem_tasks"
+
+begin
+    require 'tasks/standalone_migrations'
+rescue LoadError => e
+    puts "gem install standalone_migrations to get db:migrate:* tasks! (Error: #{e})"
+end
+

data/TODO

@@ -0,0 +1,25 @@
+Make sure to change ENV['RAILS_ENV'] to default to "production" upon release
+
+Write control/management scripts
+Ex: writing the scripts to add users, and create/delete
+verification suites/analysis cases from the commandline.
+
+Esure that the thor tasks for copying the dtf migrations and db config into a 
+project. which work now, get tests written to show they do.
+
+Properly document the params for DTF's dtf-* commands, as well as integration 
+docs for sub-gems
+
+Then its on to dtf-session to rewrite it so that when it includes dtf, the thor 
+tasks are registered and usable, and to redo the code to use the new schema
+
+Then on to dtf-rvm gem, dtf-sm gem, and dtf-shell 
+
+Those 3 gems would provide a full suite for testing ruby code, rvm, shell code and
+sm directly, when coupled with dtf master gem. Then we can build other framework
+gems.
+
+dtf-session becomes a dependency of dtf-shell which will be written to support 
+specific Shells
+
+dtf-rvm will have a dependency on both dtf-session, and rvm gems

data/app/models/analysis_case.rb

@@ -0,0 +1,12 @@
+# -*- coding: UTF-8 -*-
+
+class AnalysisCase < ActiveRecord::Base
+
+  attr_accessible :name, :description
+  validates_presence_of :name, :description
+
+  belongs_to  :verification_suite, :autosave => :true
+  belongs_to  :user, :autosave => :true
+  has_many :case_tests, :dependent => :destroy
+
+end

data/app/models/case_test.rb

@@ -0,0 +1,10 @@
+# -*- coding: UTF-8 -*-
+
+class CaseTest < ActiveRecord::Base
+
+  attr_accessible :description, :cmd
+  validates_presence_of :description, :cmd
+
+  belongs_to  :analysis_case, :autosave => :true
+  has_one     :verification_suite, :through => :analysis_case, :autosave => :true
+end