splot 0.5.2 → 0.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +16 -10
  3. data/lib/splot/version.rb +1 -1
  4. data/splot.gemspec +2 -2
  5. metadata +5 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 9a4dbbd8b1e8bf5f568d828642ee7f0481dfbad4
4
- data.tar.gz: 6f351772ddfb8fedbd4467c73487da2b1d7e3b43
3
+ metadata.gz: 31c16e62c494cad56ecfc7d04a123fd1fc645d81
4
+ data.tar.gz: b688a73a2d6d5cb4bf27f5011ed22c47ec841d25
5
5
  SHA512:
6
- metadata.gz: 57d5624e70eb25809a87cabdc7c10982e01e79b600839c1aa22f90c68ef94bf166a1145ef6f866d4bce48298a82e694d9b63c6f119c22f21291795ceadcfd9d7
7
- data.tar.gz: be6812a2c2853dd81f6f7fa7f35bc56fb3dd47f10b566eb5193e60f392fdb09e77d5a246a252279761accf98ff596eebd0e3abcbf92c326ed25fbee1fcbe44cc
6
+ metadata.gz: 15a2855e04e9d1fe34404b18c8ec3bab1347d10401a45ca356d554266e9c03a27e2c3edc4d3ea9f1ced4b751e669b2afaa595a195d1895f240e6b84191b0afce
7
+ data.tar.gz: db4ef9333518ce6fc72c174f6c9498e5213031563cd4dd6fd25b6ff56b5735499cca0f1cd202fa3dd4693d5bf394a15680a8b4ba00256c2111eff2103c8d51d1
data/README.md CHANGED
@@ -20,22 +20,22 @@ Or install it yourself as:
20
20
 
21
21
  First, play with `splot` on the command line. Jump into a project root directory. Want to run a test? Try this:
22
22
 
23
- # splot -f test/models/foo_test.rb
23
+ splot -f test/models/foo_test.rb
24
24
 
25
25
  Do you use rspec? Nothing changes, except for the path to the file.
26
26
 
27
- # splot -f spec/models/foo_spec.rb
27
+ splot -f spec/models/foo_spec.rb
28
28
 
29
29
  Want to run a test on a specific line? No problem:
30
30
 
31
- # splot -f test/models/foo_test.rb -l 44
32
- # splot -f spec/models/foo_spec.rb -l 44
31
+ splot -f test/models/foo_test.rb -l 44
32
+ splot -f spec/models/foo_spec.rb -l 44
33
33
 
34
34
  When using `Test::Unit`, `splot` will automatically figure out the name of the test corresponding to the line number you give.
35
35
 
36
36
  Now, you need a faster feedback loop, so you decide you want a preloader:
37
37
 
38
- # splot -f test/models/foo_test.rb -p zeus
38
+ splot -f test/models/foo_test.rb -p zeus
39
39
 
40
40
  That's about all there is to the command line!
41
41
 
@@ -43,20 +43,26 @@ That's about all there is to the command line!
43
43
 
44
44
  Editing `app/models/foo.rb`? `splot` can figure out which test to run:
45
45
 
46
- # splot -f app/models/foo.rb
46
+ splot -f app/models/foo.rb
47
47
 
48
- In this case, it'll look for a test at `test/models/foo_test.rb` or `spec/models/foo_spec.rb`.
48
+ In this case, it'll look for a test at `test/models/foo_test.rb` or `spec/models/foo_spec.rb`. This way, you can shove whatever file you happen to be looking at in your text editor at `splot` and it will "just work."
49
49
 
50
50
  ## vim-dispatch integration
51
51
 
52
52
  I'm a huge fan of vim dispatch. Here's my `.vimrc` entries that bind `<F5>` to "run the test at the current cursor position" and `<F6>` to "run the whole test file," respectively:
53
53
 
54
- map <f5> :w <cr> :execute "Dispatch splot -p spring -f % -l " . ( line(".") + 1 )<cr>
55
- map <f6> :w <cr> :Dispatch splot -p spring -f %<cr>
54
+ :map <f5> :w <cr> :execute "Dispatch splot -p spring -f % -l " . ( line(".") + 1 )<cr>
55
+ :map <f6> :w <cr> :Dispatch splot -p spring -f %<cr>
56
56
 
57
- ## Notes
57
+ ## Notes and planned features
58
58
 
59
59
  1. When invoking a `Test::Unit` test, `splot` defaults to using the `rake test`. This is to be compatible with preloaders like `spring` or `zeus`.
60
+ 2. There is cucumber support, too. I hope it works.
61
+ 3. I'm planning on adding git integration. Think "auto stage my changes if the tests pass."
62
+ 4. `vim-dispatch` seems to be unaware of when a test run passes, causing the "quickfix window" to stick around, even when there isn't a failure. I can potentially work around it in `splot`.
63
+ 5. I may write a small vim plugin to simplify the above dispatch mappings. It doesn't seem super necessary at this point, and I like to keep my plugin list small.
64
+ 6. I'd like to implement project level configuration. That way, you can store the information necessary to teach `splot` how to run your tests inside your project, kind of like how a `ruby-version` file configures the version of ruby you use.
65
+ 7. More context specific handlers. For example, running `splot` on a `.gemspec` file should build the gem (if the tests all pass). Ideally, this would be extensible and not bundled in this gem.
60
66
 
61
67
  ## Contributing
62
68
 
data/lib/splot/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Splot
2
- VERSION = "0.5.2"
2
+ VERSION = "0.5.3"
3
3
  end
data/splot.gemspec CHANGED
@@ -8,9 +8,9 @@ Gem::Specification.new do |spec|
8
8
  spec.version = Splot::VERSION
9
9
  spec.authors = ["ntl"]
10
10
  spec.email = ["nathanladd+github@gmail.com"]
11
- spec.description = %q{Run any test from any file from any project :)}
11
+ spec.description = %q{Run any test from any file from any project. When using Test::Unit, specify an individual test by line number the way you can in rspec. Easily integrate "run the tests corresponding to this file" in your editor.}
12
12
  spec.summary = %q{Run any test from any file from any project :)}
13
- spec.homepage = ""
13
+ spec.homepage = "https://github.com/ntl/splot"
14
14
  spec.license = "MIT"
15
15
 
16
16
  spec.files = `git ls-files`.split($/)
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: splot
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.2
4
+ version: 0.5.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - ntl
@@ -94,7 +94,9 @@ dependencies:
94
94
  - - '>='
95
95
  - !ruby/object:Gem::Version
96
96
  version: '0'
97
- description: Run any test from any file from any project :)
97
+ description: Run any test from any file from any project. When using Test::Unit, specify
98
+ an individual test by line number the way you can in rspec. Easily integrate "run
99
+ the tests corresponding to this file" in your editor.
98
100
  email:
99
101
  - nathanladd+github@gmail.com
100
102
  executables:
@@ -120,7 +122,7 @@ files:
120
122
  - test/fixtures/test_unit_example_test.rb
121
123
  - test/splot_test.rb
122
124
  - test/test_helper.rb
123
- homepage: ''
125
+ homepage: https://github.com/ntl/splot
124
126
  licenses:
125
127
  - MIT
126
128
  metadata: {}