blocks|key|5225281|text|测试驱动开发(+TDD+)及其扩展表亲、接受TDD+(ATDD)和行为驱动开发(BDD)是Java生态系统中作为测试人员学习的有用技术。在您寻找白盒测试时，我将重点关注TDD。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5225282|什么是TDD？-本质上是编写一个失败的测试(红色)，通过编写一个实现(绿色)，然后再重构来通过测试。维基百科文章是一个足够开始了解更多信息的地方。但是这个话题很广泛，我建议大家在这个领域里读一些著名的书，比如测试驱动开发和有效地使用遗留代码。我还将为基础良好的Java开发人员中的TDD章节添加一个无耻的插件|offset|length|5225283|在Java生态系统中，这意味着您想学习：|5225284|JUnit库和/或TestNG库。|ordered-list-item|5225285|模拟库，如莫基托或JMock|5225286|攻击代码的负载测试工具-+JMeter|5225287|依赖注入+(一种控制反转形式)的概念|5225288|然后练习练习。优秀的Java白盒测试人员非常罕见，最好的测试人员都编写了针对范围广泛的代码库的测试。|5225289|让你开始吧！|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Test-driven_development|1|http://rads.stackoverflow.com/amzn/click/0321146530|2|http://rads.stackoverflow.com/amzn/click/0131177052|3|http://www.java7developer.com/|4|http://www.junit.org/|5|http://testng.org/doc/index.html|6|http://code.google.com/p/mockito/|7|http://www.jmock.org/|8|http://jakarta.apache.org/jmeter/|9|http://martinfowler.com/articles/injection.html^0|0|1E|6|0|2W|6|1|33|9|2|3H|D|3|0|0|0|5|4|9|6|5|0|5|3|6|9|5|7|0|D|6|8|0|0|4|9|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]|$D|1O|E|1P|1|1Q]|$D|1R|E|1S|1|1T]|$D|1U|E|1V|1|1W]]|A|$]]|$1|F|3|G|5|6|7|1X|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1Y|8|@]|9|@$D|1Z|E|20|1|21]|$D|22|E|23|1|24]]|A|$]]|$1|K|3|L|5|J|7|25|8|@]|9|@$D|26|E|27|1|28]|$D|29|E|2A|1|2B]]|A|$]]|$1|M|3|N|5|J|7|2C|8|@]|9|@$D|2D|E|2E|1|2F]]|A|$]]|$1|O|3|P|5|J|7|2G|8|@]|9|@$D|2H|E|2I|1|2J]]|A|$]]|$1|Q|3|R|5|6|7|2K|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2L|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]|13|$5|W|X|Y|A|$Z|14]]|15|$5|W|X|Y|A|$Z|16]]|17|$5|W|X|Y|A|$Z|18]]|19|$5|W|X|Y|A|$Z|1A]]|1B|$5|W|X|Y|A|$Z|1C]]|1D|$5|W|X|Y|A|$Z|1E]]|1F|$5|W|X|Y|A|$Z|1G]]|1H|$5|W|X|Y|A|$Z|1I]]]]

Test Driven Development (TDD) and it's extended cousins, Acceptance TDD (ATDD) and Behaviour Driven Development (BDD) are useful techniques to learn as a tester in the Java ecosystem. I'll focus on TDD as you're looking for white box testing.

What is TDD? - At it's heart it's the practice of writing a failing test (red), making that test pass by writing an implementation (green) and then re-factoring. The <a href="http://en.wikipedia.org/wiki/Test-driven_development">Wikipedia Article</a> is a sufficient place to start to find out further information. But the topic is vast, I recommend reading some of the well-known books in this space such as <a href="http://rads.stackoverflow.com/amzn/click/0321146530">Test Driven Development by Example</a> and <a href="http://rads.stackoverflow.com/amzn/click/0131177052">Working effectively with legacy code</a>. I'll also throw in a shameless plug for the TDD chapter in <a href="http://www.java7developer.com/">The Well-Grounded Java Developer</a>

In the Java ecosystem, this means you want to learn:

<ol>
<li>The <a href="http://www.junit.org/">JUnit</a> library and/or the <a href="http://testng.org/doc/index.html">TestNG</a> library.</li>
<li>A mocking library such as <a href="http://code.google.com/p/mockito/">Mockito</a> or <a href="http://www.jmock.org/">JMock</a></li>
<li>A load testing tool to attack the code - <a href="http://jakarta.apache.org/jmeter/">JMeter</a></li>
<li>The concept of <a href="http://martinfowler.com/articles/injection.html">Dependency Injection</a> (a form of Inversion of Control)</li>
</ol>

And then practice, practice, practice, practice. Good Java white box testers are very rare, the best have written tests against a wide range of code bases.

HTH's get you started!

blocks|key|5224999|text|Junit是Java编程语言的最佳单元测试框架之一。它是一个开源框架，可以编写和运行可重复的测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Junit is one of the best unit testing framework for the Java programming language. Its an open source framework to write and run repeatable tests.

blocks|key|5225064|text|我通常不喜欢引用维基百科，但这篇文章的信息似乎足够安全.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5225065|http://en.wikipedia.org/wiki/Test-driven_开发|offset|length|5225066|从本质上讲，这是一种测试优先的软件开发方法，单元测试首先是为用例设计和编写的，然后才是硬开发，以帮助那些单元测试通过。|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Test-driven_development^0|0|0|17|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]]]

I normally don't like to quote Wikipedia but the information on this article seems safe enough...

<a href="http://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow">http://en.wikipedia.org/wiki/Test-driven_development</a>

Essentially in lay terms it is a Test-First approach to software development were unit tests are designed and written to use cases first, then hard development occurs afterwards to help make those unit tests pass.

blocks|key|1490171|text|我不确定我的建议是否会被视为白盒测试的工具，但您也可以查看数据库驱动项目的dbUnit和web测试的硒+(例如，根据某些结果检查应该存在的元素)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dbunit.org/|1|http://seleniumhq.org/^0|11|6|0|1E|1|1^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]|$A|Q|B|R|1|S]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]|K|$5|F|G|H|C|$I|L]]]]

I am not sure if my suggestion will be considered as tools for white box testing but you can also look at <a href="http://www.dbunit.org/" rel="nofollow">dbUnit</a> for database-driven projects and <a href="http://seleniumhq.org/" rel="nofollow">Selenium</a> for web testing(e.g. inspection of elements that should be existing based on some results).

blocks|key|1490316|text|这个问题特别提到“白盒测试”。在这里，您的测试对代码的内部结构有很好的了解，并在每个步骤中断言行为，而不仅仅是输入/输出/副作用(黑匣子测试)。虽然JUnit在这两方面都做得很好，但是您需要更多的框架才能在单元测试的上下文中做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1490317|EasyMock和JMock是很好的框架。我倾向于喜欢JMock。|offset|length|1490318|冒着引发OT争论的风险，您应该仔细考虑白盒测试的含义。白盒测试与代码密切相关(很明显)，如果不小心使用，模拟框架可能会导致测试相当复杂、难以阅读，并且在重构时会变得更加脆弱。|1490319|我倾向于两者兼而有之。只要有可能，黑匣子测试就会出现，而白盒测试只适用于风险更高/更复杂的代码。|1490320|当然，上面列出的框架也可以用于黑匣子测试，在这些测试中，贡献类(注入)的数量很大，而且简单的固执变得难以使用。|1490321|关于TDD+-它主要是一种设计增强的方法来编写代码，而不仅仅是一种编写测试的方法。最后的测试是一个重要的输出，但是这种方法的目的是增强应用程序的设计和结构。|entityMap|0|LINK|mutability|MUTABLE|url|http://easymock.org/|1|http://www.jmock.org/^0|0|0|8|0|9|5|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]|$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|17|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]]]

The question specifically makes reference to "white box testing". This is where your tests have intimate knowledge of the internal structure of your code and assert behaviour at each step rather than just the input/output/side effect(black box testing). Whilst JUnit is excellent to do both, you need further additional frameworks in order to do this within the context of a unit test. 

<a href="http://easymock.org/" rel="nofollow">EasyMock</a> and <a href="http://www.jmock.org/" rel="nofollow">JMock</a> are good frameworks to do this. I tend to favour JMock.

At the risk of starting a OT debate, you should think carefully about the implications of white box testing. White box tests are intimately tied to your code (obviously), and if not used carefully, mocking frameworks can cause your tests to be rather complicated, difficult to read and tend to be more brittle when refactoring. 

I tend to stick to a mix of both. Black box tests wherever possible, and white box tests sparingly applied to riskier/more complicated code. 

Of course the frameworks listed above can also be used in black box tests where the number of contributing (injected) classes is large and simple stubbing becomes unwieldly.

Regarding TDD - it's primarily a design enhancing approach to writing code, rather than simply a way of writing tests. The tests you have at the end are an important output, but moreover the approach is intended to enhance the design and stucture of your application.

I am an entry level Java Programmer straight out of school.
I have good knowledge and experience with J2SE.
Can anyone advise me on how to improve or tune my skills towards being a Java white box tester? Wide range of inputs are welcome.

And what is Test Driven Development?

Test-driven development and improving white box testing skills

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我是一个入门级的Java程序员，刚从学校毕业。我对J2SE有很好的知识和经验。有人能建议我如何提高或调整我的技能，使我成为一个Java白盒测试人员吗？欢迎广泛的投入。什么是测试驱动的开发？

问测试驱动开发和提高白盒测试技能
EN

回答 5

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试驱动开发和提高白盒测试技能EN

回答 5

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试驱动开发和提高白盒测试技能
EN