thinking-sphinx 2.1.0 → 3.0.0.pre

data/features/abstract_inheritance.feature

@@ -1,10 +0,0 @@
-Feature: Abstract inheritance
-  In order to use Thinking Sphinx in complex situations
-  As a developer
-  I want to define indexes on subclasses of abstract models
-
-  Scenario: Searching on subclasses of abstract models
-    Given Sphinx is running
-    And I am searching on music
-    When I search
-    Then I should get 3 results

data/features/alternate_primary_key.feature

@@ -1,27 +0,0 @@
-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 Expendable
-    Then I should get 0 results

data/features/attribute_transformation.feature

@@ -1,22 +0,0 @@
-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 2 and 4 days ago on created_on by date
-    Then I should get 3 results
-
-  Scenario: Timestamps as Datetimes
-    Given Sphinx is running
-    And I am searching on alphas
-    When I filter between 2 and 4 days ago on created_at
-    Then I should get 2 results

data/features/attribute_updates.feature

@@ -1,79 +0,0 @@
-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 four to 13
-    And I wait for Sphinx to catch up
-    And I filter by 13 on value
-    And I use index alpha_core
-    Then I should get 1 result
-    When I use index alternative_core
-    Then I should get 1 result
-
-    When I change the value of alpha four to 4
-    And I wait for Sphinx to catch up
-    And I filter by 13 on value
-    And I use index alpha_core
-    Then I should get 0 results
-    When I use index alternative_core
-    Then I should get 0 result
-
-  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 wait for Sphinx to catch up
-    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 secondary_beta_delta index
-    Then it should not exist
-
-  Scenario: Updating attributes in a delta index
-    Given Sphinx is running
-    And I am searching on betas
-
-    When I change the name of beta nine to nineteen
-    And I change the value of beta nineteen to 19
-    And I wait for Sphinx to catch up
-
-    When I filter by 19 on value
-    And I use index secondary_beta_delta
-    And I clear the connection pool
-    Then I should get 1 result
-
-  Scenario: Updating attributes in a delta index with deltas disabled
-    Given Sphinx is running
-    And I am searching on betas
-
-    When I change the name of beta eleven to twentyone
-    And I disable delta updates
-    And I change the value of beta twentyone to 21
-    And I wait for Sphinx to catch up
-    And I clear the connection pool
-
-    When I filter by 21 on value
-    And I use index secondary_beta_delta
-    Then I should get 1 result
-    And I enable delta updates
-
-  Scenario: Updating boolean attribute in Sphinx
-    Given Sphinx is running
-    And I am searching on alphas
-    When I filter by active alphas
-    Then I should get 10 results
-
-    When I flag alpha five as inactive
-    And I wait for Sphinx to catch up
-    And I filter by active alphas
-    Then I should get 9 results

data/features/deleting_instances.feature

@@ -1,70 +0,0 @@
-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 eighteen
-    And I wait for Sphinx to catch up
-    And I clear the connection pool
-    And I search for eighteen
-    Then I should get 1 result
-
-    When I destroy beta eighteen
-    And I wait for Sphinx to catch up
-    And I search for eighteen
-    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 clear the connection pool
-    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 clear the connection pool
-    And I search for thirteen
-    Then I should get 1 result
-
-    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

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

@@ -1,21 +0,0 @@
-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"
-
-  Scenario: Excerpt Options
-    Given Sphinx is running
-    And I am searching on comments
-    And I search for "lorem"
-    And I provide excerpt option "before_match" with value "<em>"
-    And I provide excerpt option "after_match" with value "</em>"
-    Then calling content on the first result excerpts object should return "de un sitio mientras que mira su diseño. El punto de usar <em>Lorem</em> Ipsum es que tiene una distribución"

data/features/extensible_delta_indexing.feature

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

@@ -1,88 +0,0 @@
-Feature: Search and browse models by their defined facets
-  
-  Background:
-    Given Sphinx is running
-  
-  Scenario: Requesting facets
-    Given 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 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: Requesting float facets
-    Given 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 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 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 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 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 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
-
-  Scenario: Requesting MVA facets from source queries
-    Given I am searching on posts
-    When I am requesting facet results
-    Then the Comment Ids facet should have 9 keys
-  
-  Scenario: Requesting facets from a subclass
-    Given I am searching on animals
-    When I am requesting facet results
-    And I want classes included
-    Then I should have the facet Class
-  
-  Scenario: Requesting facets with explicit value sources
-    Given I am searching on developers
-    When I am requesting facet results
-    Then the City facet should have a "Melbourne" key
-  

data/features/facets_across_model.feature

@@ -1,29 +0,0 @@
-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 12 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 11 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

data/features/field_sorting.feature

@@ -1,18 +0,0 @@
-Feature: Field Sorting
-  In order to sort by strings
-  As a developer
-  I want to enable sorting by existing fields
-  
-  Background:
-    Given Sphinx is running
-    And I am searching on people
-    
-  Scenario: Searching with ordering on a sortable field
-    When I order by first_name
-    Then I should get 20 results
-    And the first_name of each result should indicate order
-  
-  Scenario: Sort on a case insensitive sortable field
-    When I order by last_name
-    Then the first result's "last_name" should be "abbott"
-  

data/features/handling_edits.feature

@@ -1,97 +0,0 @@
-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 returning 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 clear the connection pool
-    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 eleventeen
-    And I wait for Sphinx to catch up
-    And I clear the connection pool
-    And I search for one
-    Then I should get 0 results
-
-    When I search for eleventeen
-    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 clear the connection pool
-    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 secondary_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 secondary_beta_delta index
-    Then it should not exist if using Rails 2.1 or newer
-
-  Scenario: Handling edits with a delta when Sphinx isn't running
-    Given Sphinx is running
-    And I am searching on betas
-    When I stop Sphinx
-    And I change the name of beta six to sixteen
-    And I start Sphinx
-    And I search for sixteen
-    Then I should get 1 result
-
-  Scenario: Handling edits when updates are disabled
-    Given Sphinx is running
-    And updates are disabled
-    And I am searching on betas
-
-    When I search for seven
-    Then I should get 1 result
-
-    When I change the name of beta seven to seventeen
-    And I wait for Sphinx to catch up
-    And I search for seven
-    Then I should get 1 result
-
-    When I search for seventeen
-    Then I should get 0 results