oojspec 0.0.4 → 0.0.5

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -74,8 +74,8 @@ just like Mocha but it didn't give any guarantees about the order of execution o
74
74
  I needed that guarantee for some integration tests.
75
75
 
76
76
  But on the other side it is pretty modular and I would be able to take advantage of their
77
- assertions and expectations syntax as well as its reporter (although I'm still not happy with
78
- the default html reporter and I'll probably have to write a new one in the future).
77
+ assertions and expectations syntax as well as its reporter (although I had to change it a bit so
78
+ that it fit my taste).
79
79
 
80
80
  As Buster.js allowed me to focus on the runner itself I decided to begin this new project.
81
81
 
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta http-equiv="content-type" content="text/html; charset=utf-8">
5
5
 
6
- <title>Buster.js Test Runner</title>
6
+ <title>OOJSpec Test Runner</title>
7
7
 
8
8
  <%= stylesheet_link_tag "oojspec" %>
9
9
  <%= javascript_include_tag "oojspec" %>
@@ -1,3 +1,3 @@
1
1
  module Oojspec
2
- VERSION = "0.0.4"
2
+ VERSION = "0.0.5"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: oojspec
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.4
4
+ version: 0.0.5
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -86,7 +86,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
86
86
  version: '0'
87
87
  segments:
88
88
  - 0
89
- hash: 2483002507602501921
89
+ hash: 4089390275139911858
90
90
  required_rubygems_version: !ruby/object:Gem::Requirement
91
91
  none: false
92
92
  requirements:
@@ -95,7 +95,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
95
95
  version: '0'
96
96
  segments:
97
97
  - 0
98
- hash: 2483002507602501921
98
+ hash: 4089390275139911858
99
99
  requirements: []
100
100
  rubyforge_project:
101
101
  rubygems_version: 1.8.24