错误搜寻策略? [英] Bug Hunting Strategies?

问题描述

假设您有一个错误，该错误是在对该软件相当复杂的部分进行功能测试时发现的. 它可能来自数据库中的错误/意外数据，中间层代码或前端中的某些内容.

Let's say you have a bug that was found in functional testing of a fairly complex part of the software. It could stem from bad/unexpected data in the database, middle-tier code, or something in the front-end.

好.我们都去过那里.

您有单元测试要编写&运行，调试/记录日志语句以插入，sql语句写入&运行，您要使用FireBug检查的内容，等等.

You have unit tests to write & run, debugging/logging statements to insert, sql statements to write & run, things you want to check with FireBug, etc.

让我们说第一步是要列出您要调查的潜在原因.

Let's say the first step is come up with a list of potential causes that you want to investigate.

现在，您必须确定执行操作的顺序.

Now you have to decide what order to do things in.

您:

1. 根据直觉来按顺序调查原因?
2. 按从最快检查到最慢检查的顺序调查原因?
3. 假设该错误是特定于此功能的，并且从大多数特定于功能的代码到最少特定于功能的代码进行调查?
4. 假设这是别人的错，然后从最通用的代码一直调查到您的特定代码?
5. 还有我没提到的东西?

我觉得第一个策略是最常用的.也许是因为我不与许多初级开发人员一起工作，而更多的高级开发人员往往具有良好的直觉.或者，也许我们只是认为我们有很不错的直觉，但实际上应该使用更系统的方法.

I have a feeling the first strategy is the most often used. Maybe just because I don't work with many junior developers, and more senior developers tend to have decent intuition. Or maybe we just think we have decent intuition but should really be using a more systematic approach.

有什么想法吗?

推荐答案

我找到了橡胶鸭调试策略也很好.

这篇关于错误搜寻策略?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！