📇
Catalogue API
  • Catalogue API
  • developers
  • How users request items
  • Search
    • Current queries
      • images
      • Query structure
    • Search
      • Changelog
      • Collecting data
      • Query design
      • Query design
      • wellcomecollection.org query development index
      • Reporting and metrics
      • Work IDs crib sheet
      • Analysis
        • Less than 3-word searches
        • Subsequent searches
        • Searches with 3 words or more
      • Hypotheses
        • Behaviours
        • Concepts, subject, and another field
        • Concepts, subjects with other field
        • Concepts, subjects
        • Contributor with other field
        • Contributors
        • Further research and design considerations
        • Genre with other field
        • Genres
        • Mood
        • Phrases
        • Reference number with other field
        • Reference numbers
        • Search scenarios
        • Synonymous names and subjects
        • Title with other field
        • Titles
      • Relevance tests
        • Test 1 - Explicit feedback
        • Test 2 - Implicit feedback
        • Test 3 - Adding notes
        • Test 4 - AND or OR
        • Test 5 - Scoring Tiers
        • Test 6 - English tokeniser and Contributors
        • Test 7 - BoolBoosted vs ConstScore
        • Test 8 - BoolBoosted vs PhaserBeam
    • Rank
      • Rank cluster
      • Developing with rank
      • Testing
Powered by GitBook
On this page
  • CLI
  • CI
  • Performance
  1. Search
  2. Rank

Testing

CLI

To run tests from the CLI, run yarn test --queryEnv=[production|staging|candidate].

N.B. this command is typically invoked to test the functionality of an app. Here, the test command does not test the rank app functionality; It runs the actual rank tests for queries/mappings/indices etc.

CI

Tests are automatically run against the pipeline cluster in CI when we deploy a new pipeline to stage.

Performance

Rank allows us to test the performance (precision, recall, etc) of new candidate queries and mappings, but real-world performance is based on more than just delivering trustworthy results. We also test the speed at which a query runs to make sure that each iteration is faster than the last.

We use real-world search terms from our own analytics systems to assess the performance of our queries. To fetch a set of search terms for testing, run:

yarn getSearchTerms

To compare the speed of candidate/production queries using those search terms, run:

yarn compareQuerySpeed
PreviousDeveloping with rank

Last updated 10 months ago