How to use the Regex Tester.
Testing requires an actual compatible regex engine. Report the pattern, flags and sample strings so the result can be reproduced.
Make the workflow fit your task.
Run the supplied pattern and flags against explicit strings in a compatible regex engine. Record match status and, where relevant, captures or positions, keeping the exact test inputs available for reproduction.
- What you provide
- Pattern, flavor and sample strings.
- What you get
- Match results from an appropriate deterministic regex engine.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
JavaScript expression /^cat$/ with no flags. Test cat, Cat, cats and a string containing cat followed by a newline.
Completed example
cat → true Cat → false cats → false cat followed by a newline → false Reproduce with: samples.map(value => /^cat$/.test(value))
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can a prose explanation substitute for running regex tests?
It can describe expected behavior, but a test result requires actual evaluation in the stated engine. Keep predictions and executed results distinct.
Why do repeated tests behave differently with the same JavaScript pattern?
Inspect stateful flags and lastIndex handling, especially with global or sticky expressions. Use a deliberate reset or fresh instance for independent tests.
Reference for this workflow.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑