测试网络应用程序
我花了一些时间通过构建一些网络应用程序来学习 CakePHP。现在我需要测试其中一些，然后才能将它们放在公共场所。
您能给我一些关于如何模拟真实案例环境以了解哪些问题的指示吗？
I've spent some time in learning CakePHP, by building some webapps. Now I need to test some of them, before I'll put them on a public place.
Can you give me some pointers about how can I simulate a real case environment in order to know which are the problems?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
总之，我建议查看 这里。
软件 QA（测试）是一个很大的主题，它本身就是一门专业学科；除了编码之外。此外，网络质量检查也是一个完全独立的分支，（如果做得好的话）需要了解互联网和浏览器技术的某些技术方面的经验，特别是与安全相关的内容——这似乎是您关心的问题之一。作为曾经从事 QA 工作并开发测试自动化的人，询问更具体的问题也可能会给您带来最有用的答案。
为了给出部分答案，我将阐述单元测试的想法。这就像程序员通过使用“线束”一次测试一个软件的方法。作为粉丝，Cake 最好的一点是“框架”概念确实使这种测试成为可能，并且 相对简单。正如该页面中提到的，其想法是，当从测试模式（在线束内）执行脚本时，固定装置允许您定义源自测试连接的示例数据。
总之，我想详细阐述框架思想以及它如何在软件开发中发挥作用。真正的问题是，好的软件需要使用一套方法来开发/构建，使其需要最少的维护，同时最大限度地提高可重用性。建议采用自上而下的分层开发方法，以便每个层或级别都可测试的。 MVC（Cake 主要实现）是一个代码如何分离以及每个区域如何独立测试的模型，表面上允许人们得出系统作为一个整体功能正常、安全等的结论。然而，最终，黑盒，仍然需要外层用户体验测试来评估事物如何协同工作。优秀的开发人员并不经常成为优秀的测试人员（或希望成为），除此之外，让尽可能多的其他人关注您的软件也是一个好主意。因此，如果您计划发布人们想要继续使用的优质产品，那么一定要在发布周期中留出大量测试时间。
In summary, I recommend looking HERE.
Software QA (testing) is a big subject, and a professional discipline in it's own right; apart from coding. Furthermore, web QA is also a whole separate branch that (when done well) requires experience with understanding some technical aspects of Internet and browser technologies, especially as it relates to security -- which appears to be one of your concerns. As someone who used to work in QA, and worked with developing test automation, asking about a more specific issue might also get you an optimally useful answer.
To throw out a partial answer, I'll address the idea of unit testing. This is like the programmer approach to testing one piece of software at a time through the use of a "harness". As a fan, the nicest thing about Cake is the "framework" concept does make this kind of testing possible and relatively simple. As mentioned from that page, the idea is that fixtures allow you to define sample data sourced from a test connection when executing the script from test mode (within the harness).
In conclusion, I'd like to elaborate more about the framework idea and how it plays into software development. The real issue is that good software needs to be developed/architected with a set of methodologies that allow it to be require minimal maintenance, while maximizing reusability. The top-down, tiered development approach is advisable so that each tier or level is testable. MVC (which Cake mostly implements) is a model for how code can be separated and each area can be tested independently, ostensibly allowing one to conclude that the system as a whole is functional, secure, etc. However, final, black-box, outer-level, user-expereince testing is still required to assess how things work together. It isn't often that good developers make good testers (or want to be), besides which it's a great idea to enlist as many other sets of eyes as possible on your software. So, definitely allow lots of testing time into your release cycles if you plan on releasing a quality product that people will want to keep using.
您可以尝试使用 Selenium 来模拟用户通过浏览器与您的应用程序交互。
You can try using Selenium to simulate a user interacting with your app through the browser.