Every time I sit down to write down my test plan, I simply feel as though I'm regurgitating my design requirements. I've been through the Mentor Coverage Cookbook a few times already; It has a UART and a couple other things. Does anyone know other good examples / explanations of test plans?
Everybody writes one of these things... right?
My example "function":
Receive an ARP request; generate an ARP reply. The destination IP of the ARP must match the DUT IP in order for DUT to generate reply.
What line item(s) would I write in my "test plan"?
ARP request received by DUT Type: covergroup, cross
ARP reply sent by DUT Type: covergroup, cross
This is where I get really wrapped around the axle. I already know what I sit down to write the test, I am going to simply randomize an ARP packet, and bombard my DUT. It will receive ARP Replies (which it should drop), ARP Request addressed to someone else (drop this as well), and occasionally a Request with the correct address (accept and reply).
I definitely want coverpoints on all the non-supported behavior as well, but I take it that's not supposed to be mentioned in the test plan anywhere? The whole point of constrained random stimulus generation is to find the bugs you aren't looking for, and it must be paired with a coverage collector to tell you where your blind sheep has wandered.