The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
Empieza por la explicación más corta y útil antes de profundizar.
The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como una herramienta o abstracción que reduce fricción en el workflow de desarrollo en Solana.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Anchor, validators locales, explorers, SDKs y flujos de testing.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
Pruebas (Programas Solana) (testing) Categoría: Herramientas de Dev Definición: The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners). Relacionados: Bankrun (solana-bankrun), LiteSVM, anchor init / anchor build / anchor test
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
A fast Solana testing framework (solana-bankrun for TypeScript, bankrun for Rust) that runs tests against an in-process Bank without starting a full validator. Bankrun processes transactions ~100x faster than solana-test-validator, supports time warping (advance slots/time), and can load accounts from fixtures or mainnet snapshots.
A lightweight Solana VM for testing Rust programs. LiteSVM provides a minimal SVM environment that executes transactions without the overhead of a full validator. It supports account setup, program deployment, and transaction execution. Faster than solana-program-test and suitable for unit testing individual program instructions.
Anchor CLI commands for project lifecycle. `anchor init <name>` scaffolds a new project (program, tests, Anchor.toml). `anchor build` compiles to SBF and generates the IDL. `anchor test` builds, starts a local validator, deploys, and runs Mocha/Jest tests. `anchor deploy` deploys to the configured cluster. `anchor verify` checks deployed bytecode.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.
The Rust crate (solana-sdk) providing types and utilities for building Solana clients and programs. For on-chain programs, use `solana-program` (no-std compatible subset). For off-chain clients, use `solana-sdk` (full features including keypair generation, transaction signing). The SDK includes types like Pubkey, Instruction, Transaction, and Account.
A property-based testing approach where developers define invariants (properties that must always hold true) and a fuzzer generates random sequences of function calls attempting to violate them. Unlike unit tests that check specific scenarios, invariant tests explore the state space stochastically. Tools like Foundry invariant testing, Echidna, and Medusa support this approach.
The official command-line tool for interacting with Solana clusters. Key commands: `solana balance`, `solana transfer`, `solana program deploy`, `solana config set --url`, `solana airdrop` (devnet). Configuration in `~/.config/solana/cli/config.yml` sets the default cluster URL and keypair path.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
A fast Solana testing framework (solana-bankrun for TypeScript, bankrun for Rust) that runs tests against an in-process Bank without starting a full validator. Bankrun processes transactions ~100x faster than solana-test-validator, supports time warping (advance slots/time), and can load accounts from fixtures or mainnet snapshots.
A lightweight Solana VM for testing Rust programs. LiteSVM provides a minimal SVM environment that executes transactions without the overhead of a full validator. It supports account setup, program deployment, and transaction execution. Faster than solana-program-test and suitable for unit testing individual program instructions.
Anchor CLI commands for project lifecycle. `anchor init <name>` scaffolds a new project (program, tests, Anchor.toml). `anchor build` compiles to SBF and generates the IDL. `anchor test` builds, starts a local validator, deploys, and runs Mocha/Jest tests. `anchor deploy` deploys to the configured cluster. `anchor verify` checks deployed bytecode.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
The most popular framework for building Solana programs in Rust. Anchor provides macros (#[program], #[account], #[derive(Accounts)]) that auto-generate boilerplate for account validation, serialization, discriminators, and error handling. It includes a CLI (anchor init/build/test/deploy), IDL generation, and TypeScript client generation. Reduces program code by ~80% compared to native development.
The Anchor macro applied to structs to define on-chain account data layouts. `#[account]` auto-derives Borsh serialization, adds an 8-byte discriminator prefix (SHA-256 of 'account:<Name>'), and implements space calculation. Optional attributes: `#[account(zero_copy)]` for zero-copy deserialization of large accounts.
The Anchor macro that defines the accounts struct for an instruction. Each field specifies an account with validation constraints. Account types include: `Account<'info, T>` (deserialized), `Signer<'info>` (must sign), `Program<'info, T>` (program reference), `SystemAccount<'info>`, and `UncheckedAccount<'info>` (no validation, use carefully).
Declarative validation rules on Anchor account fields. Key constraints: `#[account(mut)]` (writable), `#[account(init, payer=x, space=n)]` (create), `#[account(seeds=[...], bump)]` (PDA validation), `#[account(has_one=field)]` (field equality), `#[account(constraint = expr)]` (custom boolean), `#[account(close=target)]` (close and reclaim rent).