sherpa99-thinking-sphinx 1.1.4

data/cucumber.yml

@@ -0,0 +1 @@
+default: "--require features/support/env.rb --require features/support/db/mysql.rb --require features/support/db/active_record.rb --require features/support/post_database.rb --require features/step_definitions/alpha_steps.rb --require features/step_definitions/beta_steps.rb --require features/step_definitions/cat_steps.rb --require features/step_definitions/common_steps.rb --require features/step_definitions/datetime_delta_steps.rb --require features/step_definitions/delayed_delta_indexing_steps.rb --require features/step_definitions/facet_steps.rb --require features/step_definitions/find_arguments_steps.rb --require features/step_definitions/gamma_steps.rb --require features/step_definitions/search_steps.rb --require features/step_definitions/sphinx_steps.rb"

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/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/datetime_deltas.feature

@@ -0,0 +1,55 @@
+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

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,52 @@
+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

data/features/facets.feature

@@ -0,0 +1,26 @@
+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 4 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
+  
+  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

data/features/handling_edits.feature

@@ -0,0 +1,67 @@
+Feature: Keeping Sphinx in line with model changes when requested
+  In order to keep indexes as up to date as possible
+  Thinking Sphinx
+  Should return the expected results depending on whether delta indexes are used
+  
+  Scenario: Returning instance from old data if there is no delta
+    Given Sphinx is running
+    And I am searching on alphas
+    When I search for two
+    Then I should get 1 result
+    
+    When I change the name of alpha two to twelve
+    And I wait for Sphinx to catch up
+    And I search for two
+    Then I should get 1 result
+  
+  Scenario: Not returing an instance from old data if there is a delta
+    Given Sphinx is running
+    And I am searching on betas
+    When I search for two
+    Then I should get 1 result
+  
+    When I change the name of beta two to twelve
+    And I wait for Sphinx to catch up
+    And I search for two
+    Then I should get 0 results
+  
+  Scenario: Returning instance from new data if there is a delta
+    Given Sphinx is running
+    And I am searching on betas
+    When I search for one
+    Then I should get 1 result
+  
+    When I change the name of beta one to eleven
+    And I wait for Sphinx to catch up
+    And I search for one
+    Then I should get 0 results
+    
+    When I search for eleven
+    Then I should get 1 result
+  
+  Scenario: Returning new records if there's a delta
+    Given Sphinx is running
+    And I am searching on betas
+    When I search for fifteen
+    Then I should get 0 results
+    
+    When I create a new beta named fifteen
+    And I wait for Sphinx to catch up
+    And I search for fifteen
+    Then I should get 1 result
+  
+  Scenario: Avoiding delta updates if there hasn't been changes
+    Given Sphinx is running
+    And I am searching on betas
+    When I search for five
+    Then I should get 1 result
+    
+    When I change the name of beta five to five
+    And I wait for Sphinx to catch up
+    And I search for five
+    Then I should get 1 result
+    
+    When I search for the document id of beta five in the beta_core index
+    Then it should exist if using Rails 2.1 or newer
+    When I search for the document id of beta five in the beta_delta index
+    Then it should not exist if using Rails 2.1 or newer

data/features/retry_stale_indexes.feature

@@ -0,0 +1,24 @@
+Feature: Manually updating Sphinx indexes to handle uncaught deletions
+  In order to keep indexes as up to date as possible
+  Thinking Sphinx
+  Should automatically update the indexes and retry the search if it gets a nil result
+  
+  Scenario: Changing retry_stale settings
+    Given Sphinx is running
+    And I am searching on gammas
+    Then I should not get 0 results
+    
+    When I set retry stale to false
+    And I set per page to 1
+    And I order by "sphinx_internal_id ASC"
+    And I destroy gamma one without callbacks
+    Then I should get a single result of nil
+    
+    When I set retry stale to 1
+    Then I should get a single gamma result with a name of two
+    
+    When I destroy gamma two without callbacks
+    Then I should get a single result of nil
+    
+    When I set retry stale to true
+    Then I should get a single gamma result with a name of three

data/features/searching_across_models.feature

@@ -0,0 +1,20 @@
+Feature: Searching across multiple model
+  In order to use Thinking Sphinx's core functionality
+  A developer
+  Should be able to search on multiple models
+  
+  Scenario: Retrieving total result count
+    Given Sphinx is running
+    When I search for James
+    And I am retrieving the result count
+    Then I should get a value of 3
+  
+  Scenario: Confirming existance of a document id in a given index
+    Given Sphinx is running
+    When I search for the document id of alpha one in the alpha_core index
+    Then it should exist
+  
+  Scenario: Retrieving results from multiple models
+    Given Sphinx is running
+    When I search for ten
+    Then I should get 5 results

data/features/searching_by_model.feature

@@ -0,0 +1,118 @@
+Feature: Searching on a single model
+  In order to use Thinking Sphinx's core functionality
+  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 people
+    When I search for James
+    Then I should get 3 results
+  
+  Scenario: Searching on a specific field
+    Given Sphinx is running
+    And I am searching on people
+    When I search for James on first_name
+    Then I should get 2 results
+  
+  Scenario: Searching on multiple fields
+    Given Sphinx is running
+    And I am searching on people
+    When I search for James on first_name
+    And I search for Chamberlain on last_name
+    Then I should get 1 result
+  
+  Scenario: Searching with a filter
+    Given Sphinx is running
+    And I am searching on alphas
+    When I filter by 1 on value
+    Then I should get 1 result
+  
+  Scenario: Searching with multiple filters
+    Given Sphinx is running
+    And I am searching on boxes
+    When I filter by 2 on width
+    And I filter by 2 on length
+    Then I should get 1 result
+    
+  Scenario: Searching to filter multiple values on an MVA
+    Given Sphinx is running
+    And I am searching on boxes
+    When I filter by 11 and 12 on dimensions
+    Then I should get 2 results
+    When I clear existing filters
+    And I filter by both 11 and 12 on dimensions
+    Then I should get 1 result
+  
+  Scenario: Searching with ordering by attribute
+    Given Sphinx is running
+    And I am searching on alphas
+    When I order by value
+    Then I should get 10 results
+    And the value of each result should indicate order
+  
+  Scenario: Searching with ordering on a sortable field
+    Given Sphinx is running
+    And I am searching on people
+    And I order by first_name
+    Then I should get 20 results
+    And the first_name of each result should indicate order
+  
+  Scenario: Intepreting Sphinx Internal Identifiers
+    Given Sphinx is running
+    And I am searching on people
+    Then I should get 20 results
+    And each result id should match the corresponding sphinx internal id
+  
+  Scenario: Retrieving weightings
+    Given Sphinx is running
+    And I am searching on people
+    When I search for "Ellie Ford"
+    And I set match mode to any
+    Then I can iterate by result and weighting
+  
+  Scenario: Retrieving group counts
+    Given Sphinx is running
+    And I am searching on people
+    When I group results by the birthday attribute
+    Then I can iterate by result and count
+  
+  Scenario: Retrieving group values
+    Given Sphinx is running
+    And I am searching on people
+    When I group results by the birthday attribute
+    Then I can iterate by result and group
+  
+  Scenario: Retrieving both group values and counts
+    Given Sphinx is running
+    And I am searching on people
+    When I group results by the birthday attribute
+    Then I can iterate by result and group and count
+  
+  Scenario: Searching for ids
+    Given Sphinx is running
+    And I am searching on people
+    When I search for Ellie
+    And I am searching for ids
+    Then I should have an array of integers
+  
+  Scenario: Search results should match Sphinx's order
+    Given Sphinx is running
+    And I am searching on people
+    When I search for Ellie
+    And I order by "sphinx_internal_id DESC"
+    Then searching for ids should match the record ids of the normal search results
+  
+  Scenario: Retrieving total result count when total is less than a page
+    Given Sphinx is running
+    And I am searching on people
+    When I search for James
+    And I am retrieving the result count
+    Then I should get a value of 3
+
+  Scenario: Retrieving total result count for more than a page
+    Given Sphinx is running
+    And I am searching on people
+    When I am retrieving the result count
+    Then I should get a value of 1000
+