On Thu, Feb 11, 2010 at 12:54 AM, David Brownell <[email protected]> wrote:
> On Wednesday 10 February 2010, Edgar Grimberg wrote:
>> On Wed, Feb 10, 2010 at 10:38 PM, David Brownell <[email protected]> wrote:
>> >
>> > Yes, systematic testing to help uncover regressions is really The Way
>> > To Do Things. I'm not sure how complete our test coverage is, though.
>>
>> One entire category was intentionally left out: commands specific to targets.
>
> How about coverage of boards and board-level mechanisms, like 'reset-init'
> event handlers to initialize things?
I was referring to commands like:
* arm11 vcr [value]
* stm32x options_write bank_id ('SWWDG'|'HWWDG') ('RSTSTNDBY'|'NORSTSTNDBY')
('RSTSTOP'|'NORSTSTOP')
reset init is a valid command for all the targets, so the test cases
don't have to be
adjusted for different targets.
>
>> The goal of this first attempt of systematic of tests was to prove
>> that "basic" functionality is there for each of the tested target.
>> As a constraint, it is necessary that the tests can be easily be ran
>> and reproduced.
>
> That constraint is present for almost all testing. :)
>
>
>> > I still have some board tests on my list-of-stuff-to-do, but I did get
>> > most of them done.
>>
>> Post them over and I'll make sure to include them in the template and
>> ask Laurentiu to run them when he gets the chance.
>
> He won't be able to do that with boards he doesn't have. ;)
If there are tests we can cover with the test farm that we have, don't hesitate
to post them. Also, donations to our test farm are always welcomed and
appreciated :)
> Of course, there's also value in more ad-hoc testing; it's likely
> to uncover different issues. But using purely ad-hoc testing would
> ensure there are significant holes in test coverage.
Ad-hoc testing happens as a natural part of the development process. Also,
here the Monte Carlo method applies: more ad-hoc testing increases the
chance of covering more code.
Regards,
Edgar
--
Edgar Grimberg
System Developer
Zylin AS
Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118
http://www.zylin.com/events_embeddedworld.html
ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
Phone: (+47) 51 63 25 00
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
