matest 1.0.1 → 1.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 19f65ecc765b4eb7cdb7eaf25c6f5648d9c901f2
4
- data.tar.gz: ec5e805afbf404d59335d25815b37aeb6cbe4578
3
+ metadata.gz: 51563e6bdadf816457727fca0a2121d773057f84
4
+ data.tar.gz: dda3baf6631a2461dcc68ef323e84b54f186f66c
5
5
  SHA512:
6
- metadata.gz: 9dfd3eb0dae94b317f4490b9f32ac0c74b0e8f1bb823c186137cd385bb6dca7d96ad9ad4901124254a3e5683f066142246d57bdb9eef6041e7f9736288ba5337
7
- data.tar.gz: f41231aa62ed1453868d538734f6355ddc5409c0b9b9afaea4886d35a000f205ffa720f4750d40c2639bf3698a05a716119d7b7aa8e0d8eb4344f7894c82356b
6
+ metadata.gz: b12c6c27102ee26adc1be14ff57f55e4386efb741ab6f611062571094f9eb576ecd967f5a418807fa13ee5bc40e3cc19f615491d62ed05490230083a4a7439a6
7
+ data.tar.gz: c02ff5d49a3bf1e17a0aef285e9a216b4c4976313b9141535e85d50506de03e404e6026d71e438a0c84b00475ae9938f1f2a2e520a4d9432ed2ce724f6ffe3ab
data/README.md CHANGED
@@ -16,22 +16,22 @@ This means that:
16
16
 
17
17
  ## Usage
18
18
 
19
- To run Matest, you just need to execute the `mt` command, passing as arguments the desired test files.
19
+ To run Matest, you just need to execute the `matest` command, passing as arguments the desired test files.
20
20
 
21
21
  ```bash
22
- $ mt spec/my_spec.rb
22
+ $ matest spec/my_spec.rb
23
23
  ```
24
24
 
25
25
  You can also use wildcards.
26
26
 
27
27
  For example, to run all the specs in a directory:
28
28
  ```bash
29
- $ mt spec/*_spec.rb
29
+ $ matest spec/*_spec.rb
30
30
  ```
31
31
 
32
32
  Or to run recursively
33
33
  ```bash
34
- $ mt spec/**/*_spec.rb
34
+ $ matest spec/**/*_spec.rb
35
35
  ```
36
36
 
37
37
  ## Specs
@@ -131,6 +131,10 @@ scope do
131
131
  end
132
132
  ```
133
133
 
134
+ ## The output
135
+
136
+ In case the test fails, the instance variables you define inside it as well as the ones defined by `let` and `let!` are tracked and you'll see their final values in the output.
137
+
134
138
  ## Matchers
135
139
 
136
140
  Matest doesn't come with predefined matchers, it doesn't need them. In fact, the concept of a matcher is not required, because of the natural assertions nature of the library.
data/Rakefile CHANGED
@@ -7,5 +7,5 @@ task :matest do
7
7
  files = arg_files || all_files
8
8
  puts "\nRuning tests for: #{ files.join(" ") }\n\n"
9
9
 
10
- system *["./bin/mt"].concat(files)
10
+ system *["./bin/matest"].concat(files)
11
11
  end
data/bin/{mt → matest} RENAMED
File without changes
@@ -1,3 +1,3 @@
1
1
  module Matest
2
- VERSION = "1.0.1"
2
+ VERSION = "1.1.0"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: matest
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.1
4
+ version: 1.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Federico Iachetti
@@ -42,7 +42,7 @@ description: Natural assertions test suite.
42
42
  email:
43
43
  - iachetti.federico@gmail.com
44
44
  executables:
45
- - mt
45
+ - matest
46
46
  extensions: []
47
47
  extra_rdoc_files: []
48
48
  files:
@@ -51,7 +51,7 @@ files:
51
51
  - LICENSE.txt
52
52
  - README.md
53
53
  - Rakefile
54
- - bin/mt
54
+ - bin/matest
55
55
  - lib/matest.rb
56
56
  - lib/matest/spec_printer.rb
57
57
  - lib/matest/spec_status.rb