Automated test farm

Tool

The automated test farm is a Crusoe development tool comprising in-house farm hardware and software that allows unattended initialization of CMS, the BIOS, and the hard disk drive, so that any machine can be allocated, configured, and reallocated for purposes such as remote interactive debugging or batch testing with arbitrary versions of CMS, BIOS, and disk image. The farm executes long-running tests to find bugs and leaves checkpoints so developers can quickly reach the point of failure found by automation, and it is paired with multiple categories of tests and automatic test generators.

First seen 9/21/2026

Last seen 9/21/2026

Evidence 4 chunks

Wiki v1

WIKI

Automated test farm

The automated test farm is one of the key tools used during the development of the Transmeta Crusoe processor. It is listed alongside reference x86 simulators, corner-case tests, a fast simulator, fault-isolating debuggers, and test generators as a tool used to "build, run, and debug Crusoe."

Purpose and capabilities

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

10 connections

VLIW test suites uses → 58% 2e

The environment conducts testing with VLIW suites, and the farm executes automated tests at scale; together these indicate the farm used VLIW suites.

x86 test suites uses → 58% 2e

Since the testing workflow uses x86 suites and the farm automates long-running tests, the farm is used to execute x86 suites.

Industry-standard test suites uses → 66% 1e

Industry-standard tests are part of the external test corpus; given the farm’s role in batch and automated testing, it is used to run these suites.

Acceptance test suites uses → 66% 1e

Acceptance suites are among the external tests exercised; the farm infrastructure is used to automate these runs.

Application and OS-based tests uses → 65% 1e

Applications and OSes are explicitly used as tests in the environment; automated farm testing is the mechanism to run these at scale.

Performance tests uses → 62% 1e

Performance tests are one of the enumerated categories used in testing; the farm infrastructure automates their execution.

Benchmarks used as tests uses → 60% 1e

Benchmarks are used as tests within the testing regimen; the farm is the automated facility to run long and batch tests, including benchmarks.

Automatic instruction-level test generators uses → 62% 1e

The paper lists a highly automated test farm alongside test generators among the core tools, indicating operational use of generators within the farm-driven testing workflow.

Corner-case tests uses → 50% 1e

Corner-case tests are listed among the key tools used alongside the automated test farm within the development and testing toolchain, indicating the farm’s role in executing them.

Automatic system-level test generators uses → 55% 1e

Automatic generators (including system-level) are stated as being used for testing; combined with the farm’s role in automated testing, this implies the farm ran tests produced by these generators.

LINKED ENTITIES

10 links

Automatic instruction-level test generators USES Extracted graph relationship

Automatic system-level test generators USES Extracted graph relationship

VLIW test suites USES Extracted graph relationship

x86 test suites USES Extracted graph relationship

Industry-standard test suites USES Extracted graph relationship

Acceptance test suites USES Extracted graph relationship

Application and OS-based tests USES Extracted graph relationship

Performance tests USES Extracted graph relationship

Benchmarks used as tests USES Extracted graph relationship

Corner-case tests USES Extracted graph relationship

CITATIONS

9 sources

9 citations — click to expand

[1] The automated test farm comprises in-house farm hardware and software that allow automated initialization of CMS, the BIOS, and the hard disk drive. Transmeta Crusoe Hardware, Software, and Development

[2] Any farm machine can be allocated, configured, and used for remote interactive debugging, then without human intervention reallocated and reconfigured for another use such as batch testing with any desired versions of CMS, BIOS, and disk image. Transmeta Crusoe Hardware, Software, and Development

[3] Automated farm testing executes long-running tests to find bugs, then leaves checkpoints so humans can quickly get to the point of failure found by automation. Transmeta Crusoe Hardware, Software, and Development

[4] Checkpoints may be loaded by different debugger sessions and are also an easy way to hand off debugging sessions between developers. Transmeta Crusoe Hardware, Software, and Development

[5] Testing uses both VLIW and x86 suites; tests include instruction-level tests and system-level tests including performance tests; VLIW tests are all in-house while x86 tests include in-house and external tests bought from other companies, industry-standard tests, applications and OSes used as tests, and acceptance suites used by individual makers. Transmeta Crusoe Hardware, Software, and Development

[6] Several automatic instruction-level and system-level test generators are used in addition to traditional hand-written tests and real workloads. Transmeta Crusoe Hardware, Software, and Development

[7] Automated tests find both hardware and software bugs including tricky corner cases missed by hand-written tests, and a technique of biased random number generation was used to balance coverage of interesting and 'boring' cases. Transmeta Crusoe Hardware, Software, and Development

[8] The automated test farm is listed among example tools used to build, run, and debug Crusoe alongside reference x86 simulators, corner-case tests, a fast simulator and fault-isolating debugger, and test generators. Transmeta Crusoe Hardware, Software, and Development

[9] In-house debug systems are in limited supply and often need rework, motivating the flexibility provided by the farm. Transmeta Crusoe Hardware, Software, and Development