Q414: Implementation Drill Practice Console Manual QA Script

What Interviewers Want To Evaluate

This drill tests whether you can write a manual QA script that someone else can follow.

Manual QA is not a replacement for tests, but it is useful for visual, keyboard, and theme behavior while the practice ground is still evolving.

Short Interview Answer

I would create a short manual QA script for the JS and TS practice pages that covers run, error, copy, clear, reset, keyboard shortcuts, theme switching, and responsive layout. The script should be specific enough that another developer can run it and know what success looks like.

QA Script

Run:

open JavaScript practice
run default sample
verify output appears
copy code
copy console
clear console
reset code
clear code
try empty copy

Then repeat for TypeScript.

Keyboard Script

Check:

Tab indents
Shift Tab outdents
Alt Down duplicates line
Ctrl Enter runs
Ctrl L clears console
focus remains visible
toolbar buttons are reachable

These are now core product behaviors.

Error Script

Use:

throw new Error("practice")
console.error("failed")
invalid TypeScript syntax

Expected:

error appears
console remains readable
copy still works
clear recovers

Theme Script

Check:

light theme buttons
dark theme buttons
secondary button contrast
copy feedback contrast
console error contrast
read-more pill contrast
focus ring contrast

This directly targets the current UI risk.

Responsive Script

Check:

desktop side-by-side
tablet stacking or readable columns
mobile stacked layout
toolbar wrapping
long button labels
console scroll

The tool should degrade gracefully.

Common Mistakes

• Writing vague QA notes.
• Not including expected results.
• Forgetting TypeScript.
• Testing only happy path.
• Ignoring dark mode.
• Not checking keyboard shortcuts after UI fixes.

Final Mental Model

Manual QA scripts should be:

specific
short
repeatable
workflow-based
expected-result driven

Good scripts turn uncertainty into a checklist.