test-unit-around 0.0.1 → 0.0.2

data/README.md

@@ -1,54 +1,73 @@
+
 # Test::Unit::Around
 
 Use an around filter instead or in addition to test/unit's setup and teardown methods.
+This is imho especially useful in combination with context blocks provided by e.g.,
+the test-unit-context gem to avoid duplicate code.
 
 ## Installation
 
 Add this line to your application's Gemfile:
 
-    group :test do
-      gem 'test-unit-around'
-    end
+```ruby
+group :test do
+  gem 'test-unit-around'
+end
+```
 
 And then execute:
 
-    $ bundle
+```
+$ bundle
+```
+
+Alternatively, you can of course install it without bundler via:
+
+```
+$ gem install test-unit-around
+```
 
 ## Usage
 
 Use it in your tests:
 
-<pre>
-class FeatureTest &lt; Test::Unit::TestCase
+```ruby
+class FeatureTest < Test::Unit::TestCase
   def around
-    # Before the test runs
+    # Before a test runs
 
     yield
 
-    # After the test has run
+    # After a test has run
   end
 
   def test_feature
-    # The test itself
+    # First test
   end
+
+  ...
 end
-</pre>
+```
 
 You can as well use around as a class method:
 
-<pre>
-class FeatureTest &lt; Test::Unit::TestCase
+```ruby
+class FeatureTest < Test::Unit::TestCase
   around do |test|
-    # Before the test runs
+    # Before a test runs
 
     test.run
 
-    # After the test has run
+    # After a test has run
+  end
+
+  test "feature" do
+    # First test
   end
 
   ...
 end
-</pre>
+```
 
 ## Contributing
 

data/lib/test/unit/around/version.rb

@@ -1,7 +1,7 @@
 module Test
   module Unit
     module Around
-      VERSION = "0.0.1"
+      VERSION = "0.0.2"
     end
   end
 end

data/test-unit-around.gemspec

@@ -17,6 +17,6 @@ Gem::Specification.new do |s|
   s.require_paths = ["lib"]
 
   s.add_development_dependency "rake"
-  s.add_dependency 'test-unit', '>= 2.4.0'
+  s.add_dependency 'test-unit', '>= 2.4.4'
 end
 

data/test/test/unit/around_test.rb

@@ -3,42 +3,62 @@ require File.expand_path("../../../../lib/test/unit/around", __FILE__)
 require "test/unit"
 
 class AroundClassMethodTest < Test::Unit::TestCase
+  setup do
+    assert_nil @before
+    assert_nil @after
+  end
+
   around do |test|
     @before = :before
 
     test.run
 
     @after = :after
+  end
 
+  teardown do
+    assert_equal :before, @before
     assert_equal :after, @after
   end
 
-  def test_around
+  test "around" do
     assert_equal :before, @before
+
     assert_nil @after
   end
 end
 
 class AroundInstanceMethodTest < Test::Unit::TestCase
+  def setup
+    assert_nil @before
+    assert_nil @after
+  end
+
   def around
     @before = :before
 
     yield
 
     @after = :after
+  end
 
+  def teardown
+    assert_equal :before, @before
     assert_equal :after, @after
   end
 
   def test_around
     assert_equal :before, @before
+
     assert_nil @after
   end
 end
 
 class WithoutAroundTest < Test::Unit::TestCase
   def test_something
+    assert_nil @before
     assert_nil @after
+
     assert_equal 1, 1
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: test-unit-around
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -34,7 +34,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.4.0
+        version: 2.4.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -42,7 +42,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.4.0
+        version: 2.4.4
 description: Use around instead or in combination with test/unit's setup and teardown
   methods
 email: