Analysis Workspace

Configure target scenario, inspect schema, and execute twin-environment verification.

Target: zodv3.23.8 (Baseline)->v4.6.7 (Candidate)

Section A: Select Verified Scenario

Target Schema DefinitionTypeScript

// Schema defined by developer
const registrationSchema = z.object({
  username: z.string({ required_error: "Username is required" }).min(3),
  email: z.string({ 
    required_error: "Email is required", 
    invalid_type_error: "Email must be a string" 
  }).email("Invalid email format"),
  age: z.number({ required_error: "Age is required" }).min(18),
  newsletter: z.boolean().default(false)
});

Compares form validation schemas using legacy custom error options (required_error / invalid_type_error) vs Zod v4 unified error syntax.

Synchronized Test Corpus (5)

#1Valid Complete SubmissionOracle: VALID

{"username":"alex_dev","email":"alex@company.org","age":28,"newsletter":true}

#2Missing Required Username (Custom Error Expectation)Oracle: INVALID

{"email":"alex@company.org","age":28}

#3Invalid Type for Email FieldOracle: INVALID

{"username":"alex_dev","email":998877,"age":28}

#4Underage User with Valid String EmailOracle: INVALID

{"username":"junior_coder","email":"junior@school.edu","age":15}

#5Omitted Default Boolean FieldOracle: VALID

{"username":"alex_dev","email":"alex@company.org","age":30}

+ Add Custom Test Input

Execution Control & StatusStatus: Ready

Ready to execute twin runtime comparison