test-patterns

test-patterns is a cursor rule for Cursor from tugkanboz/awesome-cursorrules. It costs 2,177 tokens per session, scanned A, original, MIT.

A collection of patterns for testing Selenium-based Python applications with pytest, a Python testing tool. It covers arranging tests, running them with different data, grouping them, handling failures, and checking performance.

In plain words
What is it for?
Use it when writing Selenium tests with pytest, especially tests that cover multiple user types, reusable fixtures, expected failures, and performance checks.
Why use it?
It provides a consistent structure for browser tests, making authentication and other user-flow checks easier to organize and repeat.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when writing Selenium tests with pytest, especially tests that cover multiple user types, reusable fixtures, expected failures, and performance checks.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/tugkanboz/awesome-cursorrules/test-patterns
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/tugkanboz/awesome-cursorrules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for test-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/tugkanboz/awesome-cursorrules/test-patterns/github.svg)](https://agentmods.dev/rules/tugkanboz/awesome-cursorrules/test-patterns)
Your own site
<a href="https://agentmods.dev/rules/tugkanboz/awesome-cursorrules/test-patterns"><img src="https://agentmods.dev/badge/rules/tugkanboz/awesome-cursorrules/test-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/tugkanboz/awesome-cursorrules/test-patterns"><img src="https://agentmods.dev/badge/rules/tugkanboz/awesome-cursorrules/test-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,177 This file is loaded in full into every session.
When invoked 2,177 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.02177 $0.02177
Opus 5.5 $0.00871 $0.00871
Sonnet 5.5 $0.00435 $0.00435
Haiku 4.5 $0.00218 $0.00218

Measured 1mo ago against content hash 6eaeb61f3086, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

example-structures/selenium-python/.cursor/rules/test-patterns.mdc · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Selenium Python Test Patterns

Advanced Test Structure

  • Arrange-Act-Assert Pattern: Clear test structure with setup, action, and verification
  • Data-Driven Testing: Parametrized tests with comprehensive data coverage
  • Test Categorization: Smart use of pytest markers for test organization
  • Robust Error Handling: Graceful failure management and recovery

Data-Driven Test Excellence

import pytest
from pages.login_page import LoginPage
from pages.dashboard_page import DashboardPage

class TestUserAuthentication:
    """Comprehensive user authentication test suite."""
    
    @pytest.mark.smoke
    @pytest.mark.parametrize("user_type,expected_dashboard", [
        ("admin", "admin-dashboard"),
        ("manager", "manager-dashboard"),
        ("employee", "employee-dashboard"),
        ("guest", "guest-dashboard")
    ])
    def test_role_based_dashboard_access(self, driver, test_data, user_type, expected_dashboard):
        """Test that users see appropriate dashboard based on their role."""
        # Arrange
        user_credentials = test_data.get_user_credentials(user_type)
        login_page = LoginPage(driver)
        
        # Act
        dashboard_page = login_page.navigate() \
                                 .login(user_credentials['email'], user_credentials['password'])
        
        # Assert
        assert dashboard_page.is_loaded(), f"Dashboard not loaded for {user_type}"
        assert dashboard_page.get_dashboard_type() == expected_dashboard, \
               f"Wrong dashboard type for {user_type}"
        assert dashboard_page.get_user_role() == user_type.upper(), \
               f"User role not displayed correctly"
    
    @pytest.mark.regression
    @pytest.mark.parametrize("invalid_credential", [
        {"email": "[email protected]", "password": "validPassword123", "error": "Invalid email"},
        {"email": "[email protected]", "password": "wrongPassword", "error": "Invalid password"},
        {"email": "", "password": "validPassword123", "error": "Email is required"},
        {"email": "[email protected]", "password": "", "error": "Password is required"},
        {"email": "notanemail", "password": "validPassword123", "error": "Invalid email format"}
    ])
    def test_login_validation_errors(self, driver, invalid_credential):
        """Test comprehensive login validation error scenarios."""
        # Arrange
        login_page = LoginPage(driver)
        
        # Act
        result_page = login_page.navigate() \
                               .login(invalid_credential['email'], invalid_credential['password'])
        
        # Assert
        assert isinstance(result_page, LoginPage), "Should remain on login page for invalid credentials"
        assert result_page.get_error_message() == invalid_credential['error'], \
               f"Expected error: {invalid_credential['error']}"
        assert result_page.is_password_field_cleared(), "Password field should be cleared after error"

Read the full file on GitHub · 271 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 271 lines · 2,177 tokens per session scan A 6eaeb61f3086

Subscribe to this mod's changes

test-patterns is a cursor rule published in the GitHub repository tugkanboz/awesome-cursorrules (22 stars, last pushed 18d ago), licensed MIT. It adds 2,177 tokens to every session, about $0.0087 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.