Frontory

Open code, practice, and notes →

Download source with English comments · for reading

Vue · 26 Checking Behavior Regressions and Save Races

Series contents · Technology map

Stage: Canvas Integration and Update Verification · Editable example · Storage ID: vue-step-26

Goals and learning outcomes

Prerequisites

Unit 26 builds on the work and experiment records from Unit 25.

Key concepts and explanations

User flows

Check component contracts through inputs and observable outputs. Depending on internal ref names makes checks fragile when implementations change.

Time control

Delayed saves must not overwrite another unit during rapid switching. Use save-completion conditions or controlled timers rather than fixed waits.

Practice setup

First check the execution scope guidance on the example screen. The following is the preparation environment for extending the assignment in a separate project. Use .vue SFCs and script setup in a separate Vue Vite project. Record package versions and the lockfile, and run on the development server. The built-in Vue examples use the h function and are not a general-purpose SFC compiler.

The linked example is a starting point. It does not implement every task below. Complete work beyond its supported scope in a separate project.

Practice tasks

  1. Write add, toggle, search, and A/B draft-switching checks in tests/workspace.spec.js.
  2. Reproduce entering A then switching to B with a 1000ms save delay.
  3. Also check 0 active loops after Canvas removal and 1 after showing it again.

Variables to observe

VariableBaselineChangeExpected change / hypothesis
Input intervalLonger than the save delayShorter than the save delayThe draft's unit id remains correct even with short intervals.

Predictions in this table are not measured results. Change one condition at a time and record why the actual result differs.

Completion criteria

Self-check

  1. How do fake timers differ from actual browser RAF checks?
  2. What changes if storage is not reset before a test?

Official references

Linked example and execution scope

Example source · Runtime environments and limits

This is an experiment with actual Vue reactivity and render functions. Check SFC templates in an external compilation environment.

Source code and records are not overwritten automatically. Resetting an existing example also preserves your notes.

Next learning

Previous: Observing Vue Performance · Next: Composition API Integration Review

Open code, practice, and notes →