Re: [Zope-dev] Why is test.py silent by default

Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The default usecase for running tests should be a developer making changes and running tests. In this case, silent mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole

[Zope-dev] Why is test.py silent by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The default usecase for running tests should be a developer making changes and running tests. In this case, silent mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The dots

Re: [Zope-dev] Why is test.py silent by default

Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The default usecase for running tests should be a developer making changes and running tests. In this case, silent mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole

Re: [Zope-dev] Why is test.py silent by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The default usecase for running tests should be a developer making changes and running tests. In this case, silent mode is unhelpful; it gives no feedback