Hi there,
I've had few words about "jallib" wrapper and how tests can be handled.
Questions are how the script can know which test is available for which PIC,
so it can generate at any time, a new matrix (or update an existing one to
include new tests/samples).
Could you have a look at the following ?
Thanks,
Seb
> Just was about to ask how to use the test section in the yaml file
>> when I read this. Can you give me an example on this?
>
>
> Don't invest too much time on "jallib" script, it's not ready. I worked
> quite a lot on it, trying to provide an easy way to access the repos. Most
> of work is for handling tests ("test" + "sample") so testers could have a
> easy-to-use tool to perform tests, and report results. For now, I still have
> to get information about svn revision. And deal with "test" map...
>
> ... tests are not handled by jallib. There are deactivated, because I don't
> know yet how to deal with them.
> Samples are easy: you look at "by_device", you have all PICs, then inside,
> all available samples. jallib can then generate a new matrix, or update an
> existing one, by exploring "sample" dir (jallib -u + all other options)
>
> Tests are more complicated.
>
> * I could look at "test" dir and search for "test_*" files, and register
> them for all PIC. The problem is not all PIC can handled all tests (eg, as
> you said before, testing 2 PWM channels on a PIC 16F88). So ? One
> requirement for me: if a test or a sample is registered in the yaml file for
> a given PIC, then it's relevant for this PIC. That way, every piece of
> information in the testing matrix is valid/relevant.
>
> * I could search for "board_*" files, and try to compile board + test. If
> it compiles, I register test for the PIC defined in the board_ file. If not,
> I skip the test. Will compilation always fail when it *has* to fail ?
>
> * finally, we could manually register tests for each PIC which can handle
> them. Updates/generating a new matrix will require manual operations.
>
> Do you see any other options ?
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
