Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/568#issuecomment-210501721
I don't see any reason to block writing tests on some proposed framework.
All you really need to write a test is a hook to run it (which we have) and a
way to check state (which we have). I think that is is possible to write an
actual unit test for this, focusing on just the ``Diags`` class, but for now
I'd also be ok with a shell-script or something like what we used for testing
access log rolling in the first iteration of TSQA.
Off the top of my head, how about a test that starts a few threads writing
diagnostics, then a second set of threads that continually rebinds ``stderr``
and ``stdout`` to ``/dev/null``?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
