gonavi-go
01Cursor rule Cursor
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
439 tagged Unit testing, measured the same way as everything else here.
Browse within: hacktoberfest 621c-enterprise 61hacktoberfest2022 60yaxunit 60cursor 53cursorrules 34nodejs 19cli 18prisma 14cursor-ai 13nextjs 13ai-coding 12javascript 12cursor-rules 11
Cursor rule Cursor
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
Cursor rule Cursor
We use expecttest for testing. If you need to match against a multiline string or some output that is likely to change in the future (e.g., the kind of thing you would have ordinarily done an assertIn with), use an expect test. If a test is assertExpectedInline and it fails, use 'accept' command to update the output…
Cursor rule Cursor
Rules for writing Jest tests in TypeScript.
Cursor rule Cursor
Run gofmt, go vet, and unit tests before committing Go files.
Cursor rule Cursor
Architectural planning guidelines for Level 4 Complex System tasks.
Cursor rule Cursor
Never try to run a test-script from commandline using node -e. This will always fail, you'll need to write a typescript test file, build that and execute that.
Cursor rule Cursor
Add Vitest tests when changing behavior in this monorepo.
Cursor rule Cursor
Cursor rule "testing" from udecode/plate-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.
Cursor rule Cursor
A Cursor rule file containing project development guidance, including TDD, BDD, unit testing, and general practices. TDD means writing tests before code; BDD describes expected behavior in user-focused terms.
Cursor rule Cursor
Core project conventions for the Uniqlo Sales Alerter.
Cursor rule Cursor
A set of Cursor coding rules for testing generated code from a Rust Model Context Protocol server attribute system. Code generation means producing source code automatically from declarations or annotations.
Cursor rule Cursor
A set of testing rules covering test practices and strategy. It discusses unit tests for small pieces of code, integration tests for connected components, and end-to-end tests for complete workflows.
Cursor rule Cursor
This project uses Vitest for testing with React Testing Library for component testing. The testing stack includes.
linuxfoundation/lfx-self-serve
Cursor rule Cursor
Enforce Prettier format, ESLint lint, and unit tests before every commit in lfx-self-serve.
Cursor rule Cursor
When writing tests, always follow these best practices.
Cursor rule Cursor
React/TypeScript UI kit conventions — components, stories, tests, exports.
holasoymalva/AI-Unit-Test-Builder
Cursor rule Cursor
Review and refactor generated unit tests for improved quality and coverage.
Cursor rule Cursor
A set of project rules for writing unit and integration tests. Unit tests check one function or module, while integration tests check several parts working together, often with a test database.
Cursor rule Cursor needs its repo
Comprehensive Effect-TS service architecture patterns covering stores, usecases, handlers, and testing for building scalable applications.
Cursor rule Cursor
Cursor rule "rspec-let-do-blocks" from panozzaj/cursor-rules, covering multi-line array, multi-line method call with keyword args, multi-line hash definition, complex single line expression and using { ... } for multi-line blocks.
Cursor rule Cursor
Always follow these rules when creating or modifying Tecton unit tests.
Cursor rule Cursor
Testing conventions and patterns.
VirtusLab-Open-Source/strapi-plugin-mcp
Cursor rule Cursor
Testing conventions and techniques for Strapi MCP plugin.
Cursor rule Cursor
Cursor rule "testing" from SecondLifes/code-intel, covering testing — rules, the two-tier split (non-negotiable), naming — the name states the locked-in behavior, good — the real convention (tests/testchunker.py) and weak — names the function, not the behavior.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: