How to log unittest results?

[EricN]

I like to use unittest. However, when my QA Manager shows up in my
cube and says "Give me evidence that all your unit tests passed", I
have nothing to provide. I'd like to log the unittest results
(verbose mode) somehow. I'm open: logger module, stdmsg redirect,
whatever.

Thanks.

 

[Roy Smith]

I like to use unittest. However, when my QA Manager shows up in my
cube and says "Give me evidence that all your unit tests passed", I
have nothing to provide. I'd like to log the unittest results
(verbose mode) somehow. I'm open: logger module, stdmsg redirect,
whatever.

Thanks.

Unless you're doing something very unusual, most unit test suites run in
a very short amount of time. When PHB asks if your unit tests pass,
just run them and demonstrate.

If you really want to archive evidence of them having run in the past, I
would think the simpliest way would be to capture the output with the
script command (assuming a unix-like environment).

In one sense, all that really matters is that all your unit tests pass
NOW. What does it matter if you can show evidence that they ran
yesterday if you've broken the code since then? Of course, PHB's being
what they are, recording your test runs with script may be what it takes
to keep him off your back

 

[John Roth]

I like to use unittest. However, when my QA Manager shows up in my
cube and says "Give me evidence that all your unit tests passed", I
have nothing to provide. I'd like to log the unittest results
(verbose mode) somehow. I'm open: logger module, stdmsg redirect,
whatever.

I'd start by asking him what he wants as evidence. I'd also ask
him if he want's to be shown how his people can run the test
scripts and verify that they all pass for themselves.

John Roth

 

[Dang Griffith]

I like to use unittest. However, when my QA Manager shows up in my
cube and says "Give me evidence that all your unit tests passed", I
have nothing to provide. I'd like to log the unittest results
(verbose mode) somehow. I'm open: logger module, stdmsg redirect,
whatever.

Another way to pacify the QAM would be to show the version control
log. If you check your stuff in at each stage, and have comments
saying what was fixed (e.g., "passed unittest XYZZY"), that should be
sufficient for QA purposes. QA confirms that the process is being
followed--not that the code works.

Sorry I can't help, but why would your QAM care about this level of
detail? Unless your code is looking bad (i.e., high defect density)
later, when it's integrated, your personal development process, i.e.,
using unittest or not, is too low-level of a detail. MicroQAM. Does
your QAM also want to see marked up printouts of your code, showing
that you performed a code review? Design review? Etc?

--dang