PC + 组合的自动化系统测试方法 嵌入式软件
该系统由硬件设备和PC机组成。 PC 运行控制硬件设备的 GUI。 为了测试设备，使用了可由 RS232 或 GPIB 控制的各种测试硬件。 为了自动执行此测试，测试软件必须控制测试硬件并与 PC GUI 交互。
您所知道的自动测试该系统的最佳方法是什么？
有很多方法可以测试这样的系统。 测试可以通过 COTS 测试软件或内部内置的定制测试软件进行控制。 COTS 包的组合可能是最好的方法 - 一个专门用于 GUI 测试，另一个用于设备。 我见过 Labview 应用于测试设备 - 不确定它是否也可以做 GUI。 也许放弃 Windows 应用程序的 GUI 层并公开自动化层是最好的方法。 你怎么认为？ 你尝试过什么？
投票选出更好的技术应该很有趣。
“最好的方法”必须考虑以下因素：最有效、可维护性、实施时间、成本等。
The system consists of a hardware device and a PC. The PC runs a GUI that controls the hardware device. To test the device various test hardware is used that can be controlled by RS232 or GPIB. To automate this testing the test software would have to control the test hardware and interact with the PC GUI.
What is the best way you know of to automate the testing of this system?
There are lots of ways to test a system like this. The tests can be controlled by COTS test software or by a custom test software built in house. Possibly a combination of COTS packages would be the best approach - one that specializes in GUI testing and one for the device. I've seen Labview applied to testing devices - not sure if it can do GUIs too. Maybe leaving off the GUI layer of the Windows app and exposing an automation layer is the best approach. What do you think? What have you tried?
Voting up the better techniques should be very interesting.
"the best way" would have to take into account things like: most effective, maintainability, implementation time, cost, etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在这种具有多个单独组件的情况下，几乎可以肯定最好首先单独测试每个组件，然后测试集成的整体。
因此，创建用于测试的框架和测试：
Windows 图形用户界面
自动化层。
硬件设备。
虽然大多数组件都可以在无限的预算和无限的时间下实现自动化，但测试关键组件并让人员测试其余组件通常更值得。
用户显然有能力破坏任何东西，所以一旦你解决了大部分问题就让他们参与进来。 这也意味着您会得到宝贵的反馈。
最后...仅在硬件/软件中存在错误可以接受的情况下才使用此方法。
例如，如果您正在编写飞机控制软件，我不会推荐这种方法......
In situations like this with multiple seperate components it's almost certainly best to test each component in isolation first, and then test the integrated whole.
So create frameworks and tests for testing:
The Windows GUI
The automation layer.
The hardware device.
While automation can be achieved for most components with an unlimited budget, and an unlimited amount of time, it's often more worthwhile to test the key components, and use people to test the rest.
Users are obviously capable of breaking anything, so involve them once you've ironed out the majority of the issues. This will also mean you get valuable feedback.
Finally... only use this approach if having bugs in the hardware/software is acceptable.
I wouldn't recommend this approach if you're writing aeroplane control software for example...