agentleFS
Sign inStart free
marqo-aimarqo-ai/marqo/.cursor/rules/run-tests.mdc

marqo / rules

Cursor rule5k starsChanged 16 months agoApache-2.0View on GitHub

- Unit tests are in ./tests/unit_tests, integ tests are in ./tests/integ_tests, API tests are in ./tests/api_tests/v1/tests/api_tests - If you add new tests, make sure to run them and verify they pass. - To run unit and integ tests, make sure working directory is repo root and set PYTHONPATH=./src. - If running integ or API tests, make sure Vespa is running via docker ps. If not running, use python scripts/vespa_local/vespa_local.py full_start to run Vespa first. - To run API tests, first…

Trending

Quiet since June.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the marqo-ai/marqo repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about marqo-ai/marqo

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub, Hacker News and Bluesky (57 times).

On GitHub · 45

40 more on GitHub
  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

We split this run-tests.mdc into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you add new tests, make sure to run them and verify they pass.

    line 7
  2. Very specific:

    If running integ or API tests, make sure Vespa is running via docker ps.

    line 9
  3. Distinctive:

    Add to existing test files where appropriate.

    line 13
  4. Distinctive:

    Put all imports at the top of the file when possible.

    line 14
  5. Distinctive:

    Don't write the actual line in the implementation you're testing in the test code comments, because this line could change.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
run-tests.mdc
---
description: 
globs: 
alwaysApply: true
---
- Unit tests are in ./tests/unit_tests, integ tests are in ./tests/integ_tests, API tests are in ./tests/api_tests/v1/tests/api_tests
- If you add new tests, make sure to run them and verify they pass.
- To run unit and integ tests, make sure working directory is repo root and set PYTHONPATH=./src.
- If running integ or API tests, make sure Vespa is running via docker ps. If not running, use
python scripts/vespa_local/vespa_local.py full_start to run Vespa first.
- To run API tests, first run Marqo API in one process by running src/marqo/tensor_search/api.py using PYTHONPATH=./src MARQO_ENABLE_BATCH_APIS=true MARQO_MODE=COMBINED. While the API is running, run API tests via pytest using PYTHONPATH=./tests/api_tests/v1/tests/api_tests . If Marqo API fails to run, stop. Terminate Marqo API when done.
- Unit tests must follow the same package hierarchy as the code they test.
- Add to existing test files where appropriate. Create new test files only when necessary, Follow the format of existing tests.
- Put all imports at the top of the file when possible.
- Don't write the actual line in the implementation you're testing in the test code comments, because this line could change.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free