Total Posts: 39
Joined: Dec 2009
|
It's said that assertions are useful, but hard to write. Do you agree? Does that stop you from using them? We covered some attempts to make assertions easier to use this week; do they address your issues?
Posted on 2010-06-29 17:56:57 at 2010-06-29 17:56:57
|
Total Posts: 8
Joined: Feb 2010
|
Comment on the car driver example
The example of the car driver shows that before coding assertion verification, you must have a specification that describes the expected behavior. All the assertions made after that should be based on the requirements of the specification.
When coding assertion, you also should keep in mind: "how would I do manual verification for this case ?". When you are watching waveforms on simulations, you instinctively filter the cases that you don't have to check. For the car, imagine you are a policeman that verify the behavior of the driver. If there is a sun reflexion in the glass, may be you can't distinguish the driver's hands. During this time, you have to accept that no verification is possible.
To verify the driver behavior, I would do:
- detection if driver's hands are not on the wheel (only if there is no sun reflexion)
- capture of the movement realized by the driver
- check if the movement is authorized in the list au authorized movement written in the specification
- give the result
Posted on 2010-07-01 06:01:47 at 2010-07-01 06:01:47
|
