modifying-test-components

Rebuild WebAssembly test components after SDK or source changes.

1.5k|207|Updated Nov 24, 2023
One-click install
npx skills add https://github.com/golemcloud/golem --skill modifying-test-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modifying-test-components
Source: https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-test-components
Command: npx skills add https://github.com/golemcloud/golem --skill modifying-test-components

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of rebuilding WebAssembly (WASM) components used for testing, ensuring that your test environment accurately reflects the latest SDK changes or component modifications.

Core Features & Use Cases

  • Targeted Rebuilds: Rebuilds specific test components only when necessary, such as after SDK updates or source code changes.
  • Dependency Management: Guides users on the correct order for rebuilding components, especially after changes to the TypeScript or Rust SDKs.
  • Use Case: After updating the golem-rust SDK, use this Skill to identify and rebuild all affected Rust test components to ensure integration tests pass.

Quick Start

Follow the instructions in the skill to rebuild the 'my-test-component' WASM file if its source code has changed.

Frequently Asked Questions about modifying-test-components

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

FAQPage Schema
How do I rebuild WASM test components after modifying source code?

To rebuild WASM test components after source code alterations, you need to manage the recompilation process by following the specific build instructions outlined in AGENTS.md to ensure the test environment reflects the latest changes.

When do I need to recompile WebAssembly test components in the Golem ecosystem?

You need to recompile WebAssembly test components when direct source code alterations occur in test artifacts or when modifications are made to the TypeScript and Rust SDKs, ensuring integration tests pass with the updated dependencies.

What is the correct order for rebuilding test components after a Rust SDK update?

After updating the golem-rust SDK, the correct approach is to identify all affected Rust test components and execute targeted rebuilds, managing the dependency chain to ensure every component reflects the new SDK modifications.

Does this rebuild process handle dependency management for TypeScript SDK changes?

Yes, the rebuild process guides users on the correct order for rebuilding components after TypeScript SDK modifications, ensuring that all affected test artifacts are properly recompiled before running integration tests.

Are there limitations when trying to rebuild only specific WASM test components?

The targeted rebuild approach is limited to scenarios requiring component recompilation due to SDK modifications or direct source code alterations, meaning unnecessary rebuilds are skipped to maintain efficiency within the Golem ecosystem.

Can I use this to rebuild a specific test component like 'my-test-component'?

Yes, you can follow the provided instructions to rebuild a specific WASM file such as 'my-test-component' whenever its underlying source code has changed, ensuring the compiled artifact is up to date.