moneypools-thinking-sphinx 1.2.11 → 1.2.12

data/README.textile

@@ -12,24 +12,9 @@ Fork on GitHub and after you've committed tested patches, send a pull request.
 
 To quickly see if your system is ready to run the thinking sphinx specs, run the contribute.rb script found in the project root directory. Use the following instructions to install any missing requirements.
 
-To get the spec suite running, you will need to install the not-a-mock gem if you don't already have it:
+To get the spec suite running, you will need to install the ginger gem:
 
-  git clone git://github.com/freelancing-god/not-a-mock.git
-  cd not-a-mock
-  rake gem
-  gem install pkg/not_a_mock-1.1.0.gem
-  
-Then install the ginger gem. The steps are the same, except that you might need to sudo the gem install:
-
-  git clone git://github.com/freelancing-god/ginger.git
-  cd ginger
-  rake gem
-  sudo gem install pkg/ginger-1.1.0.gem
-  
-Alternatively, install the ginger gem directly from the freelancing-god github repository
-
-  sudo gem sources -a http://gems.github.com
-  sudo gem install freelancing-god-ginger
+  sudo gem install ginger --source http://gemcutter.org
   
 Then install the cucumber, yard, jeweler and rspec gems. Make sure you have a git install version 1.6.0.0 or higher, otherwise the jeweler gem won't install.
 
@@ -155,3 +140,5 @@ Since I first released this library, there's been quite a few people who have su
 * Ward Bekker
 * Brian Terlson
 * Christian Aust
+* Martin Sarasale
+* Édouard Brière

data/VERSION.yml

@@ -1,4 +1,4 @@
 --- 
-:patch: 11
 :major: 1
 :minor: 2
+:patch: 12

data/features/a.rb

@@ -0,0 +1,17 @@
+# This file exists because Cucumber likes to auto-load all ruby files
+puts <<-MESSAGE
+Cucumber 0.1.12 defaults to loading all ruby files within the features folder
+alphabetically. This is annoying, because some files need to be loaded before
+others (and others perhaps not at all, given missing dependencies). Hence this
+place-holder imaginatively named 'a.rb', to force this message.
+
+A work-around is to use cucumber profiles. You will find the default profile in
+cucumber.yml should serve your needs fine, unless you add new step definitions.
+When you do that, you can regenerate the YAML file by running:
+rake cucumber_defaults
+
+And then run specific features as follows is slightly more verbose, but it
+works, whereas this doesn't.
+cucumber -p default features/something.feature
+MESSAGE
+exit 0

data/features/alternate_primary_key.feature

@@ -0,0 +1,27 @@
+Feature: Searching on a single model
+  In order to use search models with non-integer primary keys
+  A developer
+  Should be able to search on a single model
+  
+  Scenario: Searching using a basic query
+    Given Sphinx is running
+    And I am searching on robots
+    When I search for Sizzle
+    Then I should get 2 results
+  
+  Scenario: Searching using another basic query
+    Given Sphinx is running
+    And I am searching on robots
+    When I search for fritz
+    Then I should get 1 result
+  
+  Scenario: Deleting an instance
+    Given Sphinx is running
+    And I am searching on robots
+    When I search for Expendable
+    Then I should get 1 result
+    
+    When I destroy robot Expendable
+    And I wait for Sphinx to catch up
+    And I search for three
+    Then I should get 0 results

data/features/attribute_transformation.feature

@@ -0,0 +1,22 @@
+Feature: Handle not-quite-supported column types as attributes
+  In order for Thinking Sphinx to be more understanding with model structures
+  The plugin
+  Should be able to use translatable columns as attributes
+  
+  Scenario: Decimals as floats
+    Given Sphinx is running
+    And I am searching on alphas
+    When I filter between 1.0 and 3.0 on cost
+    Then I should get 2 results
+  
+  Scenario: Dates as Datetimes
+    Given Sphinx is running
+    And I am searching on alphas
+    When I filter between 1 and 3 days ago on created_on
+    Then I should get 2 results
+  
+  Scenario: Timestamps as Datetimes
+    Given Sphinx is running
+    And I am searching on alphas
+    When I filter between 1 and 3 days ago on created_at
+    Then I should get 2 results

data/features/attribute_updates.feature

@@ -0,0 +1,33 @@
+Feature: Update attributes directly to Sphinx
+  In order for updates to be more seamless
+  The plugin
+  Should update Sphinx's attributes where possible
+  
+  Scenario: Updating attributes in Sphinx without delta indexes
+    Given Sphinx is running
+    And I am searching on alphas
+    When I filter by 3 on value
+    Then I should get 1 result
+    
+    When I change the value of alpha two to 13
+    And I wait for Sphinx to catch up    
+    And I filter by 13 on value
+    Then I should get 1 result
+    
+    When I change the value of alpha two to 3
+    And I wait for Sphinx to catch up    
+    And I filter by 13 on value
+    Then I should get 0 results
+
+  Scenario: Updating attributes in Sphinx with delta indexes
+    Given Sphinx is running
+    And I am searching on betas
+    When I filter by 8 on value
+    Then I should get 1 result
+    
+    When I change the value of beta eight to 18
+    And I filter by 18 on value
+    Then I should get 1 result
+    
+    When I search for the document id of beta eight in the beta_delta index
+    Then it should not exist

data/features/datetime_deltas.feature

@@ -0,0 +1,66 @@
+Feature: Datetime Delta Indexing
+  In order to have delta indexing on frequently-updated sites
+  Developers
+  Should be able to use an existing datetime column to track changes
+  
+  Scenario: Delta Index should not fire automatically
+    Given Sphinx is running
+    And I am searching on thetas
+    When I search for one
+    Then I should get 1 result
+  
+    When I change the name of theta one to eleven
+    And I wait for Sphinx to catch up
+    And I search for one
+    Then I should get 1 result
+    
+    When I search for eleven
+    Then I should get 0 results
+  
+  Scenario: Delta Index should fire when jobs are run
+    Given Sphinx is running
+    And I am searching on thetas
+    When I search for two
+    Then I should get 1 result
+  
+    When I change the name of theta two to twelve
+    And I wait for Sphinx to catch up
+    And I search for twelve
+    Then I should get 0 results
+    
+    When I index the theta datetime delta
+    And I wait for Sphinx to catch up
+    And I search for twelve
+    Then I should get 1 result
+    
+    When I search for two
+    Then I should get 0 results
+  
+  Scenario: New records should be merged into the core index
+    Given Sphinx is running
+    And I am searching on thetas
+    When I search for thirteen
+    Then I should get 0 results
+    
+    When I create a new theta named thirteen
+    And I search for thirteen
+    Then I should get 0 results
+    
+    When I index the theta datetime delta
+    And I wait for Sphinx to catch up
+    And I search for thirteen
+    Then I should get 1 result
+    
+    When I search for the document id of theta thirteen in the theta_core index
+    Then it should exist
+  
+  Scenario: Deleting records
+    Given Sphinx is running
+    And I am searching on thetas
+    When I search for three
+    Then I should get 1 result
+    
+    When I delete the theta named three
+    And I wait for Sphinx to catch up
+    And I search for three
+    Then I should get 0 results

data/features/delayed_delta_indexing.feature

@@ -0,0 +1,37 @@
+Feature: Delayed Delta Indexing
+  In order to have delta indexing on frequently-updated sites
+  Developers
+  Should be able to use delayed_job to handle delta indexes to lower system load
+  
+  Scenario: Delta Index should not fire automatically
+    Given Sphinx is running
+    And I am searching on delayed betas
+    When I search for one
+    Then I should get 1 result
+  
+    When I change the name of delayed beta one to eleven
+    And I wait for Sphinx to catch up
+    And I search for one
+    Then I should get 1 result
+    
+    When I search for eleven
+    Then I should get 0 results
+  
+  Scenario: Delta Index should fire when jobs are run
+    Given Sphinx is running
+    And I am searching on delayed betas
+    When I search for one
+    Then I should get 1 result
+  
+    When I change the name of delayed beta two to twelve
+    And I wait for Sphinx to catch up
+    And I search for twelve
+    Then I should get 0 results
+    
+    When I run the delayed jobs
+    And I wait for Sphinx to catch up
+    And I search for twelve
+    Then I should get 1 result
+    
+    When I search for two
+    Then I should get 0 results

data/features/deleting_instances.feature

@@ -0,0 +1,64 @@
+Feature: Keeping Sphinx in line with deleted model instances
+  In order to avoid deleted items being returned by Sphinx
+  Thinking Sphinx
+  Should keep deleted items out of search results
+  
+  Scenario: Deleting instances from the core index
+    Given Sphinx is running
+    And I am searching on betas
+    When I search for three
+    Then I should get 1 result
+    
+    When I destroy beta three
+    And I wait for Sphinx to catch up
+    And I search for three
+    Then I should get 0 results
+  
+  Scenario: Deleting subclasses when the parent class is indexed
+    Given Sphinx is running
+    And I am searching on cats
+    When I search for moggy
+    Then I should get 1 result
+    
+    When I destroy cat moggy
+    And I wait for Sphinx to catch up
+    And I search for moggy
+    Then I should get 0 results
+  
+  Scenario: Deleting created instances from the delta index
+    Given Sphinx is running
+    And I am searching on betas
+    When I create a new beta named eleven
+    And I wait for Sphinx to catch up
+    And I search for eleven
+    Then I should get 1 result
+    
+    When I destroy beta eleven
+    And I wait for Sphinx to catch up
+    And I search for eleven
+    Then I should get 0 results
+  
+  Scenario: Deleting edited instances from the delta index
+    Given Sphinx is running
+    And I am searching on betas
+    When I change the name of beta four to fourteen
+    And I wait for Sphinx to catch up
+    And I search for fourteen
+    Then I should get 1 result
+    
+    When I destroy beta fourteen
+    And I wait for Sphinx to catch up
+    And I search for fourteen
+    Then I should get 0 results
+
+  Scenario: Deleting created instances from the delta index when deltas are disabled
+    Given Sphinx is running
+    And I am searching on betas
+    When I create a new beta named thirteen
+    And I wait for Sphinx to catch up
+    And I disable delta updates
+    And I destroy beta thirteen
+    And I wait for Sphinx to catch up
+    And I enable delta updates
+    And I search for thirteen
+    Then I should get 0 results

data/features/direct_attributes.feature

@@ -0,0 +1,11 @@
+Feature: Direct Attributes
+  In order to avoid unnecessary SQL queries
+  I want to access attribute values from Sphinx's response
+  
+  Scenario: Accessing attribute values directly
+    Given Sphinx is running
+    And I am searching on posts
+    When I search
+    Then the first result should have a comments count of 9
+
+  

data/features/excerpts.feature

@@ -0,0 +1,13 @@
+Feature: Generate excerpts for search results
+  
+  Scenario: Basic Excerpts Syntax
+    Given Sphinx is running
+    And I am searching on comments
+    And I search for "lorem punto"
+    Then the content excerpt of the first result is "de un sitio mientras que mira su diseño. El <span class="match">punto</span> de usar <span class="match">Lorem</span> Ipsum es que tiene una distribución"
+  
+  Scenario: Integrated Excerpts Syntax
+    Given Sphinx is running
+    And I am searching on comments
+    And I search for "lorem"
+    Then calling content on the first result excerpts object should return "de un sitio mientras que mira su diseño. El punto de usar <span class="match">Lorem</span> Ipsum es que tiene una distribución"

data/features/extensible_delta_indexing.feature

@@ -0,0 +1,9 @@
+Feature: Delayed Delta Indexing
+  In order to have delta indexing on frequently-updated sites
+  Developers
+  Should be able to create their own handlers for delta indexing
+  
+  Scenario: I specify a valid handler for delta indexing
+    Given Sphinx is running
+    When I change the name of extensible beta one to eleven
+    Then the generic delta handler should handle the delta indexing

data/features/facets.feature

@@ -0,0 +1,76 @@
+Feature: Search and browse models by their defined facets
+  
+  Scenario: Requesting facets
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    Then I should have valid facet results
+    And I should have 6 facets
+    And I should have the facet State
+    And I should have the facet Country
+    And I should have the facet Age
+    And I should have the facet City
+    And I should have the facet Tag Ids
+    And I should have the facet Tags
+  
+  Scenario: Requesting specific facets
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    And I am requesting just the facet State
+    Then I should have valid facet results
+    And I should have 1 facet
+    And I should have the facet State
+    When I am requesting just the facets State and Age
+    Then I should have valid facet results
+    And I should have 2 facet
+    And I should have the facet State
+    And I should have the facet Age
+  
+  Scenario: Requseting float facets
+    Given Sphinx is running
+    And I am searching on alphas
+    When I am requesting facet results
+    Then I should have 1 facet
+    And the Cost facet should have a 5.55 key
+  
+  Scenario: Requesting facet results
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    And I drill down where Country is Australia
+    Then I should get 11 results
+  
+  Scenario: Requesting facet results by multiple facets
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    And I drill down where Country is Australia and Age is 30
+    Then I should get 4 results
+    
+  Scenario: Requesting facets with classes included
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    And I want classes included
+    Then I should have valid facet results
+    And I should have 7 facets
+    And I should have the facet Class
+  
+  Scenario: Requesting MVA facets
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    And I drill down where tag_ids includes the id of tag Australia
+    Then I should get 11 results
+    When I am requesting facet results
+    And I drill down where tag_ids includes the id of tags Melbourne or Sydney
+    Then I should get 5 results
+  
+  Scenario: Requesting MVA string facets
+    Given Sphinx is running
+    And I am searching on developers
+    When I am requesting facet results
+    Then the Tags facet should have an "Australia" key
+    Then the Tags facet should have an "Melbourne" key
+    Then the Tags facet should have an "Victoria" key

data/features/facets_across_model.feature

@@ -0,0 +1,29 @@
+Feature: Search and browse across models by their defined facets
+
+  Scenario: Requesting facets across multiple models
+    Given Sphinx is running
+    When I am requesting facet results
+    And I want all possible attributes
+    Then I should have valid facet results
+    And I should have 10 facets
+    And I should have the facet Class
+    And the Class facet should have a "Person" key
+    And I should have the facet Gender
+    And the Gender facet should have a "female" key
+    And I should have the facet Country
+    And I should have the facet Category Name
+    And the Category Name facet should have a "hello" key with 10 hits
+  
+  Scenario: Requesting facets across models without class results
+    Given Sphinx is running
+    When I am requesting facet results
+    And I want all possible attributes
+    And I don't want classes included
+    Then I should have 9 facets
+    And I should not have the facet Class
+  
+  Scenario: Requesting facets common to all indexed models
+    Given Sphinx is running
+    When I am requesting facet results
+    Then I should have the facet Class
+    And I should have 1 facet