DOCSEARCHbyAlgolia
Submit Docs

Vue Test Utils

website·Indexed 30 days ago

https://note.wedsatcoming.com

The official testing utility library for Vue.js. This documentation focuses on Vue Test Utils v2 for Vue 3, covering component mounting, wrapper methods, stubs, shallow mounting, and element lookup for verifying component behavior.

Tokens
77.3K
Snippets
411
Records
547
Agent score
49%

What's inside Vue Test Utils

  2. Overview of the OPSX Workflow

    OPSX is the standard fluid and iterative workflow for OpenSpec changes. Unlike legacy linear workflows, OPSX uses an action-based approach (propose, apply, archive) rather than rigid phases. This allows developers to experiment with prompts, test individual artifacts independently, and define custom workflows and dependencies. The typical flow is: proposal → specs → design → tasks → implement.

  3. Overview of MCP Server Core Building Blocks

    An MCP server exposes specific capabilities to AI applications through a standardized protocol. It provides functionality using three primary building blocks:

    1. Tools: Used for AI actions (e.g., searching flights, sending messages). These are model-controlled.
    2. Resources: Used for content data (e.g., documents, calendar events, weather data). These are application-controlled.
    3. Prompts: Used for interaction templates (e.g., "Plan a vacation", "Summarize my meeting"). These are user-controlled.

  4. Overview of Gemini CLI

    Gemini CLI is a command-line interface tool developed by Google AI that integrates Gemini models directly into the terminal. It acts as an AI Agent capable of understanding project context, reading/writing files, executing commands, and assisting with coding, refactoring, and debugging. It is context-aware, treating the current working directory as a workspace to analyze file and folder structures.

  5. Overview of the wedsatcoming knowledge base

    The wedsatcoming documentation site serves as a technical resource hub providing the following content:

    • Technical document translations into Traditional Chinese.
    • Technical perspectives and simplified explanations of complex concepts using AI tools.
    • Recommendations and records of useful developer tools.
    • Learning notes derived from using Large Language Models (LLMs) to study various technologies.
    • Practical implementation notes and guides for technical projects.

  6. Overview of Model Context Protocol (MCP)

    The Model Context Protocol (MCP) is an open standard designed to enable seamless integration between LLM applications and external data sources and tools. It provides a standardized way to connect LLMs with the context they need, whether for AI-driven IDEs, enhanced chat interfaces, or custom AI workflows. The protocol is based on JSON-RPC 2.0 and defines three primary roles:

    • Hosts: The LLM applications that initiate connections.
    • Clients: Connectors within the host application.
    • Servers: Services that provide context and functionality.

  7. Overview of Agent Skills open standard

    Agent Skills is an open standard (originally developed by Anthropic) that allows AI agents to dynamically expand their capabilities by loading procedural knowledge and context-specific information. A 'Skill' consists of a collection of instructions, scripts, and resources organized within a folder. This enables agents to perform complex tasks more accurately and efficiently by providing them with domain expertise, new functional capabilities (e.g., building MCP servers or analyzing datasets), and repeatable, auditable workflows.

    Key benefits include:

    • For Authors: Write a skill once and deploy it across multiple compatible agent products.
    • For Agent Products: Allow end-users to add new features to the agent directly.
    • For Organizations: Encapsulate organizational knowledge into portable, version-controlled packages.

    Compatible tools include Claude Code, Cursor, Windsurf, Cline, Augment, and Zed.

  8. Overview of Git Worktree

    Git Worktree allows you to have multiple working directories attached to the same Git repository. Each directory can be checked out to a different branch, eliminating the need to frequently use git checkout or git stash when switching tasks. This is particularly useful for fixing bugs in main while developing a feature, comparing code between two branches, or running tests without interrupting current work.

  10. Overview of changes from OpenSpec to OPSX

    OPSX replaces the legacy stage-locked workflow with a fluid, action-oriented approach. Key changes include:

    • Commands: Legacy commands like /openspec:proposal are replaced by /opsx:propose, /opsx:apply, and /opsx:archive.
    • Workflow: Artifacts can now be created incrementally or all at once, rather than in a fixed sequence.
    • Flexibility: Artifacts can be updated at any time without restrictive stage gates.
    • Configuration: Configuration moves from CLAUDE.md markers and project.md to a structured openspec/config.yaml file.

  11. Overview of SuperClaude slash commands

    SuperClaude provides a set of intelligent slash commands to automate development tasks. The system automatically enables relevant 'experts' (e.g., Security, Performance, QA, Architecture) and MCP servers based on the command used and the context of the request. Users do not need to manually manage these experts.
    /sc:index        # List all available commands
/sc:analyze      # Intelligent code analysis
/sc:workflow     # Create implementation plan from PRD
/sc:implement    # Build features, components, or APIs
/sc:build         # Project build and packaging
/sc:improve       # Code cleanup and refactoring
/sc:troubleshoot # Debugging and issue investigation