Hi, How can I draw the line between positive and negative testing? Do you have any resources to read and to look at? how the env would change from positive to negative? what sort of checkers one needs? thanks
In reply to Ed Ham:
Drawing the line between positive and negative testing is very easy if you have a specification of design requirements. Positive testing tests that the design does what the document says it should do. Negative testing tests that a design can handle stimulus that is outside the requirements and recover in a graceful way. There are many resources on the internet regarding this topic, especially for software design. Negative testing in software usually involves a human being erroneously providing stimulus that is outside the specification. That stimulus space could be boundless. But there has to be be some practical restrictions on what is physically possible or some set of assumptions as what could be provided as stimulus to make the problem manageable. This is probably more true with hardware design than software.
In practical terms, negative testing can be thought of finding what is missing the design spec, getting the spec updated, and turning those tests into the positive.
In reply to dave_59:
Hi Dave, thanks for the answer and the clarifications. I actually couldn’t find much on the web…maybe you know of a particular resource related to software development tools.
Hi Dave ,
Can you explain few negative testing scenarios by taking example of memory / fifo/ any block?
In reply to Kishankk:
Write to a memory address that does not exist. If you are supposed to an error response, that is a positive test. If not, does the spec say anything about what is supposed to happen? Does it truncate the upper address bits at still do a write?