Convert
Import STIL, WGL, VCD or eVCD and generate ATE-targeted patterns and related collateral for current Advantest and Teradyne flows.
local-first · deterministic · ATE-aware
Convert patterns.
Prove equivalence.
Migrate with confidence.
TestXector converts STIL, WGL, VCD and eVCD into Advantest and Teradyne-targeted workflows while keeping timing decisions, comparison evidence and migration risk visible to the engineer.
No cloud upload required · GUI + CLI · deterministic profiles · node-locked and floating commercial options
STILWGLVCDeVCDSmarTest 7/8J750FLEX / UltraFLEX
Real product captureSource → target workflow stays inspectable
SOURCE→CONVERT→TARGET→READBACK→COMPARE
Engineering evidenceTiming · compare · validation
MigrationClean · review · unsupported
Product surfaces
Explore the workspaces engineers use every day.
Browse key TestXector surfaces across import, timing debug, compare, migration and bridge workflows.
REAL PRODUCT
Import complete pattern workspaces
Keep the main pattern, setup collateral, pin maps and profiles together before analysis and target generation.
- Folder-aware source selection
- Format detection and target setup
- Profiles and collateral stay explicit
1 / 5
Why TestXector
Pattern conversion is only useful when engineers can trust the result.
TestXector brings conversion, engineering inspection, equivalence evidence and migration assessment into one connected workflow.
Inspect
Review timing, waveforms, pin behavior, profiles and engineering decisions instead of treating conversion as a black box.
Prove
Compare source and generated output at multiple engineering levels and retain evidence that makes reviews reproducible.
Migrate
Assess source-to-target compatibility, review unsupported constructs and manage cross-platform migration deliberately.
Compact market comparison
Compare the buying decision, not a hundred checkboxes.
Different tool categories solve different parts of the pattern workflow. Use the lenses below to compare the typical emphasis of each approach.
Competitor categories are intentionally anonymized. Capabilities vary by product, version and configuration; confirm against your own engineering requirements.
Cross-platform migration
What changes when the destination tester changes?
Format conversion
May generate several tester formats, while migration assessment is often a separate engineering activity.
Manual adaptation
Useful for direct edits, with source-to-target migration decisions typically handled by the engineer.
Single ecosystem
Usually optimized around its own tester family and surrounding tool flow.
Dedicated workflow
Compatibility assessment, clean/review/unsupported classification, reports and a guided migration workflow.
Closed-loop assurance
Check what came back, not only what went out.
Translation is only one step. TestXector keeps source intent, target generation, readback and comparison connected so assumptions and mismatches remain reviewable.
Qualification boundaryInternal PASS is engineering evidence. Vendor-tool compile/load and tester/customer correlation remain separate qualification steps.
SOURCE EVIDENCE
Start from source engineering intent.
Signals, directions, vectors, waveform tables and timing context are made explicit before conversion decisions are applied.
SignalsVectorsTimingDirection
Unique engineering capabilities
More than format translation.
The differentiator is the connected engineering loop around conversion: inspect, compare, explain, migrate and retain reproducible evidence.
01
Interactive timing workbench
Inspect waveforms in cycle and time domains, place cursors, measure deltas and keep debug tied to the converted pattern.
Round-trip assurance
Read back generated output where supported and compare engineering intent instead of relying on generation success alone.
Source ↔ Target ↔ EvidenceMigration intelligence
Classify clean mappings, review items and unsupported constructs before migration becomes tester debug.
Compatibility · risk · reportsDeterministic profiles
Pin maps, timing variables, setup collateral and inferred decisions stay explicit and reproducible.
Repeatable configurationEngineering evidence
Validation reports, diagnostics and qualification levels leave a trail that can be reviewed and supported.
Explainable outcomes06
Local-first deployment
Pattern IP can stay on the engineering workstation or controlled infrastructure without mandatory cloud upload.
Controlled engineering environmentNode-locked or floating licensingNo mandatory cloud upload
Connected workflow
From source pattern to deployment evidence.
Each stage produces something an engineer can inspect rather than hiding the conversion behind a single button.
- 01ImportPattern + collateral
- 02ConfigureTiming + pin intent
- 03ConvertATE-targeted output
- 04InspectTiming + waveforms
- 05ValidateCompare + evidence
- 06Migrate / deployRisk + target flow
Commercial model
Configure the engineering model you actually need.
Annual Engineer licenses include software updates and standard support. Pricing is explicit about deployment, ATE platform scope and the Migration add-on.
Engineer Node-locked€5,900/ node / year · 1 ATE platform
Engineer Floating€7,900/ concurrent license / year · 1 ATE platform
Additional ATE platform+€2,500/ licensed seat / year
Migration add-on+€599/ month / node
EnterpriseCustom>10 licenses · talk to us
Prices shown in EUR, excluding VAT where applicable. Final commercial order form/EULA governs. No pattern-count, vector-count or cloud-usage meter. Migration pricing shown for node-locked deployment; floating/enterprise deployment scope is confirmed in the quote.
Deployment & trust
Engineering claims stay bounded by evidence.
TestXector is designed for controlled environments and makes the distinction between internal validation and production qualification explicit.
Pattern IP stays controlled
Desktop/local processing, offline-capable node licensing and controlled infrastructure options.
Scope is explicit
ATE platforms and commercial add-ons are enabled deliberately rather than hidden behind ambiguous editions.
PASS means what it says
Internal parse/compare/validation evidence is not presented as vendor-tool or tester qualification.
Internal validation≠Vendor-tool compile / load≠Tester + customer qualification
FAQ
What engineering teams usually ask first.
Which input formats are supported?
Current product scope includes STIL, WGL, VCD and eVCD workflows, with functional and scan-oriented processing depending on source content.
Which ATE families are the current commercial focus?
Advantest SmarTest 7/8-style and Teradyne J750/FLEX/UltraFLEX-style workflows are the current focus. Exact target maturity and entitlement should be confirmed during evaluation.
Does TestXector require pattern files to be uploaded to the cloud?
No. The standard product is designed for local or controlled-infrastructure operation.
Does internal validation mean a pattern is tester-qualified?
No. Internal parsing, comparison and validation are engineering evidence. Vendor-tool compile/load and tester/customer correlation remain the authority for production qualification where applicable.
What does the Migration add-on add?
Cross-platform compatibility assessment, migration risk/review items, reports and the dedicated source-to-target migration workflow. It is intended for customers operating two or more enabled ATE platforms.
Technical evaluation
Bring one real engineering problem.
Tell us the source, target and what needs to be proven. We can structure the evaluation around that workflow rather than a generic product tour.
NO UPLOAD
No pattern data is uploaded by this page. The enquiry is prepared locally and opened in your mail application.