Acceptance test suites

Tool

Acceptance test suites are externally sourced collections of tests used as acceptance criteria in the validation of the Transmeta Crusoe processor's x86 software and hardware. They are part of a broader testing program that combines in-house and external tests to evaluate both VLIW and x86 behavior, and they feed results into an automated test farm that supports allocation, configuration, and reconfiguration of machines for debugging and batch testing.

First seen 9/21/2026

Last seen 9/21/2026

Evidence 1 chunks

Wiki v1

WIKI

Overview

Acceptance test suites are external test collections used to validate the Transmeta Crusoe processor's x86 implementations. They are drawn from "other companies," industry-standard tests, applications and operating systems used as tests, and "acceptance suites used by individual makers," serving as input to the Crusoe hardware/software validation flow described in the 2009 Crusoe retrospective paper.

Role in the Crusoe testing program

The Crusoe validation effort distinguished between in-house and external test sources:

In-house tests: All VLIW tests were written in-house, while some x86 tests were also written in-house.
External tests: x86 tests were augmented with tests bought from other companies, industry-standard tests, applications and OSes used as tests, and acceptance suites used by individual makers.

READ FULL ARTICLE →

NEIGHBORHOOD

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

explore full graph →

RELATIONSHIPS

1 connections

Automated test farm ← uses 66% 1e

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

LINKED ENTITIES

1 links

Automated test farm USES Extracted graph relationship

CITATIONS

5 sources

5 citations — click to expand

[1] x86 testing includes both in-house and external tests, with external tests comprising 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

[2] In the Crusoe methodology, "test" implies an acceptance or rejection criteria; some benchmarks have checkable results files while "crashes" and "fails to complete" are also treated as checkable failures. Transmeta Crusoe Hardware, Software, and Development

[3] The in-house farm's automated initialization of CMS, the BIOS, and the hard disk drive allows any machine to be allocated, configured, and reallocated for purposes such as remote interactive debugging or batch testing without human intervention, with any desired versions of CMS, BIOS, and disk image. Transmeta Crusoe Hardware, Software, and Development

[4] Automatic instruction-level and system-level test generators are used in addition to hand-written tests and real workloads, and their tests are complicated enough to find failures not found by simple tests while often being simpler to diagnose than real-workload failures; generators can be constrained to emphasize or exclude features to help find small, easy-to-debug test cases. Transmeta Crusoe Hardware, Software, and Development

[5] A remote debugger stub is built into CMS, queries a special debug connector on boot, and downloads a larger debug stub if "live"; the debugger's user interface is kept consistent between simulation and hardware. Transmeta Crusoe Hardware, Software, and Development