blocks|key|343784|text|断言的重要之处在于被测试的实际情况。在C语言中，您可以使用预处理器“字符串化”来输出被测试的实际情况。我的代码只是输出|type|unstyled|depth|inlineStyleRanges|entityRanges|data|343785|Assert+Failed:+(4-2)==2+:+Line+123,+File+foo.c|code-block|syntax|javascript|343786|如果你幸运的话，你也可以得到一个堆叠垃圾堆.|343787|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The important thing with an assert is the actual condition being tested. In C you can use the preprocessor "stringization" to output the actual condition being tested. My code just outputs

<pre><code>Assert Failed: (4-2)==2 : Line 123, File foo.c
</code></pre>

If you're lucky, you can get a stack dump as well...

blocks|key|684039|text|我不知道是否有“标准”，但在大多数情况下，我喜欢看到断言条件本身。这是自动完成的。不幸的是，在C#中，我不得不复制粘贴它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|684040|Debug.Assert(4-2==2,+"4-2==2");|offset|length|style|CODE|684041|在某些情况下，看到比条件提供的更多的信息是有用的。在这种情况下，我将断言消息视为错误消息，并声明错误的地方。|684042|Debug.Assert(result+!=+null,+"No+result+returned+for+input+'"+%2B+input+%2B+"'");|684043|entityMap^0|0|0|V|0|0|0|25|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

I don't know if there's any "standard", but in most cases I like to see the assertion condition itself. C does this automatically. In C# I have to copy-paste it, unfortunately, eg.

<code>Debug.Assert(4-2==2, "4-2==2");</code>

In some cases it's useful to see more information than the condition provides. In that case I treat the assert message like an error message and state what's wrong, eg.

<code>Debug.Assert(result != null, "No result returned for input '" + input + "'");</code>

blocks|key|684626|text|我将断言消息视为注释:如果我能够避免，如果我能够从代码中澄清意图，我就尽量不使用它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|684627|通常，这是一个问题，当有几个属性您希望断言在某种程度上是相关的。将断言提取到一个名为“表示感兴趣的方面/关系”的方法中，可以更清楚地了解所发生的事情，而无需维护注释/消息。|684628|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I treat assertion messages like comments: I try not to have them if I can avoid it, if I can make the intent clear from the code.

Usually this is an issue when there are several attributes you want to assert on that are related in some way. Extracting the assertions into a method named to indicate the aspect/relationship you're interested in makes it more obvious what is going on without the cost of maintaining the comment/message.

blocks|key|695872|text|这真的无关紧要，只要错误信息告诉你哪里出了问题，哪里出了问题。在正常操作下，永远不会看到断言消息。如果它被发现，代码中就有一个bug，您需要能够跟踪并修复该错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|695873|该消息应该提供尽可能多的有用信息--如果您正在检查两个值是否相等，则应该打印出值是什么。这样就不需要使用调试器来检查值了。当然，这样做需要您的语言支持断言消息中的非静态信息。如果断言消息只能是固定的静态字符串，则在不跳转的情况下不能添加额外的运行时信息。|695874|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It really doesn't matter IMO, as long as the error message tells you what went wrong and where the problem is. Under normal operation, an assertion message will never be seen. If it is seen, there's a bug in the code somewhere, and you need to be able to track down and fix the bug.

The message should provide as much helpful information as possible - if you're checking that two values are equal and they're not, you should print out what the values are. That obviates the need to step into it with a debugger to examine the values. Of course, doing this requires that your language supports non-static information in assertion messages. If assertion messages can only be fixed, static strings, you can't add extra runtime information without jumping through hoops.

blocks|key|695894|text|罗迪的建议是一个很好的建议--它确实使添加新断言的“成本”变得更便宜(也就是说，不需要考虑或输入新的字符串消息)。信不信由你，但执行他的建议对我使用断言产生了重大影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|695895|不过，如果您仍在寻找更清晰的短信，您可能会考虑如下：|695896|“预期4-2等于2”|695897|这似乎表明(至少对我来说)预期的答案是2，但期望没有达到.|695898|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Roddy's suggestion is a good one--it certainly makes the "cost" of adding new assertions much cheaper (i.e. doesn't require thinking of or typing out a new string message). Believe it or not, but implementing his suggestion has had a significant impact on my usage of assertions.

If you're still looking for a clearer text message, though, you might consider something like:

"Expected 4-2 to equal 2"

This seems to make clear (at least to me) that the expected answer was 2, but that the expectation was not met...

blocks|key|684373|text|我使用断言消息来文档--断言正在测试什么，或者预期的值是什么。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|684374|有时，当测试失败时，我不需要查看失败的测试:仅仅从断言消息和我刚才所做的更改，我就知道如何修复它。|684375|entityMap^0|8|2|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I use the assertion message to document what the assertion is testing, or what the expected value is about. 

Sometimes, when a test fails, I do not need to look at the failing test : just from assertion message and the change(s) I just made, I know how to fix it.

When testing in any language, how does everybody phrase their assertion messages?

I see three obvious ways:

<pre><code># assume failure
assert (4-2) == 2, "Subtracting 2 from 4 doesn't equal 2"

# describe success
assert (4-2) == 2, "Subtracting 2 from 4 should equal 2"

# be vauge with failure
assert (4-2) == 2, "Subtracting 2 from 4 is broken"
</code></pre>

This is obviously a simple example, but you get the idea. What is the standard practice? What do you do? Why?

Assertion messages: assume failure, or assume success

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在用任何语言进行测试时，每个人如何表达他们的断言消息？我看到了三种明显的方式：# assume failureassert (4-2) == 2, "Subtracting 2 from 4 doesn't equal 2"# describe successassert (4-2) == 2, "Subtracting 2 from 4 should equal 2"# be vauge wit

问断言消息:假设失败，或假定成功
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问断言消息:假设失败，或假定成功EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问断言消息:假设失败，或假定成功
EN