reliable unit test logging

[Vyacheslav Maslov]

Ben Finney wrote:
> Vyacheslav Maslov <vmaslov at swsoft.com> writes:
> 
>> I have many many many python unit test, which are used for testing
>> some remote web service.
> 
> Part of your confusion comes from the fact that "test a remote
> service" isn't what a unit test does.
> 
> A unit test is one that executes a very *limited* part of the code: it
> tests a code unit, not the whole system, and makes a simple set of
> assertions about the result. If there are accesses to remote services
> over the network, that's far beyond the scope of a unit test.
> 
> I don't doubt that you may be using the Python standard library module
> 'unittest' to perform these tests. But they're not unit tests; they're
> integration tests, or system tests, or performance tests, or something
> else.
> 
>> Can someone explain my why so simple feature like logging of
>> timestamps during test execution was not implemented in any
>> extension?
> 
> Probably because the most important thing to know for the purpose of a
> unit test is whether the yes/no assertions were violated. Knowing when
> the tests start and finish isn't interesting. If start and finish
> times *are* interesting for your tests, you're *not* doing unit
> testing, but some other form of testing like performance tests.
I understand your opinion, you are right, i use unit tests for some 
other kind of work. But anyway it works and produce good results for 
project.

> Untested code, that should give you enough to try it out yourself:
Thanks i will look into this.