用户错误故障需要管理员干预。
在这种场景中,一个每夜都崩溃的构建可以很容易地说明,QA人员只能在第二天闲坐着,失去了宝贵的测试时间,而开发和构建团队却在寻找错误故障。
In this kind of scenario, a broken nightly build can easily mean that QA staff will sit idle the next day, losing precious testing time while the development and build teams troubleshoot the errors.
由模糊测试导致的许多故障都是内存分配错误及缓冲器溢出的直接结果。
Many of the crashes resulting from fuzz testing are direct results of memory allocation mistakes and buffer overflows.
应用推荐