So here's a bit of a pickle. Just by using TAP::Harness $ENV{HARNESS_ACTIVE}
gets set to true. This seems odd since you can you it outside of a running test.
And this causes problems with Smolder. When I'm running the test suite I don't
want it to do certain things (like actually send email alerts), so I do a test
to not do them if $ENV{HARNESS_ACTIVE}. But I do want to do them live. But since
I use TAP::Harness::Archive (which uses TAP::Harness) to get the results out of
an existing TAP archive Smolder constantly thinks it's being tested.Thoughts? -- Michael Peters Plus Three, LP
