Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #98003

Re: Unittests and serial workflows

Show all headers | View raw

On 10/27/2015 07:18 AM, Paul Rubin wrote:
>> >     def test_b(self):
>> >         tmp = A()
>> >         out = B(tmp)
>> >         self.assertStuffs(out)
> It's better to avoid that.  Write B so that it doesn't require input to
> actually come from A, but rather, write or generate some other sample
> input.  Then test B separately from A.  Then afterwards you can have
> function C that calls both, and put a test case through that.

Thanks for your thoughts. I am not sure that this is always possible in 
my case, but I see what you mean.

Cheers,

Fabien

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Unittests and serial workflows Fabien <fabien.maussion@gmail.com> - 2015-10-27 05:10 +0100
  Re: Unittests and serial workflows Paul Rubin <no.email@nospam.invalid> - 2015-10-26 23:18 -0700
    Re: Unittests and serial workflows Fabien <fabien.maussion@gmail.com> - 2015-10-30 16:05 +0100
      Re: Unittests and serial workflows Paul Rubin <no.email@nospam.invalid> - 2015-10-30 09:23 -0700
  Re: Unittests and serial workflows Steven D'Aprano <steve@pearwood.info> - 2015-10-31 12:28 +1100

csiph-web