我应该继续注册失败吗？ [英] Should I Keep Registering A Failure?

问题描述

我正在为一个我所维护的应用程序自动化回归测试套件。在开发自动化回归测试时，我遇到了几乎肯定是一个错误的行为。所以，现在，我修改了自动化回归测试，没有注册失败 - 这是故意允许这个坏的行为，我的意思是。

I'm working on an automated regression test suite for an app which I maintain. While developing the automated regression test, I ran across some behavior that's almost certainly a bug. So, for now, I've modified the automated regression test to not register a failure--it's deliberately allowing this bad behavior to go by, I mean.

所以，我对本网站上的其他人的意见感兴趣。显然，我会在缺陷跟踪中添加一个错误，以确保此错误行为得到修复。但是，有没有任何令人信服的原因（无论哪种方式）改变回归测试，以不断地指示失败或者使回归测试失败，并且没有失败，直到我们能够修复有缺陷的行为？我认为这是一个六分之一的其他类型的问题，但我问这里，因为我认为其他人可能看到不同。

So, I am interested in the opinions of others on this site. Obviously, I'll add a bug to our defect tracking to make sure this error behavior gets fixed. But are there any compelling reasons (either way) to either change the regression test to constantly indicate failure or leave the regression test broken and not have a failure until we can get to fixing the defective behavior? I think of this as a 6 of one and a half-dozen of the other type of question but I ask here because I thought others may see it differently.

@Paul Tomblin，

@Paul Tomblin,

只是要清楚 - 我从来没有考虑删除测试;我只是考虑修改通过/失败条件，以便在每次运行测试时都不会在我的脸上抛出故障。

Just to be clear--I've never considered removing the test; I was simply considering modifying the pass/fail condition to allow for the failure without it being thrown up in my face every time I run the test.

我有点担心已知原因的重复故障最终会像C ++中的警告一样被对待。我知道在C ++代码中看到警告的开发人员，只是忽略它们，因为他们认为它们是无用的噪音。恐怕在回归套件中留下已知的失败可能会导致人们开始忽视其他可能更重要的失败。

I'm a little concerned about repeated failures from known causes eventually getting treated like warnings in C++. I know developers who see warnings in their C++ code and simply ignore them because they think they're just useless noise. I'm afraid leaving a known failure in the regression suite might cause people to start ignoring other, possibly more important, failures.

BTW，以免被误解，我认为C ++中的警告是制定强大代码的重要辅助工具，但从其他C ++开发人员的角度来看，我认为我'

BTW, lest I be misunderstood, I consider warnings in C++ to be an important aid in crafting strong code but judging from other C++ developers I've met I think I'm in the minority.

推荐答案

我会说地狱是啊！简单的事实是，它是否失败？是!然后应该记录。通过允许失败的测试通过，您几乎完全损害了您的测试。

I would say "hell yeah!". The simple fact is, is it failing? Yes! Then it should be logged. You are pretty much compromising your testing by allowing a failed test to pass.

有一件与我个人有关的事情是，如果我这样做，并在公共汽车，那么补丁可能不会被删除，这意味着即使在错误修复错误可能仍然存在之后。

One thing that would concern me personally, is that if I did this, and went under a bus, then the "patch" may not get removed, meaning even after a "bugfix" the bug may still remain.

保留，更新您的项目说明，甚至可能将严重性降低（如果可能），但肯定不要打破那些检查破碎的东西的东西;）

Leave it in, update your project notes, perhaps even move the severity down (if possible), but certainly dont break the thing that is checking for broken things ;)

这篇关于我应该继续注册失败吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！