Winium.Desktop是否需要甚至在开发后也要运行? [英] Is Winium.Desktop required to be running even post development?
问题描述
我是Winium世界的新手.我尝试与 Winium.Cruciatus 一起玩，这似乎工作正常，但并不完美. 因此，我正在考虑尝试理解的 Winium.Desktop.Driver.exe -
I am new to the Winium world. I tried playing with Winium.Cruciatus which seems to be working fine but not perfect. Hence, I am thinking to try Winium.Desktop.Driver.exe which I understand -
-
是Cruciatus的硒兼容包装，并且
is a Selenium-compatible wrapper for Cruciatus, and
开发时需要单独运行.
但是，我想了解一下，一旦开发完成， 如果该解决方案已在生产中部署，它将 ( Winium.Desktop.Driver.exe )仍需要预先运行 寻求解决方案?
However, I wanted to understand that once the development is done and if the solution is deployed in production, will it (Winium.Desktop.Driver.exe) still be required to be running in advance for the solution to work?
我的要求: 要从一个虚拟机上自动在多个虚拟机(已加入域)上安装软件.
My requirement: To automate the installation of a software on multiple VMs (domain joined) from one single VM.
如果(是)
{
- 我认为如果需要显式管理员，它可能会阻止安装 允许运行.由于我们无法在每台计算机上都单击是"， 这违反了自动化的目的.
- 因为我的环境将是Windows Server 2012 R2，并且大多数 它们比Win10等普通Windows受到更多限制的时间.
- I think it may block the installation if it requires explicit Admin permission to run. As we cannot go on each machine to click on 'Yes', which defeats the purpose of automation.
- Because my environments will be Windows Server 2012 R2 and most of the time they are more restricted than a normal Windows like Win10.
}
如果(否)
{
与仅使用 Cruciatus 库进行开发相比，使用 Winium.Desktop.Driver 有什么特别的优势?
Any specific advantage of using Winium.Desktop.Driver vs only developing with Cruciatus library?
}
注意:信誉良好的人可以创建一个新标签- 'Winium' ，因为我们现在已经需要它了还有其他问题 在Winium上.
Note: Can someone of high reputation please create a new tag - 'Winium' as it seems this is required now as we already have few more questions on Winium.
推荐答案
Winium.Desktop是一种测试工具，通常用于自动化端到端或其他功能测试方案.当它用作测试工具时，仅在开发/测试阶段才需要，而在生产中则不需要.
Winium.Desktop is a testing tool, it is usually used to automate end-to-end or other functional testing scenarios. When it is used as testing tool, then it is only required during development/testing phase, not in production.
但是，如果您不是将Winium.Desktop用于测试，而是将其用作自动化工具，例如用于自动安装软件，即Winium.Desktop，则它是解决方案的核心部分，它运行安装程序并单击下一步或类似按钮，然后在部署阶段，您将需要Winium.Desktop.
But if you use Winium.Desktop not for testing, but as an automation tool, for example to automate installation of a software, i.e. Winium.Desktop is a core part of solution that runs setup program and clicks next or something, then you will need Winium.Desktop during deployment phase.
Winium.Desktop与Cruciatus相比的关键优势在于它提供Selenium接口并用作客户端服务器，这对于测试自动化非常有用，因为可以扩展客户端服务器，并且Selenium接口是众所周知的，并且有很多如何使用它的教程.
Key advantage of Winium.Desktop over Cruciatus is that it provides Selenium interface and works as client-server, which is useful for test automation, as client-server can be scaled, and Selenium interface is well known and there are a lot of tutorials on how to use it.
如果您只需要自动化某些软件的安装(即不需要使用Winium进行实际测试)，我建议您研究一下诸如Ansible，Chef等IT基础架构自动化工具之一的方向.
If you just need to automate installation of some software (i.e. do not need to do actual testing using Winium), I would suggest looking into direction of one of IT infrastructure automation tools like Ansible, Chef, etc.
关于管理员权限，我建议在 https://github.com/2gis中打开一个问题/Winium.Desktop/issues 描述您的用例，可能有一种无需管理员权限即可运行它或只授予一次访问权限的方法.
Regarding admin rights I suggest to open an issues at https://github.com/2gis/Winium.Desktop/issues describing your use case, probably there is a way to run it without admin rights or grant access only once.
这篇关于Winium.Desktop是否需要甚至在开发后也要运行?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
