duck_test 0.1.4

data/lib/notes.txt

@@ -0,0 +1,215 @@
+random brainstorming notes when I first starting toying with the idea of building this gem.
+
+Should be able to run the debugger from a test.
+
+potential idea to unload files
+http://www.ruby-forum.com/topic/121905
+
+# #  watch pattern: "**/*" do
+# #    map /^models/, /^bike/ do
+# #      target /^unit/, /^bike_spec.rb/
+# #      target /^functional/, /^bike_controller_spec.rb/
+# #    end
+# #  end
+
+
+DuckTest.config do
+
+  # would set global includes / excludes within the default framework
+  included /.rb$/
+  included_dirs /^unit/
+  excluded /.rb$/
+  excluded_dirs /^functional/
+
+  framework :rspec do
+
+    # would set global includes / excludes within the framework being defined
+    included /.rb$/
+    included_dirs /^unit/
+    excluded /.rb$/
+    excluded_dirs /^functional/
+
+    watch "**/*", included: /book/ do
+      # would set includes / excludes within the watch list being defined
+      included /.rb$/
+      included_dirs /^unit/
+      excluded /.rb$/
+      excluded_dirs /^functional/
+
+      app_watch "**/*", included: /book/ do
+        resolver /asdjajd/
+        resolver /asdjajd/
+      end
+
+    end
+
+  end
+
+end
+
+
+
+NOTES:
+- a rule is that there will be ONLY one runnable watchlist and allow multiple app watchlists.
+- object containing criteria, settings, etc. is considered a config object
+- directories are the source for config objects, however, directories and files in the common list will have a reference to the config object that created it.
+- a watch list is created in config/environments/test.rb config file using the watch statement
+  watch "**/*", /book/
+- non-runnable files that are watched are considered "app" files.
+  - a single statement creates a single watch list object.
+
+CONSOLE SESSION NOTE:
+- criteria for all watched directories / files is configured in config/environments/test.rb
+  - config data is loaded and kept in memory during the console session
+  - attempt to allow adding / removing criteria via the console and do a full reload including stopping all of the watched directories, etc. ??
+
+use a pattern to get a list of files and directories.
+
+  - traverse the list
+    NOTE: directories and files have separate included / excluded regexp arrays.
+    - match the directory or file against the included / excluded regexp arrays.
+      - if directory / file should be watched
+        - the directory / file gets added to the actual watch notifier to receive messages about changes.
+        - the directory / file gets added to a common lookup list for easy lookup later with a reference back
+          to the object config object.
+
+      - else, directories / files that do not match get blacklisted right away
+
+when a file is deleted:
+  - for now, do nothing.
+
+when a file is created / moved into the directory:
+  - should be able to follow the same logic and call the same method as for changes, however,
+    DO NOT autorun the file.  everything else.
+
+when a file changes:
+
+  - if -> is it blacklisted?
+    yes
+    - ignore it
+
+  - elsif -> is it whitelisted and runnable?
+    yes
+    - run it
+
+  - elsif -> is it whitelisted and NON-runnable?
+    - can it be resolved to a runnable set of files?
+      yes
+      - run those files
+
+      no
+      - do nothing
+
+  - else
+    - if we have a file that has changed and was not previously on the whitelist, then,
+      the event must have been triggered due to some other action such as after being created or being moved to the containing directory.
+
+      - current file parent object exist and is the parent watchable?
+        yes
+        - whitelist the file with the config object attached
+
+        # parent object will always be a directory, therefore, NEVER runnable.
+        - can file_spec be resolved to a runnable set of files?
+          yes
+          - run those files
+
+        no
+        - blacklist the file due to no parent
+
+  - else
+    - blacklist the file
+
+when a directory changes:
+  - could be a subdirectory is added, etc.
+  - lookup the criteria of the parent directory and match against the directory
+    - if match
+      - add to the common list as normal with a reference back to the object containing the criteria that allowed the directory to be included.
+        In this case, it should be the parent directory found during the lookup.
+
+
+let's say this was the app file that changed.
+how would i resolve the associated test?
+rails does follow convention, however, that does mean all developers will follow it.
+
+# /alldata/rails/gems/duck_test/spec/testdir/app/app01.rb
+
+# this might get very complicated !!!!
+resolving link between non-runnable and runnable files:
+  - a config object is needed for this process
+  - break the full file spec into pieces
+
+    /alldata/rails/gems/duck_test/spec/testdir/app/app01.rb
+
+    | root                                      |  watch directory  | subdir        | file name
+    /alldata/rails/gems/duck_test/spec/testdir  /  app              /               / app01.rb
+
+    # source file
+    /alldata/rails/gems/duck_test/spec/testdir  /  app              /models         / bike.rb
+
+    sub dir mappings
+
+    /alldata/rails/gems/duck_test/spec/testdir/models/bike.rb
+
+    /^models/   -> /^bike/  mapped to --> [
+                                            unit             => /^bike_spec.rb/,
+                                            functional       => /^bike_controller_spec.rb/
+                                          ]
+
+    /^models/   -> /^(.+)/  mapped to --> [
+                                            unit             => /^bike_spec.rb/,
+                                            functional       => /^bike_controller_spec.rb/
+                                          ]
+
+
+    models      -> [unit        => [/^bike_spec/, /^car/, /^truck/],
+                    functional  => [/^bike/, /^car/, /^truck/]
+                    ]
+
+    controllers -> [functional]
+
+
+    # mapped to
+    /alldata/rails/gems/duck_test/spec/testdir  /  spec             / unit          / bike_spec.rb
+    /alldata/rails/gems/duck_test/spec/testdir  /  spec             / functional    / bike_controller_spec.rb
+
+    - note: the runnable watch list is considered the target watchlist in this context.
+
+    - the first task would be find target director(ies)y within the target watchlist.
+      the goal is to build a list of target directories.
+
+      - if the changed file HAS a subdirectory
+        - extract the subdirectory
+        - build a list of translation directories
+
+          # this would be the default order of precedence
+          # i should make the order of precedence configurable
+          - first, add the sub-directory
+          - then, add translation directories attached to the config object
+          - then, add global translation directories
+
+          - the translations will be an array of Strings or regexp's
+
+        - search the target watch list for a subdirectory(ies) matching the translation directory(ies).
+          - there should be a switch that says match first or match all.  this should facilitate the ability
+            to trigger multiple tests when a single file changes.  for instance, when I change model I might
+            want it to run the unit tests and the functional tests as well.
+
+      - if there is no sub directory, then, the root of the runnable watch list is the target directory.
+        - add the watch directory root to the list of directories to search.
+
+      - at this point, we should have a list of target directories to search for matching files.
+
+      # i will not recursively search thru the subdirectories.  this compares the file names ONLY.
+      - loop thru each of the directory(ies)
+
+        # this step requires IO with the disk which will create a little bit of a performance issue, but, worth it.
+        - grab a list of the files contained within the directory
+
+          # each file will have a set of filters used to resolve links between non-runnable and runnable files.
+          # basically, it is an array of regexp's PAIRS
+          - loop thru all of the regexp pairs and compare the first regexp against the source file (non-runnable file that changed)
+            - if the regexp matches
+              - loop thru the files contained in the directory
+                - compare the second regexp in the pair against the target file
+                  - if regexp matches
+                    - add to list of runnable files that should be executed.

data/lib/tasks/duck_tests.rake

@@ -0,0 +1,35 @@
+namespace :test do
+
+  desc "Removes all of the test files using rake test:prepare"
+  task :clean do
+    $:.unshift File.expand_path("spec")
+    require "test_files"
+    TestFiles.clean
+  end
+
+  desc "Runs all of the necessary tasks prior to running the tests"
+  task :prepare do
+    $:.unshift File.expand_path("spec")
+    require "test_files"
+    TestFiles.prepare
+  end
+
+  desc "Runs all of the tests"
+  task :all do
+    $:.unshift File.expand_path("spec")
+    load "all_specs.rb"
+  end
+
+  desc "Tests I used to develop small pieces of code or ideas"
+  task :dev do
+    $:.unshift File.expand_path("spec")
+    load "dev_specs.rb"
+  end
+
+  desc "Run the file watch queue.  Not designed to run with normal tests"
+  task :queue do
+    $:.unshift File.expand_path("spec")
+    load "run_queue.rb"
+  end
+
+end

data/lib/tasks/gem_tasks.rake

@@ -0,0 +1,18 @@
+# once upon a time, I had a series of tasks and gemspecs to build different versions for different platforms.
+# this file was huge.  I made a decision to adandon all of those different gems and simply notify the developer
+# to edit their Gemfile
+require "duck_test/gem/helper"
+
+namespace :local do
+
+  desc "Locally build and release the default gem without dependencies"
+  task :default do
+    DuckTest::Gem::Helper.new.local("duck_test", "duck_test")
+  end
+
+  desc "Locally build and release all of the gems"
+  task :all => [:default]
+
+end
+
+task :local => "local:default"

metadata

@@ -0,0 +1,92 @@
+--- !ruby/object:Gem::Specification
+name: duck_test
+version: !ruby/object:Gem::Version
+  version: 0.1.4
+  prerelease: 
+platform: ruby
+authors:
+- Jeff Duckett
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2012-02-22 00:00:00.000000000 Z
+dependencies: []
+description: DuckTest is a gem that facilitates automated running of TestUnit and
+  RSpec tests directly in the IRB console.  Tests run within a second of being changed.
+email:
+- jeff.duckett@gmail.com
+executables:
+- ducktest
+extensions: []
+extra_rdoc_files: []
+files:
+- lib/tasks/gem_tasks.rake
+- lib/tasks/duck_tests.rake
+- lib/duck_test/config_helper.rb
+- lib/duck_test/version.rb
+- lib/duck_test/console.rb
+- lib/duck_test/default_config.rb
+- lib/duck_test/autoload_config.rb
+- lib/duck_test/config.rb
+- lib/duck_test/base.rb
+- lib/duck_test/option_parser.rb
+- lib/duck_test/usage.rb
+- lib/duck_test/commands.rb
+- lib/duck_test/platforms/dependencies.rb
+- lib/duck_test/platforms/watch_event.rb
+- lib/duck_test/platforms/listener.rb
+- lib/duck_test/platforms/base.rb
+- lib/duck_test/platforms/windows/listener.rb
+- lib/duck_test/platforms/windows/base.rb
+- lib/duck_test/platforms/generic/listener.rb
+- lib/duck_test/platforms/generic/base.rb
+- lib/duck_test/platforms/os_helper.rb
+- lib/duck_test/platforms/mac/listener.rb
+- lib/duck_test/platforms/mac/base.rb
+- lib/duck_test/platforms/mac/listener.rb.orig
+- lib/duck_test/platforms/linux/listener.rb
+- lib/duck_test/platforms/linux/base.rb
+- lib/duck_test/gem/helper.rb
+- lib/duck_test/logger.rb
+- lib/duck_test/railtie.rb
+- lib/duck_test/usage.yml
+- lib/duck_test/frame_work/file_manager.rb
+- lib/duck_test/frame_work/base.rb
+- lib/duck_test/frame_work/queue.rb
+- lib/duck_test/frame_work/rspec/base.rb
+- lib/duck_test/frame_work/rspec/frame_work.rb
+- lib/duck_test/frame_work/watch_config.rb
+- lib/duck_test/frame_work/filter_set.rb
+- lib/duck_test/frame_work/map.rb
+- lib/duck_test/frame_work/test_unit/base.rb
+- lib/duck_test/frame_work/test_unit/frame_work.rb
+- lib/duck_test/frame_work/queue_event.rb
+- lib/duck_test.rb
+- lib/notes.txt
+- bin/ducktest
+homepage: http://www.jeffduckett.com/
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.11
+signing_key: 
+specification_version: 3
+summary: DuckTest runs TestUnit and RSpec tests directly in the IRB console.
+test_files: []
+has_rdoc: