Check values that should and should not match
Use positive and negative cases to check a whole-code pattern, with fresh regex state for each value.
For operators
Use positive and negative cases to check a whole-code pattern, with fresh regex state for each value. This is isolated practice with invented records. Nothing is uploaded or written into a live system.
Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.
Check values that should and should not match
- Require a complete item code
Require a complete item code.
Start and end anchors require the whole value. The multiline flag changes how these boundaries work, so leave it off for this check.
- Enter the code to check
Enter the code to check.
Use BR-0201 as the source value. Separate expected cases will also check a value that should be refused.
- Add an expected matching case
Add an expected matching case.
Each case runs with fresh regex state, so previous matches cannot change its result.
- Enter the complete code
Enter the complete code.
This four-digit code should match the anchored pattern.
- Add an expected non-matching case
Add an expected non-matching case.
A shorter code should not pass just because one valid code worked.
- Enter the short code
Enter the short code.
BR-201 has only three digits. Keep it as a deliberate refusal case.
- Choose the expected refusal
Choose the expected refusal.
This case should not contain a match. Set that expectation explicitly before running.
- Check both expected outcomes
Check both expected outcomes.
Both cases must agree with their expectations. A match checks the pattern only, not whether an item exists in another system.
Review the result and its limits before using it in another application.