Bug#688319: devscripts: Please consider including the 'yodack' tool

[Benjamin Drung]

Am Samstag, den 06.10.2012, 18:46 +0200 schrieb Gergely Nagy:
> Benjamin Drung <bdrung at debian.org> writes:
> 
> > Am Freitag, den 28.09.2012, 15:07 +0200 schrieb Gergely Nagy:
> >> Let me know if there's anything I can do to help this script be
> >> integrated into devscripts!
> >
> > This is just my opinion: I like to see shunit2 tests for yodack before
> > integrating it into devscripts. To make yodack testable, it should be
> > possible to output the command files instead of uploading them. Then you
> > can compare the command files with the expected content. You can also
> > test the return value of yodack and test the behavior for invalid
> > input.
> 
> Makes sense, I'll let you (via this bug) know when the tests are
> done. Most of the stuff one would need for testing are already in
> yodack, all I need is to write the tests themselves. I was already
> pondering about it, but didn't know about shunit2 - so thanks for
> pointing me to the right direction!

You're welcome. I didn't know about shunit2 until someone pointed me to
it after I wrote my own test suite for devscripts. :)

You might want to look at the test/test_* scripts use runCommand() from
test/shunit2-helper-functions.sh.

-- 
Benjamin Drung
Debian & Ubuntu Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20121006/8131c310/attachment-0001.pgp>