sails-gtest

Write and execute Sails-specific gtest suites for Gear/Vara applications.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-gtest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-gtest
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-gtest
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-gtest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable gtest suites for Gear/Vara Sails applications is challenging due to Sails-specific routing quirks, raw SCALE byte handling, block progression requirements, and common Rust edition-specific pitfalls that break generic Rust tests. This skill eliminates the trial-and-error of building Sails-compatible test workflows by providing a standardized, guided loop for feature verification, debugging, and regression coverage.

Core Features & Use Cases

  • Standardized Sails gtest workflow: Provides a step-by-step verification loop that prioritizes generated clients and explicit gtest evidence before moving to live-network testing.
  • Edge case and pitfall guidance: Includes fixes for common breaking issues like Rust 2024 listener lifetime errors, incorrect program balance assertions, and missing block advancement after send operations.
  • Use case: Use this skill when building or modifying a Sails app to verify new feature behavior, debug test failures, or add regression coverage before proceeding to local-node smoke testing.

Quick Start

Use the sails-gtest skill to write and run a gtest suite for your new Sails feature, capture passing test results, and route to local smoke testing once all tests are green.

Frequently Asked Questions about sails-gtest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write reliable gtest suites for Gear and Vara Sails applications?

Reliable Sails gtest suites require handling generated client usage, explicit block advancement after send operations, and proper Sails routing framing to verify features and execute regression tests without trial-and-error.

Why does my Sails gtest fail after send operations without block progression?

Sails gtest suites fail without block progression because send operations require explicit block advancement to process messages correctly. Missing this step causes state updates and program balance assertions to fail during test execution.

What is the best way to handle raw SCALE bytes and routing framing in Sails gtest?

Handling raw SCALE bytes and Sails routing framing in gtest requires using generated clients and applying Sails-appropriate assertions to validate byte encoding and program balance accounting within your test scenarios.

Does this gtest workflow support debugging Rust 2024 listener lifetime errors in Sails apps?

Yes, the Sails gtest workflow includes specific guidance and fixes for common Rust edition pitfalls like Rust 2024 listener lifetime errors, incorrect program balance assertions, and other breaking issues that disrupt generic Rust tests.

Can I use Sails gtest for local-node smoke testing on Gear and Vara?

Sails gtest is designed for feature verification and regression testing before routing to local-node smoke testing. You run the gtest suite until all tests are green, then proceed to local network smoke tests.

What are the limitations of using gtest for Sails app verification versus live-network testing?

Gtest for Sails apps is limited to off-chain feature verification and regression coverage. It does not replace live-network testing, which is required to validate real block progression, gas reasoning, and network-level routing behavior.