A Rust testing framework in the solana-sdk that provides a BanksClient for in-process program testing. Programs are loaded directly into a test Bank without a network. Supports adding accounts, advancing clock, and processing transactions. Slower than LiteSVM/Bankrun but provides the most accurate runtime behavior for Rust-only test suites.
Comece pela explicação mais curta e útil antes de aprofundar.
A Rust testing framework in the solana-sdk that provides a BanksClient for in-process program testing. Programs are loaded directly into a test Bank without a network. Supports adding accounts, advancing clock, and processing transactions. Slower than LiteSVM/Bankrun but provides the most accurate runtime behavior for Rust-only test suites.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como uma ferramenta ou abstração que reduz atrito no workflow de desenvolvimento em Solana.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Anchor, validators locais, explorers, SDKs e fluxos de teste.
Transforme o termo de vocabulário em algo operacional para produto e engenharia.
Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
solana-program-test (solana-program-test) Categoria: Ferramentas de Dev Definição: A Rust testing framework in the solana-sdk that provides a BanksClient for in-process program testing. Programs are loaded directly into a test Bank without a network. Supports adding accounts, advancing clock, and processing transactions. Slower than LiteSVM/Bankrun but provides the most accurate runtime behavior for Rust-only test suites. Relacionados: Testes (Programas Solana), Bankrun (solana-bankrun)
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
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).
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.
Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.
Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.
Solana's built-in testing framework that spins up a lightweight BanksClient runtime to execute programs in an isolated environment without a full validator. Supports adding programs, setting account state, advancing slots/time, and processing transactions. The foundation for most Solana program integration tests.
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.
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.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
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).
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.
Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.
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).