test_launcher 0.0.3 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: bbd6981a7b53e9af503b959d87bd3dc21bc312a0
-  data.tar.gz: 1c2978d49096d3af9cc704c30d83eb1c554cff48
+  metadata.gz: 076fd8dd620db12cc980d5e0feb4e64bb0eb19d0
+  data.tar.gz: e69f9e56de5f8dd4c952301387e382ea298c8862
 SHA512:
-  metadata.gz: 30a4da05547da73f41746d1a839052493938964094700ea009a9ff37c3506a8d1e9ec348a4cbe6c62fba22ff4587e0bea2fc7b8e9714dff7b7f99468e2ce4a24
-  data.tar.gz: 6d3fb76d08ef634a12108f74643e86f58e88b601b493e07f7ce72b2ef029a1fcb6562b8ffc5c162af223aa6f693fb49ca7523d1261c951defd923ba821b9490d
+  metadata.gz: ae02ab9956036df7e73ce62f6fad7ed39027eb0220c1e3516b726e47c60db3eb79f7522a8f8f8e0a5cbe0f8b8968a3b56aed6f8405e52319b04705f7471a131e
+  data.tar.gz: 9a55b973f8896de1ccbfbc34d25cdff69efbd3007f2857b27d21c5ca866a02fec717350cd76a8a5a8c7ac6b5e505de4e1c489b4e0a685e6eca23fbc18d164436

data/README.md

@@ -1,31 +1,107 @@
-# TestLauncher
+#Test Launcher -->
 
-TODO: Write a gem description
+Test Launcher takes some input and tries to figure out what test you want to run. It makes running tests on the command line much easier.  Test Launcher works with Minitest and probably TestUnit.  RSpec isn't supported.  If you use RSpec and you think this would be handy, let me know!
 
-## Installation
+Let's suppose you want to run the test `test_name` in your `blog_post_test.rb`.  
 
-Add this line to your application's Gemfile:
+Without Test Launcher, you might type this:
 
-```ruby
-gem 'test_launcher'
 ```
+ruby -I test test/models/blog_post_test.rb --name=test_blog_name_thing
+```
+
+But with Test Launcher, you can just type this:
+
+```
+t test_blog_name_thing
+
+#=> ruby -I test test/models/blog_post_test.rb --name=test_blog_name_thing
+```
+
+What if you want to run a whole file?  Just go for it!
+
+```
+t blog_post_test
+
+#=> ruby -I test test/models/blog_post_test.rb
+```
+
+What if you just have the class name for the test?
 
-And then execute:
+```
+t BlogPostTest
+
+#=> ruby -I test test/models/blog_post_test.rb
+```
+
+But what if you aren't specific enough?
+
+```
+t test_blog_na
 
-    $ bundle
+#=> Found 10 test methods in 3 files.
+#=> Running most recently edited. Run with '--all' to run all the tests.
+#=> ruby -I test test/models/blog_post_test.rb --name=test_blog_name_thing
+```
+
+Super fun? OH YEAH!
+
+#Installation
 
-Or install it yourself as:
+To install:
+
+```
+gem install test_launcher
+```
 
-    $ gem install test_launcher
+#Setup
 
-## Usage
+This gem installs one executable called `test_launcher`.  That executable must be called with the `find` method, like so:
 
-TODO: Write usage instructions here
+```
+test_launcher find test_name_to_find
+```
+
+For me, that's way too much to type, so I recommend adding an alias to your `.bash_profile` like so:
+
+```
+alias t="test_launcher find"
+```
+
+Now you can just type `t` instead of `test_launcher find`.  Much nicer!
+
+#Usage
+
+Test Launcher searches for tests based on your input.
+
+Suppose you type `t thing`.  It will run tests using this priority preference:
+
+1. A single, specific test method name or partial name
+  - `def test_the_thing`
+
+1. Multiple test method names in the same file
+  - `def test_the_thing` and `def test_the_other_thing`
+
+1. A single test file
+  - matches on `thing_test.rb`
+
+1. Any test file based on a generic search
+  - runs `stuff_test.rb` because it found the word `thing` inside of it
+
+Any time it matches multiple files, it will default to running the most recently edited file.  You can append `--all` if you want to run all matching tests.
+
+#Does it work with inline gems?
+
+Yes!
+
+Test Launcher will automatically move to the correct subdirectory in order to run the tests.  For example, if `thing_test.rb` is within your inline_gem, you can run:
+
+
+```
+t thing_test
+
+#=> cd ./path/to/inline_gem && ruby -I test test/thing_test.rb
+```
 
-## Contributing
+You don't have to run Test Launcher from the root of your project either.  It will figure things out.
 
-1. Fork it ( https://github.com/[my-github-username]/test_launcher/fork )
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create a new Pull Request

data/lib/test_launcher/version.rb

@@ -1,3 +1,3 @@
 module TestLauncher
-  VERSION = "0.0.3"
+  VERSION = "0.1.0"
 end

data/test_launcher.gemspec

@@ -18,6 +18,7 @@ Gem::Specification.new do |spec|
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.require_paths = ["lib"]
 
+  spec.add_dependency("thor", [">= 0.19", "< 1.0"])
   spec.add_development_dependency "bundler", "~> 1.7"
   spec.add_development_dependency "rake", "~> 10.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: test_launcher
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.1.0
 platform: ruby
 authors:
 - Pete Kinnecom
@@ -10,6 +10,26 @@ bindir: bin
 cert_chain: []
 date: 2015-05-13 00:00:00.000000000 Z
 dependencies:
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.19'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.19'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement