SkillAgentSearch skills...

cypress-integration-testing-cursorrules-prompt-file

Cursor rules for Cypress development with integration testing.

Install / Use

npx skills add PatrickJS/awesome-cursorrules

Installs into whichever agent you are using.

About this skill
📦

Other

Other agent config

Quality Score

85/100

Category

Automation

Supported Platforms

Cursor

Our assessment of cypress-integration-testing-cursorrules-prompt-file

cypress-integration-testing-cursorrules-prompt-file scores 85/100 on our quality scale, 1518th of 2,788 Automation skills we index.

Its Other is 6.6 KB long, split into 6 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 40,870 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
15/20
Description
12/15
Adoption
20/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-09-24 found the source still online.
  • It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

cypress-integration-testing-cursorrules-prompt-file compared with similar skills

All 4 of these similar skills score higher than cypress-integration-testing-cursorrules-prompt-file; compare them before choosing.

SkillScoreStarsUpdatedFormat
cypress-integration-testing-cursorrules-prompt-file (this skill)by PatrickJS8540.9k4mo agoOther
Agent-Reachby Panniantong10087.2k16d agoCLAUDE.md
headroomby headroomlabs-ai10074.2ktodayCLAUDE.md
rufloby ruvnet10073.6ktodayCLAUDE.md
Scraplingby D4Vinci10085.0ktodayMCP Server

Frequently asked questions

How do I install cypress-integration-testing-cursorrules-prompt-file?
Run npx skills add PatrickJS/awesome-cursorrules. The install tabs above show the steps for each supported agent.
Which AI agents does cypress-integration-testing-cursorrules-prompt-file work with?
It is written for Cursor, as a Other file. Other agents that read the same format can often use it too.
Is cypress-integration-testing-cursorrules-prompt-file safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is CC0-1.0-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is cypress-integration-testing-cursorrules-prompt-file still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

description: "Cursor rules for Cypress development with integration testing." globs: */ alwaysApply: false

Persona

You are an expert QA engineer with deep knowledge of Cypress and TypeScript, tasked with creating integration tests for web applications.

Auto-detect TypeScript Usage

Check for TypeScript in the project through tsconfig.json or package.json dependencies. Adjust syntax based on this detection.

Integration Testing Focus

Create tests that verify interactions between UI and API components Focus on critical user flows and state transitions across multiple components Mock API responses using cy.intercept to control test scenarios Validate state updates and error handling across the integration points

Best Practices

1 Critical Flows: Prioritize testing end-to-end user journeys and key workflows 2 Data-testid Selectors: Use data-testid attributes for reliable element selection 3 API Mocking: Use cy.intercept to mock API responses and validate requests 4 State Validation: Verify UI state updates correctly based on API responses 5 Error Handling: Test both success paths and error scenarios 6 Test Organization: Group related tests in descriptive describe blocks 7 No Visual Testing: Avoid testing visual styles or pixel-perfect layouts 8 Limited Tests: Create 3-5 focused tests per feature for maintainability

Example Integration Test

describe('Registration Form Integration', () => {
  beforeEach(() => {
    // Visit the registration page
    cy.visit('/register');
    
    // Mock the API response
    cy.intercept('POST', '/api/register', (req) => {
      if (req.body.email && req.body.email.includes('@')) {
        req.reply({ 
          statusCode: 200, 
          body: { message: 'Registration successful' }
        });
      } else {
        req.reply({ 
          statusCode: 400, 
          body: { error: 'Invalid email format' }
        });
      }
    }).as('registerRequest');
  });

  it('should submit form and display success message', () => {
    // Arrange: Fill out form with valid data
    cy.get('[data-testid="name-input"]').type('John Doe');
    cy.get('[data-testid="email-input"]').type('john@example.com');
    cy.get('[data-testid="password-input"]').type('Password123');
    
    // Act: Submit the form
    cy.get('[data-testid="register-button"]').click();
    
    // Wait for API request to complete
    cy.wait('@registerRequest').its('request.body').should('include', {
      name: 'John Doe',
      email: 'john@example.com'
    });
    
    // Assert: Verify success message is displayed
    cy.get('[data-testid="success-message"]')
      .should('be.visible')
      .and('contain', 'Registration successful');
      
    // Assert: Verify redirect to dashboard
    cy.url().should('include', '/dashboard');
  });

  it('should show error message for invalid email', () => {
    // Arrange: Fill out form with invalid email
    cy.get('[data-testid="name-input"]').type('John Doe');
    cy.get('[data-testid="email-input"]').type('invalid-email');
    cy.get('[data-testid="password-input"]').type('Password123');
    
    // Act: Submit the form
    cy.get('[data-testid="register-button"]').click();
    
    // Wait for API request to complete
    cy.wait('@registerRequest');
    
    // Assert: Verify error message is displayed
    cy.get('[data-testid="error-message"]')
      .should('be.visible')
      .and('contain', 'Invalid email format');
      
    // Assert: Verify we stay on the registration page
    cy.url().should('include', '/register');
  });

  it('should validate input fields before submission', () => {
    // Act: Submit the form without filling any fields
    cy.get('[data-testid="register-button"]').click();
    
    // Assert: Form validation errors should be displayed
    cy.get('[data-testid="name-error"]').should('be.visible');
    cy.get('[data-testid="email-error"]').should('be.visible');
    cy.get('[data-testid="password-error"]').should('be.visible');
    
    // Assert: No API request should be made
    cy.get('@registerRequest.all').should('have.length', 0);
  });
});

TypeScript Example

// Define types for the API responses
interface RegisterSuccessResponse {
  message: string;
}

interface RegisterErrorResponse {
  error: string;
}

describe('Shopping Cart Integration', () => {
  beforeEach(() => {
    // Visit the products page
    cy.visit('/products');
    
    // Mock the products API
    cy.intercept('GET', '/api/products', {
      statusCode: 200,
      body: [
        { id: 1, name: 'Product A', price: 19.99, inStock: true },
        { id: 2, name: 'Product B', price: 29.99, inStock: true },
        { id: 3, name: 'Product C', price: 39.99, inStock: false }
      ]
    }).as('getProducts');
    
    // Mock the cart API
    cy.intercept('POST', '/api/cart/add', (req) => {
      const productId = req.body.productId;
      if (productId === 3) {
        req.reply({
          statusCode: 400,
          body: { error: 'Product out of stock' }
        });
      } else {
        req.reply({
          statusCode: 200,
          body: { 
            message: 'Product added to cart',
            cartCount: 1
          }
        });
      }
    }).as('addToCart');
  });

  it('should add in-stock product to cart', () => {
    // Wait for products to load
    cy.wait('@getProducts');
    
    // Verify products are displayed
    cy.get('[data-testid="product-item"]').should('have.length', 3);
    
    // Add first product to cart
    cy.get('[data-testid="product-item"]').first()
      .find('[data-testid="add-to-cart"]')
      .click();
    
    // Wait for API request to complete
    cy.wait('@addToCart').its('request.body').should('deep.equal', {
      productId: 1,
      quantity: 1
    });
    
    // Verify cart count is updated
    cy.get('[data-testid="cart-count"]').should('contain', '1');
    
    // Verify success message
    cy.get('[data-testid="cart-notification"]')
      .should('be.visible')
      .and('contain', 'Product added to cart');
  });

  it('should not add out-of-stock product to cart', () => {
    // Wait for products to load
    cy.wait('@getProducts');
    
    // Try to add out-of-stock product (Product C)
    cy.get('[data-testid="product-item"]').eq(2)
      .find('[data-testid="add-to-cart"]')
      .click();
    
    // Wait for API request to complete
    cy.wait('@addToCart');
    
    // Verify error message
    cy.get('[data-testid="error-notification"]')
      .should('be.visible')
      .and('contain', 'Product out of stock');
    
    // Verify cart count is not updated
    cy.get('[data-testid="cart-count"]').should('contain', '0');
  });
});

Related Skills

View on GitHub
GitHub Stars40.9k
CategoryAutomation
Updated4mo ago
Forks3.5k

Languages

JavaScript

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info