软件测试自动化 - 硕士论文
我正在尝试写一篇关于软件测试自动化的论文。 我计划比较测试脚本的记录和编程的两种方法，并讨论几种自动化框架，例如 Abbot、Selenium、Yemmy、FEST 等......在我的论文中还将简要概述软件测试技术和也许是自动化测试与软件测试的比较。
编辑：我计划在应用程序的 GUI 上测试应用程序的各个方面。 所以我的测试主要是在测试世界的黑盒一侧。 我本来没有打算写单元测试。
目前，我阅读了很多有关不同自动化框架的内容，但我可能没有时间回顾所有这些框架。 因此，我计划阅读有关它们的内容，并使论文更加以文献为基础。
- 您认为这个专题能成功吗？
- 您对这个主题还有其他想法吗？
- 可以推荐一下文学吗？
- 您对此主题有何看法？
i am trying to write a thesis about Software Test Automation. I plan to compare the two Approaches of Recording and Programming of Test Scripts, and to discuss about several Automation Frameworks, for example Abbot, Selenium, Yemmy, FEST, etc ... Also in my Thesis will be a short overview about Softwaretesting Techniques and maybe a comparison of automated testing to software testing.
EDIT: I am planning to the aspects of testing an Application over it's GUI. So my Tests would be mostly on the Blackbox Side of the testing world. I have not planned to write about Unit Testing.
At the Moment i read pretty much about the different Automation Frameworks, but i may not have the time to review all of them. So i plan to read about them and make the Thesis more literature - based.
- Do you think this Topic could be successful?
- Do you have any other Ideas concerning this Topic?
- Can you reccommend Literature?
- What is your Opinion about this Topic?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
文献调查应该是硕士学位论文的重点。 听起来您只想谈论黑盒 GUI 驱动的面向客户的工具，这是一个相当小的利基市场。
正如上面有人提到的，您/可能/想要用一两页的时间来了解整个测试工具的世界——单元测试、安全性、负载等。 但我认为你很好地定位了你的利基市场。
我认为通过 6 学分的论文，您应该有足够的时间来探索和尝试一些更大的商业和开源工具以及调查文献。 我鼓励您研究商业工具（快速测试专业版、测试完成）以及关键字驱动的自动化 - 例如 selenium RC。 其他人提到“GUI 背后”的测试，例如 FIT/Fitnesse，可能值得讨论和评估。
我在《软件测试和性能》杂志 2008 年 12 月号的每月专栏中介绍了黑盒功能测试自动化：
http://www.stpmag.com/issues/stp-2008-12.pdf（第 7 页）
这是一页粗略的介绍。 五句话的介绍是屏幕记录/回放工具会比较所有内容，因此如果您的 GUI 发生任何变化（即使您只是更改屏幕分辨率），都可能会作为错误错误返回。 关键字驱动的工具仅检查您告诉他们要检查的内容 - 如果按钮无缘无故突然禁用或图标不透明，它们会错过。
只有人类擅长检查每个测试用例末尾的隐藏断言“......并且没有发生其他奇怪的事情。”
因此，基于计算机的测试执行和评估可能具有一定的价值，但它应该成为均衡早餐的一部分。
其他值得关注的事情：
http://xndev.blogspot.com/2007/09/whats-test -framework.html （这是“什么是测试框架”的第 4 号谷歌结果，所以我很乐意推荐它）
http://www.softwarequalitymethods.com/H-Papers.html
我希望有所帮助。
A survey of the literature should be a fine focus for a MS thesis. It sounds like you want to just talk about black-box GUI-driving customer-facing tools, which is a reasonably small niche.
You /might/ want to have a page or two on the whole world of test tools - unit testing, security, load, etc, as someone mentioned above. But I think you targeted your niche pretty well.
I would think with a 6-credit thesis you should have plenty of time to explore and try out some of the bigger commercial and open-source tools as well as survey the literature. I would encourage you to look into both commerical tools (quick test pro, test complete) and also keyword-driven automation - selenium RC, for example. Someone else mentioned testing "behind the GUI" eg FIT/Fitnesse, it might be worth discussing and evaluating.
I cover black-box, functional test automation in my monthly column in the December 2008 issue of software test and performance magazine:
http://www.stpmag.com/issues/stp-2008-12.pdf (page 7)
That's the one page scratch-the-surface introduction. The five-sentence introduction is that screen record/playback tools compare everything, so if your GUI changes at all, in any way (even if you just change the screen resolution) that can come back as a false error. Keyword-driven tools only check what you tell them to check - they miss if a button is suddenly disabled for no good reason or an icon is not transparent.
Only a human is good at checking that hidden assertion at the end of every test case "... and nothing else strange happened."
So computer-based test execution and evaluation can have some value, but it should be part of a balanced breakfast.
Other things to look into:
http://xndev.blogspot.com/2007/09/whats-test-framework.html (it's the number 4 google result for "what is a test framework", so I'm comfortable recommending it)
http://www.softwarequalitymethods.com/H-Papers.html
I hope that helps.
软件测试自动化是一个大主题，您可能希望缩小您的关注范围，而不是尝试涵盖框架、回放/记录、技术概述、自动化与非自动化的组合。
关于软件测试自动化的整本书都有：
框架针对不同类型的测试：
我会考虑关注框架（或技术，或其他）只选择其中一个领域，而不是试图涵盖所有领域。 或者选择其中几个区域并进行对比。
播放/记录与手写测试的问题对我来说似乎很老了。 在 1980 年代，供应商喜欢推动 Windows GUI 自动化播放/录制。 它带来了很棒的演示和厚望。 但它也适用于脆性测试和货架。 播放/记录对于帮助您开始使用工具很有帮助，但为了可维护，您通常需要以更高级别编写脚本。 这开创了电子表格和基于关键字的方法的新时代，并最终迎来了 FIT/FitNesse。
Software Test Automation is a big topic, and you may want to narrow your focus rather than attempt to cover a mix of frameworks, playback/record, overview of techniques, automated vs. not.
Entire books have been written about software test automation:
Frameworks are aimed at different types of testing:
I would consider focusing on frameworks (or techniques, or whatever) in one of these areas rather than trying to cover them all. Or pick a couple of these areas and contrast them.
The issue of playback/record vs. handwritten tests seems old to me. In the 1980's vendors liked to push playback/record for Windows GUI automation. It made for great demos and high hopes. But it also made for brittle tests and shelfware. Playback/record is nice to get you started with a tool, but to be maintainable, you generally need scripts written at a higher level. That ushered in a new era of spreadsheet and keyword-based approaches, and eventually FIT/FitNesse.
我不懂文学，但我想你们学校图书馆的ACM出版物可能会产生结果。 特别是 SIG* 新闻通讯。 （也许 SIGSOFT？）
对我来说，这听起来确实是一篇很好的硕士论文。 当然，你的论文导师是最终决定者。 你应该去和他们谈谈。
I don't know about literature, but I think the ACM publications in your school library would probably produce results. Particularly the SIG* newsletters. (Perhaps SIGSOFT?)
It does sound like a good Master's thesis to me. Of course your thesis advisor is the final word on that. You should go talk to them.
作为一篇基于文献的评论，这是一个很好的话题； 那里有很多材料。 显然，我不会开始讨论所有细节，因为这是作者的工作。 :-)
然而，虽然我不熟悉硕士论文的原始研究要求，但这对于博士论文来说肯定是不够的。 我会寻找您可以添加到此的原创作品。 一个想法是测试方法和系统的分类。 您还可以检查测试与正式验证相比的作用。
As a literature-based review, this makes an excellent topic; there's plenty of material out there. Obviously I'm not going to start to get into all the details of that, since that's your job as the author. :-)
However, though I'm not familiar with the original research requirements for a master's thesis, this certainly wouldn't be enough for a PhD thesis. I would look for original work you could add to this. One idea would be a taxonomy of testing methods and systems. You might also examine the role of testing as compared to formal verification.
如果这篇论文可以在网上找到，我有兴趣阅读。 值得考虑以编程方式访问 GUI - Web 和应用程序。 然后还有像 Selenium 或 WatiR 这样的录制和播放工具。 当然，自动化的优点和缺点 - 工具的局限性（例如，大多数人无法了解 Java 小程序或网页上的 Flash）以及一些人在自动化时忘记的最重要的事情 - 并非所有事情都应该如此em> 自动化！
但如果您有可能对此发表评论，以便在完成后通知我们，我真的很想阅读。
I'd be interested in reading the thesis if it's available online. Worth considering programmatic access to GUI - both web and application. Then there's record and playback tools like Selenium or WatiR. And of course the pros and cons of automation - limitations of the tools (most can't see into java applets or flash on webpages, for example) and the most important thing some people forget when automating - NOT everything should be automated!
But if at all possible for you to comment on this to notify us when it's done, I'd genuinely like a read.
今年刚刚出版了一本关于测试自动化的优秀书籍：《实施自动化测试》，Elfriede Dustin、Thom Garrett & 伯尼·高夫，艾迪生·韦斯利。
An excellent book on test automation has just been published this year: “Implementing Automated Testing”, Elfriede Dustin, Thom Garrett & Bernie Gauf, Addison Wesley.