This account is temporarily suspended network-wide. The suspension period ends on May 11 '24 at 18:00.
Reputation
Top tag
Next privilege 5 Rep.
Participate in meta
Badges
6
Impact
~373 people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
May
23
comment Usability versus fail-fast dilemma
Yes, I believe that such phenomenon must be known
Apr
24
comment What is so specific about reentrancy?
Can you explain how quality/code reliability ensurence issue may be not related with quality assurance? I have re-posted it in codereview.stackexchange.com/questions/25408/…
Apr
22
comment Why testing, by definition, cannot find deadlocks and stack overflows?
@KatePaulk, what do you refer by "it"?
Apr
19
comment Why testing, by definition, cannot find deadlocks and stack overflows?
I see now that CHESS is attributed to the model checkers category of verification, which particularly addresses the deadlock detection. Thanks for that reference. So Beatty now seems to exclude the whole domain of formal verification from the "testing" domain.
Apr
19
comment Why testing, by definition, cannot find deadlocks and stack overflows?
The integration tests detect worst cases at random, right? Whereas the code analysis offered is systematic. "Systematic techniques, deemed to be more comprehensive and capable to find important corner cases that would be likely to be overlooked by random techniques." (loose.upt.ro/~oose/uploads/RTSS/rtss-lecture5.pdf)
Apr
17
comment Why testing, by definition, cannot find deadlocks and stack overflows?
Isn't code review considered as a part of static testing? Is it different from formal verification? Do you define testing as something that does not detect the bugs? But let me +1 for pointing out that this was "code review"