Siesta: Automation Dry Run

[krullj]

I would like to have the ability to do a "dry run" that allowed you to quickly identify what tests are going to be run based on your --include and --exclude options.

[rengine]

Seconded . This is exactly what I posted about here.

For now, I've used the "tree" command in Linux to get all of my tests, then use the regexr website to create a regular expression, then I can use the regular expression in testing to see if it works, and then finally move it to production

Adding to this idea, it would be nice to see the order at which multiple tests are run.