Re: [PATCH] Documentation: kunit: provide guidance for testing many inputs

2020-11-23 Thread Daniel Latypov
On Mon, Nov 23, 2020 at 10:32 AM Brendan Higgins wrote: > > On Mon, Nov 2, 2020 at 1:37 PM Daniel Latypov wrote: > > > > usage.rst goes into a detailed about faking out classes, but currently > > lacks wording about how one might idiomatically test a range of inputs. > > > > Give an example of ho

Re: [PATCH] Documentation: kunit: provide guidance for testing many inputs

2020-11-23 Thread Brendan Higgins
On Mon, Nov 2, 2020 at 1:37 PM Daniel Latypov wrote: > > usage.rst goes into a detailed about faking out classes, but currently > lacks wording about how one might idiomatically test a range of inputs. > > Give an example of how one might test a hash function via macros/helper > funcs and a table-

Re: [PATCH] Documentation: kunit: provide guidance for testing many inputs

2020-11-13 Thread Daniel Latypov
On Fri, Nov 6, 2020 at 8:21 PM David Gow wrote: > > On Tue, Nov 3, 2020 at 5:37 AM Daniel Latypov wrote: > > > > usage.rst goes into a detailed about faking out classes, but currently > > Nit: a detailed what? Thanks for the catch, added "detailed section" locally. > > > lacks wording about how

Re: [PATCH] Documentation: kunit: provide guidance for testing many inputs

2020-11-06 Thread David Gow
On Tue, Nov 3, 2020 at 5:37 AM Daniel Latypov wrote: > > usage.rst goes into a detailed about faking out classes, but currently Nit: a detailed what? > lacks wording about how one might idiomatically test a range of inputs. > > Give an example of how one might test a hash function via macros/hel

[PATCH] Documentation: kunit: provide guidance for testing many inputs

2020-11-02 Thread Daniel Latypov
usage.rst goes into a detailed about faking out classes, but currently lacks wording about how one might idiomatically test a range of inputs. Give an example of how one might test a hash function via macros/helper funcs and a table-driven test and very briefly discuss pros and cons. Also highlig