This template is designed to simplify the development of Solana Native Programs, particularly for those not using specific frameworks like Anchor. It offers a testing structure similar to Anchor Framework, aiming to facilitate the development and testing phases of Solana Native Programs.
- Jest for Testing: Integrates Jest for end-to-end testing. This setup automates the building of your program and the initialization of solana-test-validator.
- Log Accessibility: Access your program's logs during testing in
e2e/validator.logfor insights into its behavior. - Configurable Keypair Path: While the default keypair location is in the root directory (
program.json), you have the option to customize the path ine2e/package.json.
- Node.js installation is required (npm included).
- [Solana Tool Suite][https://docs.solana.com/cli/install-solana-cli-tools] Install the Solana Tool Suite
- [Rust] (https://www.rust-lang.org/)
- Clone the Repository: Start by cloning this repository to your local machine.
- Generate Keypair:
- The test suite looks for the program's keypair in
program.jsonin the project's root. - To generate this keypair, use
solana-keygen new -o program.json. - If you prefer a different path for the keypair, modify the configuration in
e2e/package.jsonunder thesolanasection.
- The test suite looks for the program's keypair in
- Go to the E2E Folder: Navigate to the
E2Efolder in the cloned repository. - Install Dependencies: Run
npm installto install all necessary Node.js dependencies. - Run Tests: Start the end-to-end testing with
npm run test.
By default, the program is located in target/sbf-solana-solana/release/solana_program.so, so you could use the command solana program deploy <PROGRAM_FILEPATH> to deploy your program.
.
├── Cargo.lock
├── Cargo.toml
├── README.md
├── e2e
│ ├── tests # E2E Testing
│ │ └── counter.test.ts
├── program.json # Program Keypair
└── src # Rust Solana native program
└── lib.rs