Post a reply
Note:If not registered, provide any username. For more comfort, register here.
Message body:
Enter your message here, it may contain no more than 60000 characters. 

:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
Font size:
Font colour
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation of post
To prevent automated posts the board requires you to enter a confirmation code. The code is displayed in the image you should see below. If you are visually impaired or cannot otherwise read this code please contact the %sBoard Administrator%s.
Confirmation code:
Enter the code exactly as it appears. All letters are case insensitive, there is no zero.

Topic review - howto discover bugs
Author Message
  Post subject:  howto discover bugs  Reply with quote

during last months using random input 21 bugs were discovered in 'libfactory'. 20 of them were fixed( by Martin Lee and Hans Schoenemann).
Statistic data from other software projects/studies suggests that there are more undiscovered bugs,
but how to detect them?

The random testing method from above has its issues:
- meanwhile a lot of examples are required to discover the next bug
- the input examples may be not random enough or do not cover interesting use cases.

It is known and I can confirm from own experience that applying different test methods
will not detect the same set of defects, so testing methods may used complementary.

following additional methods could be applied (to factory)
- code review (AFAIK was not done for 'libfactory') The expected cost is about an hour for 100-200 loc for a reviewer who is familiar with 'libfactory'
- writing tests for every routine (not only for the interfaces) using a framework like googletest
- others?

Post Posted: Tue Nov 25, 2014 9:51 pm

It is currently Tue Nov 20, 2018 2:30 pm
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group