RIA 开发中的测试驱动开发/集成测试
在进行 RIA 开发时，至少应该测试三个关键级别：
- RIA 应用程序类 - 在 Flash/Flex 中，可以使用 AsUnit、FlexUnit 或任何其他类似 JUnit 的解决方案进行测试
- RIA 应用程序接口 - 在 Flash/Flex 中，这可以使用 FlexMonkey RIA 完成
- 应用服务器集成 - ？
谁有经验、想法、信息、链接、书名等可以分享有关 RIA 开发工作流程的单元测试/集成测试？ 我对测试服务器集成的资源特别感兴趣。 （我在服务器端使用 PHP，在客户端使用 Flash/Flex，但任何一般性的想法将不胜感激！）
乔纳斯
When working with RIA development, there's at least three critical levels that should be tested:
- RIA application classes - in Flash/Flex these could be tested using AsUnit, FlexUnit or any other JUnit-like solution
- RIA application interface - in Flash/Flex this could be done using FlexMonkey
- RIA application server integration - ?
Anyone who has experiences, ideas, information, links, booktitles etc to share about unit testing/integration testing the RIA development workflow?
I'm especially interested in resources on testing the server integration. (I use PHP on the server side and Flash/Flex for the client, but any general thoughts would be much appreciated!)
Jonas
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不是 100% 知道你在寻找什么，但无论如何我都会尝试回答这个问题。 （写完这个答案后，我还意识到这是一篇非常旧的帖子，所以您可能已经有了答案:)）
如果您希望确保客户端与服务器正确集成，您可以使用 UI 自动化工具进行自动化端到端测试，例如Selenium（还有其他工具，我们使用 Selenium，我们对此很满意）。
实际上，我们对 UI 进行了两个级别的测试。我们有冒烟测试和验收测试。
对于这两种情况，我们将部署应用程序、设置环境并运行模拟用户在 UI 上操作的测试。
我们的冒烟测试旨在进行广度测试，但不会太深入功能。他们确保我们的应用程序安装、用户界面出现、用户可以合理地登录并在应用程序中运行。所以这基本上是为了确保应用程序没有完全损坏和无法使用。
我们的验收测试运行时间更长，而且每天只进行一次。这些更像是自动回归测试，确保我们应用程序的大部分功能按预期工作（测试的广度+深度），
我希望这能有所帮助。
I am not 100% on what you are looking for but I am going to attempt to answer this anyways. (After writing this answer I also realized this is a freaking old post, so you might already have your answer :) )
If you are looking to make sure that the client integrates with the server correctly, you can do automated end-to-end testing using a UI automation tool, like Selenium (there are others, we use Selenium and we have been happy with it).
We actually have two levels of testing for the UI. We have smoke tests and acceptance tests.
For both of these we will deploy our app, set up the environment and run tests that simulate user actions on the UI.
Our smoke tests are designed to do a breadth of testing but not going too deep into functionality. They make sure our app installs, the ui comes up, users can log in and function in the app reasonably. So this basically attempts to make sure the app is not utterly broken and unusable.
Our acceptance tests run a lot longer and only once a day. These are more like automated regression tests that make sure that most of the functionality of our app works as expected (Breadth + Depth of testing)
I hope this helps at all.