slacker 0.0.11 → 1.0.0

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.
Files changed (4) hide show
  1. data/README.markdown +14 -34
  2. data/lib/slacker/version.rb +1 -1
  3. data/slacker.gemspec +2 -2
  4. metadata +4 -4
data/README.markdown CHANGED
@@ -2,29 +2,29 @@
2
2
  Behavior Driven Development for SQL Server
3
3
 
4
4
  # Description
5
- __Slacker__ is a Ruby (RSpec-based) framework for developing automated tests for SQL Server programmable objects such as stored procedures and scalar/table functions.
5
+ Slacker is a Ruby (RSpec-based) framework for developing automated tests for SQL Server programmable objects such as stored procedures and scalar/table functions.
6
6
 
7
7
  # Installation
8
8
  gem install slacker
9
9
 
10
- ## Requirements
10
+ ### Requirements
11
11
 
12
- __Slacker__ requires Ruby 1.9.2.
12
+ * Ruby 1.9.2.
13
13
 
14
14
  Runs on Windows and Linux.
15
15
 
16
- Before installing __Slacker__ on Windows, you need to install the [Ruby Windows Development Kit](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit) (__ruby-odbc__ contains native extensions).
16
+ _Note_: Before installing on Windows, you need to install the [Ruby Windows Development Kit](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit).
17
17
 
18
- # Usage
19
- To create a new __Slacker__ project, run the following command:
18
+ # Quick Start
19
+ To create a new Slacker project, run the following command:
20
20
 
21
21
  slacker_new my_project
22
22
 
23
- This will create a directory `my_project` in your current directory and will populate it with the files of a __Slacker__ project scaffold.
23
+ This will create a new project directory `my_project`.
24
24
 
25
- Navigate to your new project directory and modify file `database.yml` to tell __Slacker__ which database it should connect to.
25
+ Navigate to the new project directory and modify file `database.yml` to tell Slacker which database to connect to.
26
26
 
27
- Then while in your project directory run __Slacker__:
27
+ Run Slacker:
28
28
 
29
29
  slacker
30
30
 
@@ -34,36 +34,16 @@ If all is good, you should see something like this:
34
34
  .....
35
35
 
36
36
  Finished in 0.05222 seconds
37
- 5 examples, 0 failures
37
+ 7 examples, 0 failures
38
38
 
39
39
  Next, check out sample file `my_project\spec\sample_1.rb` to see the BDD specification you just executed.
40
40
 
41
- Also take a look at the SQL files generated in folder `my_project\debug\passed_examples`. Those are the actual scripts __Slacker__ generated and executed against your database.
41
+ Also take a look at the SQL files generated in folder `my_project\debug\passed_examples`. Those are the actual SQL scripts Slacker generated and executed against your database.
42
42
 
43
- Pop any of these scripts into SQL Server Management Studio and run to see the actual results received by __Slacker__.
43
+ # Resources
44
44
 
45
- Note that all the scripts are executed in their own transaction which is rolled back at the end.
46
-
47
- This ensures that:
48
-
49
- 1. When __Slacker__ finishes its run, it leaves the database in the same exact state as it found it.
50
-
51
- 2. All examples (see `sample_1.rb`) are executed in isolation from each other. No example can interfere with the results of any of the other examples.
52
-
53
- # Documentation TODO
54
-
55
- Document the following features:
56
-
57
- * Slacker project
58
- * Project structure
59
- * Configuration
60
- * Running Slacker
61
- * DSL
62
- * SQL Templates
63
- * Data Fixtures
64
- * Test Matrices
65
- * Generated SQL
66
- * Debugging
45
+ * [__Documentation__](https://github.com/vassilvk/slacker/wiki)
46
+ * [__Mailing List__](https://groups.google.com/forum/#!forum/ruby_slacker)
67
47
 
68
48
 
69
49
  # LICENSE
data/lib/slacker/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Slacker
2
- VERSION = "0.0.11"
2
+ VERSION = "1.0.0"
3
3
  end
data/slacker.gemspec CHANGED
@@ -7,9 +7,9 @@ Gem::Specification.new do |s|
7
7
  s.version = Slacker::VERSION
8
8
  s.authors = ["Vassil Kovatchev"]
9
9
  s.email = ["vassil.kovatchev@gmail.com"]
10
- s.homepage = "https://github.com/vassilvk/slacker"
10
+ s.homepage = "https://github.com/vassilvk/slacker/wiki"
11
11
  s.summary = %q{Behavior Driven Development for SQL Server}
12
- s.description = %q{RSpec-based framework for developing automated tests for SQL Server programmable objects such as stored procedures and scalar/table functions}
12
+ s.description = %q{RSpec-based framework for developing automated tests for SQL Server}
13
13
 
14
14
  s.rubyforge_project = "slacker"
15
15
 
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: slacker
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.0.11
5
+ version: 1.0.0
6
6
  platform: ruby
7
7
  authors:
8
8
  - Vassil Kovatchev
@@ -10,7 +10,7 @@ autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
12
 
13
- date: 2011-06-27 00:00:00 Z
13
+ date: 2011-06-28 00:00:00 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: bundler
@@ -45,7 +45,7 @@ dependencies:
45
45
  version: 2.5.0
46
46
  type: :runtime
47
47
  version_requirements: *id003
48
- description: RSpec-based framework for developing automated tests for SQL Server programmable objects such as stored procedures and scalar/table functions
48
+ description: RSpec-based framework for developing automated tests for SQL Server
49
49
  email:
50
50
  - vassil.kovatchev@gmail.com
51
51
  executables:
@@ -114,7 +114,7 @@ files:
114
114
  - spec/test_files/matcher/test_1.csv
115
115
  - spec/slacker_spec.rb
116
116
  - spec/application_spec.rb
117
- homepage: https://github.com/vassilvk/slacker
117
+ homepage: https://github.com/vassilvk/slacker/wiki
118
118
  licenses: []
119
119
 
120
120
  post_install_message: