Exactly. And this is the second reason why your solution is bad. When it comes to testing, QUALITY trumps QUANTITY. I could care less how fast you churn out tests if they do not catch the actual problems before they work their way into production.

I of course could not realize your reality , but I use swat for a dozens web applications daily. I mean I write a new tests daily because I need this and I have time shortage, this is not artificial but real life context. This is how swat appeared . Swat by design is specially for smoke tests , no user acceptance, no UI, no Java script , no Ajax , etc, I quite ok with that there are speal tools for that ( and you know I have an experience with this too. ) But look, I talk about smoke tests , my context is quite simple - give this host a curl , check some http uri-s and that is it.

So the quality is over quantity , I agree. With swat I get qualitive smoke tests with low time price . Sure. This is proven by my experience. So why do not you try?

"Swat by design is specially for smoke tests ..."

Then this module is snake oil. Why don't I try it? Because you have not shown me why I should. Why don't you try Mojolicious or Dancer and see how they handle this kind of testing instead. I've already been where you are and I've since seen the light. Stop wasting your time on this.