gen-test 0.1.0 → 0.1.1

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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 84646aec5140b201837409f37dc51fd298c8fb5aff1c0c5d7026068c2aa7ebbd
4
- data.tar.gz: ed3b318092f96b74707c9426c9f59536e47071bc1ec68de5d1deeef7d25125bd
3
+ metadata.gz: 44397a8deb3d218362e1e7881f011ceb05d594a4ef8543111f78d4e51ccbce84
4
+ data.tar.gz: 6933716b464c2366e893a03c430332c2ad86700c7d78341fb0bbe9fc8a8b23e4
5
5
  SHA512:
6
- metadata.gz: e9b4811b8ff6bdda4268092759793053f7d1af6a74ba1ddfeff540917f8b3b92639fd32c3d77ca32e03f38efaa7df1f77c609eb564ca67b978673b2480906a6f
7
- data.tar.gz: e4ff31c90d8dffd0398ab0a965c222084f1751e6ede57c8202d351bdab69ba52baeda73394f57d36a9a299df00180a6a9a144dfc25515cc0a3c2338779f56906
6
+ metadata.gz: b48d7d26e035eeecd2a662c506400877947d511457fcfaec69bfa3481cba3d4bb9d77839211e13d1cb00f4c40e02c85f24c666bd72756389be9afbf415bb2b8e
7
+ data.tar.gz: ed28df91d63613cb14c88907a82d6aedd79a08f3ff1dcb1b9f41215b079eae6fb17a5e3fcf70d89c6d13ae1feb8e7eea0449348b1550b4afcd982d7a0e539998
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- gen-test (0.1.0)
4
+ gen-test (0.1.1)
5
5
  faker (~> 1.9.6)
6
6
  regexp-examples (~> 1.5.0)
7
7
 
data/README.md CHANGED
@@ -1,3 +1,5 @@
1
+ ![Gem](https://img.shields.io/gem/v/gen-test)
2
+
1
3
  Gen::Test
2
4
  =========
3
5
 
@@ -24,13 +26,27 @@ end
24
26
  Why?
25
27
  ====
26
28
 
27
- Generative testing has much value for unit, acceptance and integration testing over TDD and BDD, while it's
28
- value doesn't come for free.
29
+ Generative or property based testing is an approach to testing where tests are automatically generated from
30
+ defintions for properties of the system being tested. While slower, generative testing has much value for
31
+ unit, acceptance and integration testing over TDD and BDD.
32
+
33
+ For example, generative tests still have much value when they're written after your code, and when extensive
34
+ can be quite useful for integration testing.
35
+
29
36
  [Others](https://www.youtube.com/watch?v=r5i_OiZw6Sw) [argue](http://www.quviq.com/products/quickcheck-for-c/)
30
37
  this point well.
31
38
 
32
- There seemed to be a need simple, extensible, implementation for Ruby, that wasn't a DSL or a framework. This
33
- module is still very incomplete, but it's proven useful.
39
+ There seemed to be a need for a simple, extensible, implementation for Ruby, that isn't a DSL or a framework.
40
+ This module strives to serve that purpose, it's still very incomplete, but it's proven useful.
41
+
42
+ You can use Gen::Test along side other tests written in a different style and it's designed to be used with
43
+ other testing frameworks like [Minitest](https://github.com/seattlerb/minitest) and [Rspec](https://rspec.info/).
44
+
45
+ It's also extensible, defining a simple protocol for extensiblity. Just define a `generate` method that can
46
+ be called with no arguments and returns your generated data on any object and it can be used as a generator.
47
+
48
+ Many core objects have already been extended (see [lib/ext_core.rb](lib/ext_core.rb)). You can also make use
49
+ of `Gen::Generator` which is a Proc-like object that implements the `generate` method.
34
50
 
35
51
  Install
36
52
  =======
@@ -43,6 +59,12 @@ or, add
43
59
 
44
60
  to your Gemfile.
45
61
 
62
+ Extentions
63
+ ==========
64
+
65
+ - [Contracts::Gen](https://github.com/delonnewman/contracts-gen), defines generators for most of
66
+ contracts the [Contracts](https://github.com/egonSchiele/contracts.ruby) gem.
67
+
46
68
  See Also
47
69
  ========
48
70
 
@@ -18,6 +18,7 @@ Gem::Specification.new do |spec|
18
18
  spec.metadata["homepage_uri"] = spec.homepage
19
19
  spec.metadata["source_code_uri"] = spec.homepage
20
20
  spec.metadata["changelog_uri"] = "#{spec.homepage}#changelog"
21
+ spec.metadata["documentation_uri"] = "https://www.rubydoc.info/gems/gen-test"
21
22
 
22
23
  # Specify which files should be added to the gem when it is released.
23
24
  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
@@ -1,5 +1,5 @@
1
1
  module Gen
2
2
  module Test
3
- VERSION = "0.1.0"
3
+ VERSION = "0.1.1"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gen-test
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Delon Newman
@@ -121,6 +121,7 @@ metadata:
121
121
  homepage_uri: https://github.com/delonnewman/gen-test
122
122
  source_code_uri: https://github.com/delonnewman/gen-test
123
123
  changelog_uri: https://github.com/delonnewman/gen-test#changelog
124
+ documentation_uri: https://www.rubydoc.info/gems/gen-test
124
125
  post_install_message:
125
126
  rdoc_options: []
126
127
  require_paths: