什么是红盒、黄盒、绿盒测试？
我可以找到很多关于黑盒测试和白盒测试之间差异的解释，但找不到关于红盒、黄盒和绿盒测试更好的解释。
有人可以解释一下这些类型的测试术语吗？示例将不胜感激。
提前致谢。
I can find many explanations on difference between black box and white box testing, but couldn't find any better explanation on Red box, Yellow box and Green box testing.
Can someone please explain these types of testing terms? Examples will be appreciated.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
软件测试中有不同颜色的测试和技术：
黑盒 = 以下技术：
黄匣子 = 验收测试
There are different colors of testing and techniques in Software Testing:
Black Box = The following techniques:
Yellow Box = Acceptance testing
红盒测试是用户验收测试。
黄盒测试是测试警告或警报消息。
Red box testing is User Acceptance Testing.
Yellow Box testing is to test the Warning or Alert messages.
Google 提供了一种结果，多种替代方案
http://www.testrepublic .com/forum/topics/define-red-box-testing-yellow
Google has one result, several alternatives
http://www.testrepublic.com/forum/topics/define-red-box-testing-yellow
这是由客户或最终用户完成的测试，他们将在一段时间内将软件用于实时业务场景，并检查软件处理实时业务工作流程的能力
It is a testing done by the customer or end-user wherein they will use the software for real time business scenario for some period of time and check how well the software can handle the real time business work flow
令我惊讶的是，尽管这是一个老问题，但没有人发布有意义的答案。
所以这就是：没关系。正如您从矛盾的答案中看到的，这些不同颜色的测试术语没有普遍接受的定义。但也没有必要。虽然命名不同的测试类别有助于描述您正在进行的测试，但也有可能过度关注分类而不是真正重要的内容 - 实际上测试。
以更常见的“白”和“黑”框类别为例，在测试过程中是否查看源代码到底有多重要？也许您开始做所谓的“黑匣子”，但您最初的测试激发了想法和问题，使查看代码听起来像是一个好主意。这是否意味着您现在正在进行“白盒”测试（或者更有趣的是“灰盒”）？
谁知道，但谁在乎呢？只要您发现威胁产品价值的问题，就可以将其命名为在您的环境中有用或令人难忘的任何名称。
I'm amazed that even though this is an old question, nobody has posted an answer that makes sense.
So here it is: it doesn't matter. As you can see from the contradictory answers, there is no generally accepted definition of these different-colored testing terms. But there also doesn't need to be. While naming different categories of testing can be helpful for describing the testing you're doing, it's also possible to overly fixate on categorization instead of what actually matters--actually testing.
To use the more commonly recognized "white" and "black" box categories as an example, how much does it really matter if you do or don't look at the source code as part of doing your testing? Maybe you start out doing what would be called "black box", but your initial testing sparks ideas and questions that make looking at the code sound like a good idea. Does that mean you're now doing "white box" testing (or even more amusingly, "grey box")?
Who knows, but also, who cares? As long as you're finding problems that threaten the value of the product, call it whatever is helpful or memorable in your context.
验收测试，通常称为红盒测试。
简单的黄盒测试就是检查警告
消息。系统正确抛出警告消息
或不？
Acceptance testing, often referred to as Red-Box testing.
Simply yellow box testing is checking against the warning
messages. The system properly throwing the warning messages
or not?
红盒测试：也称为验收测试。用户/客户应用黑盒测试、白盒测试和灰盒测试等技术来接受项目。
黄盒测试：检查警告消息，判断系统是否抛出警告消息。
绿盒短信：从测试目标的外部角度导出测试用例。
Red Box Testing: Also referred as acceptance testing. in which user/client apply any technique like black box testing, white box testing and gray box testing to accept the project.
Yellow Box Testing: check against warning messages that weather the system throws the warning messages or not.
Green Box Texting: takes the external perspective of the test objective to derive the test cases.
根据我的经验，我发现：
红盒测试：当您在红色区域测试应用程序/产品时称为红盒测试。
黄盒测试：当您在黄色花园区域测试应用程序/产品时称为红盒测试。
绿盒测试：前盒测试和后盒测试的组合称为绿盒测试。
As per my experience, I found:
Red Box Testing: When you are testing the application/product in Red area is known as Red Box Testing.
Yellow Box Testing: When you are testing the application/product in Yellow garden area is known as Red Box Testing.
Green Box Testing: The combination of front box testing and back box testing is known as Green Box testing.