On Tue, 2020-07-14 at 06:53 +0200, Helge Kruse wrote:
>
> It's suggested to prepare a sample dumps and a "unit test" where the
> output of the decoder is compare with a sample output. Unfortunately I
> have problems with the configuration of the utility runtc that actualy
> performs the "unit test".
Have never used the runtc executable myself. See the README and
the pdtest utility. It executes decoder tests. Typical options
are -r and -v, and either -a or a list of decoder names.
And there is also -f which creates the expected data for new
tests, or adjusts existing expectations. Create or extend a
test.conf file as needed, and run pdtest with -f. Then there is
the most important step: Carefully inspect the change, and see if
it's plausible to you. Then commit and push the change.
Can't do that here for you with the data file that you provided.
Haven't seen your extended version of the decoder yet.
In general you need not delay any of the submissions until all of
them are complete. It's already useful to have example captures
available long before a decoder becomes available or gets
extended to support more features. Of couse tests only become
applicable after PD creation or fixes/extension. But I do suggest
to submit test captures first, and early on. The PD itself and
its test can follow later.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
