orb 0.0.2 → 0.0.4
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.
- data/README.md +28 -1
- data/orb.gemspec +4 -6
- metadata +5 -5
data/README.md
CHANGED
|
@@ -1 +1,28 @@
|
|
|
1
|
-
|
|
1
|
+
# ORB
|
|
2
|
+
|
|
3
|
+
# What is it?
|
|
4
|
+
|
|
5
|
+
ORB is a tool to write tests interactively. Add `ORB{}` to one of your
|
|
6
|
+
tests, then when you run your test suite, you'll get dropped to a
|
|
7
|
+
REPL, where you can explore the test's context and build an
|
|
8
|
+
implementation for the test, before automatically writing it out to
|
|
9
|
+
the file and replacing the `ORB{}` call.
|
|
10
|
+
|
|
11
|
+
# Wait... What?
|
|
12
|
+
|
|
13
|
+
[Watch the video](#) (Coming Soon).
|
|
14
|
+
|
|
15
|
+
# Can I use this with \#{framework}?
|
|
16
|
+
|
|
17
|
+
Probably. Have a look at `lib/orb/adapters/rspec.rb`. It's a pretty simple
|
|
18
|
+
format.
|
|
19
|
+
|
|
20
|
+
# Why do I have to call ORB with an empty block?
|
|
21
|
+
|
|
22
|
+
Ruby 1.8.6 and onward doesn't have a reliable way to evaluate code in
|
|
23
|
+
the context that calls a method without explicitly passing it, or
|
|
24
|
+
grabbing the binding from a block. The block is easier to type.
|
|
25
|
+
|
|
26
|
+
# I have a great idea...
|
|
27
|
+
|
|
28
|
+
Great! Let me know, or even better, send me a pull request.
|
data/orb.gemspec
CHANGED
|
@@ -1,15 +1,13 @@
|
|
|
1
1
|
Gem::Specification.new do |gem|
|
|
2
2
|
gem.name = 'orb'
|
|
3
|
-
gem.version = "0.0.
|
|
3
|
+
gem.version = "0.0.4"
|
|
4
4
|
|
|
5
5
|
gem.author, gem.email = 'Burke Libbey', "burke@burkelibbey.org"
|
|
6
6
|
|
|
7
|
-
gem.summary = "
|
|
8
|
-
gem.description = "
|
|
7
|
+
gem.summary = "ORB is a tool to write tests interactively"
|
|
8
|
+
gem.description = "ORB is a tool to write tests interactively. Add ORB{} to one of your tests, then when you run your test suite, you'll get dropped to a REPL, where you can explore the test's context and build an implementation for the test, before automatically writing it out to the file and replacing the ORB{} call."
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
gem.has_rdoc = false
|
|
10
|
+
gem.has_rdoc = false
|
|
13
11
|
|
|
14
12
|
gem.files = %w[
|
|
15
13
|
LICENSE
|
metadata
CHANGED
|
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
|
|
|
5
5
|
segments:
|
|
6
6
|
- 0
|
|
7
7
|
- 0
|
|
8
|
-
-
|
|
9
|
-
version: 0.0.
|
|
8
|
+
- 4
|
|
9
|
+
version: 0.0.4
|
|
10
10
|
platform: ruby
|
|
11
11
|
authors:
|
|
12
12
|
- Burke Libbey
|
|
@@ -14,11 +14,11 @@ autorequire:
|
|
|
14
14
|
bindir: bin
|
|
15
15
|
cert_chain: []
|
|
16
16
|
|
|
17
|
-
date: 2010-
|
|
17
|
+
date: 2010-05-01 00:00:00 -05:00
|
|
18
18
|
default_executable:
|
|
19
19
|
dependencies: []
|
|
20
20
|
|
|
21
|
-
description:
|
|
21
|
+
description: ORB is a tool to write tests interactively. Add ORB{} to one of your tests, then when you run your test suite, you'll get dropped to a REPL, where you can explore the test's context and build an implementation for the test, before automatically writing it out to the file and replacing the ORB{} call.
|
|
22
22
|
email: burke@burkelibbey.org
|
|
23
23
|
executables: []
|
|
24
24
|
|
|
@@ -62,6 +62,6 @@ rubyforge_project:
|
|
|
62
62
|
rubygems_version: 1.3.6
|
|
63
63
|
signing_key:
|
|
64
64
|
specification_version: 3
|
|
65
|
-
summary:
|
|
65
|
+
summary: ORB is a tool to write tests interactively
|
|
66
66
|
test_files: []
|
|
67
67
|
|