skills.rest
gerph
gerphCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

using-tooltesters

Automate RISC OS test suite execution and validation with riscos-tooltester.

3|Updated Apr 10, 2026
Search Tags:#automation#testing#replacement#riscos#tooltester#tests.txt
One-click install
npx skills add https://github.com/gerph/riscos-agent-skills --skill using-tooltesters
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-tooltesters
Source: https://github.com/gerph/riscos-agent-skills/tree/main/skills/using-tooltester
Command: npx skills add https://github.com/gerph/riscos-agent-skills --skill using-tooltesters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance on using the riscos-tooltester command to run tests, manage test suites, and apply replacements to normalise output for consistent results.

Core Features & Use Cases

  • Guides how to run tests with the test.pl script and the testcode/testsuite structure.
  • Explains how tests are organized with testcode/tests-<suite-name>.txt and expected results in testcode/expect/.
  • Describes how replacement scripts normalise variable data in test output to enable reliable comparisons.

Quick Start

Run make tests TEST=<suite-name> to execute a specific test suite.

Frequently Asked Questions about using-tooltesters

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

FAQPage Schema
How do I automate RISC OS test suite execution and validation?▼

To automate RISC OS test suite execution, run make tests TEST=<suite-name> to execute specific suites and validate results using riscos-tooltester with the test.pl script and expected output files.

What is the tests-*.txt file structure used for in riscos-tooltester?▼

The tests-*.txt files in riscos-tooltester define test suites by listing tests located in the testcode directory, allowing the test.pl script to organize and execute multiple test cases systematically.

How do replacement scripts normalise variable data in RISC OS test output?▼

Replacement scripts normalise variable data in RISC OS test output by applying substitutions to standardize dynamic values, enabling reliable comparisons between actual results and expected files stored in the testcode/expect directory.

Does riscos-tooltester require specific files to manage and verify tests?▼

Yes, riscos-tooltester requires the test.pl script, testcode/tests-<suite-name>.txt files for suite definitions, and a testcode/expect/ directory containing expected results to manage and verify test execution properly.

Why do my RISC OS test comparisons fail despite correct functional output?▼

RISC OS test comparisons often fail due to unnormalised variable data in the output; applying replacement scripts standardizes dynamic values, allowing the system to perform reliable comparisons against expected results.

Can I run individual test suites instead of the full riscos-tooltester workflow?▼

Yes, you can run individual test suites by executing make tests TEST=<suite-name>, which targets a specific tests-*.txt file and validates only the associated test cases against their expected outputs.

Related Skills

Explore More Software Engineering Skills→
gerphgerph
3

writing-assembly

Assemble ARM code from the s/ directory with objasm and link with riscos-link.

Community
Advanced
semicolon-devteamsemicolon-devteam

iteration-tracker

Track test iterations and outcomes for GitHub issues via issue comments.

Official
Advanced
gerphgerph
3

using-makefiles

Automate creation and understanding of RISC OS AMU makefiles.

Community
Intermediate
gerphgerph
3

stronghelp-development

Create, edit, and build StrongHelp manuals for RISC OS.

Community
Intermediate