打开 Selenium 浏览器的方法不与我当前的浏览器重叠
Way to open Selenium browser not overlapping my current browser
我有以下情况。一旦我开始 Selenium 测试，就会打开一个浏览器 window。由于我有一堆测试并且我每天都会启动它们很多次，所以我不会让 Selenium 在我当前浏览器的前面（我工作的地方）打开新浏览器 window，但是在后台，所以它不会打扰我。可能吗？
PS 来阐明为什么我需要这个 - 一天很多次，当我在当前浏览器中工作时selenium 测试是 运行，Selenium 的浏览器 windows 每个测试都突然打开，我可以突然关闭它，输入一些东西，等等
我现在拥有的：
从软件测试自动化开始是一门艺术。您的测试床应该是：
- 配置了所有必需的软件、库和二进制文件。
- 测试执行 必须在受控环境中执行以优化性能。
- 当您的
@Tests 正在执行时，它应该没有 手动干预。
特别是当您的@Tests是Selenium，而测试执行是进行中 不应干预测试环境，因为：
At the lowest level, the behavior of actions class is intended to mimic the remote end's behavior with an actual input device as closely as possible, and the implementation strategy may involve e.g. injecting synthesized events into a browser event loop. Therefore the steps to dispatch an action will inevitably end up in implementation-specific territory. However there are certain content observable effects that must be consistent across implementations. To accommodate this, the specification requires that remote ends perform implementation-specific action dispatch steps, along with a list of events and their properties. This list is not comprehensive; in particular the default action of the input source may cause additional events to be generated depending on the implementation and the state of the browser (e.g. input events relating to key actions when the focus is on an editable element, scroll events, etc.).
此外，
An activation trigger generated by the WebDriver API user needs to be indistinguishable from those generated by a real user interacting with the browser. In particular, the dispatched events will have the isTrusted attribute set to true. The most robust way to dispatch these events is by creating them in the browser implementation itself. Sending OS-specific input messages to the browser's window has the disadvantage that the browser being automated may not be properly isolated from a user accidentally modifying input source state. Use of an OS-level accessibility API has the disadvantage that the browser's window must be focused, and as a result, multiple WebDriver instances cannot run in parallel.
An advantage of an OS-level accessibility API is that it guarantees that inputs correctly mirror user input, and allows interaction with the host OS if necessary. This might, however, have performance penalties from a machine utilisation perspective.
此外，
Robot Class is used to generate native system input events for the purposes of test automation, self-running demos, and other applications where control of the mouse and keyboard is needed. The primary purpose of Robot is to facilitate automated testing of Java platform implementations. Using the class to generate input events differs from posting events to the AWT event queue or AWT components in that the events are generated in the platform's native input queue. For example, Robot.mouseMove will actually move the mouse cursor instead of just generating mouse move events.
最后，根据Internet Explorer and Native Events：
As the InternetExplorerDriver is Windows-only, it attempts to use so-called "native", or OS-level events to perform mouse and keyboard operations in the browser. This is in contrast to using simulated JavaScript events for the same operations. The advantage of using native events is that it does not rely on the JavaScript sandbox, and it ensures proper JavaScript event propagation within the browser. However, there are currently some issues with mouse events when the IE browser window does not have focus, and when attempting to hover over elements.
浏览器焦点：
The challenge is that IE itself appears to not fully respect the Windows messages we send the IE browser window (WM_MOUSEDOWN and WM_MOUSEUP) if the window doesn't have the focus. Specifically, the element being clicked on will receive a focus window around it, but the click will not be processed by the element. Arguably, we shouldn't be sending messages at all; rather, we should be using the SendInput() API, but that API explicitly requires the window to have the focus. We have two conflicting goals with the WebDriver project.
First, we strive to emulate the user as closely as possible. This means using native events rather than simulating the events using JavaScript.
Second, we want to not require focus of the browser window being automated. This means that just forcing the browser window to the foreground is sub-optimal.
结论
始终将测试环境与开发环境分开，并且绝对避免手动干预 .
浏览器是显示在您当前的浏览器之上，还是出现在后台，取决于驱动程序的实现和浏览器之间的变化——它不依赖于 Selenium 或 Serenity。但是我通常 运行 在无头模式下 chrome 中的测试，这完全消除了问题。
我有以下情况。一旦我开始 Selenium 测试，就会打开一个浏览器 window。由于我有一堆测试并且我每天都会启动它们很多次，所以我不会让 Selenium 在我当前浏览器的前面（我工作的地方）打开新浏览器 window，但是在后台，所以它不会打扰我。可能吗？
PS 来阐明为什么我需要这个 - 一天很多次，当我在当前浏览器中工作时selenium 测试是 运行，Selenium 的浏览器 windows 每个测试都突然打开，我可以突然关闭它，输入一些东西，等等
我现在拥有的：
从软件测试自动化开始是一门艺术。您的测试床应该是：
- 配置了所有必需的软件、库和二进制文件。
- 测试执行 必须在受控环境中执行以优化性能。
- 当您的
@Tests正在执行时，它应该没有 手动干预。 特别是当您的
@Tests是Selenium，而测试执行是进行中 不应干预测试环境，因为：At the lowest level, the behavior of
actionsclass is intended to mimic the remote end's behavior with an actual input device as closely as possible, and the implementation strategy may involve e.g. injecting synthesized events into a browser event loop. Therefore the steps to dispatch an action will inevitably end up in implementation-specific territory. However there are certain content observable effects that must be consistent across implementations. To accommodate this, the specification requires that remote ends perform implementation-specific action dispatch steps, along with a list of events and their properties. This list is not comprehensive; in particular the default action of the input source may cause additional events to be generated depending on the implementation and the state of the browser (e.g. input events relating to key actions when the focus is on an editable element, scroll events, etc.).
此外，
An activation trigger generated by the WebDriver API user needs to be indistinguishable from those generated by a real user interacting with the browser. In particular, the dispatched events will have the isTrusted attribute set to true. The most robust way to dispatch these events is by creating them in the browser implementation itself. Sending OS-specific input messages to the browser's window has the disadvantage that the browser being automated may not be properly isolated from a user accidentally modifying input source state. Use of an OS-level accessibility API has the disadvantage that the browser's window must be focused, and as a result, multiple WebDriver instances cannot run in parallel.
An advantage of an OS-level accessibility API is that it guarantees that inputs correctly mirror user input, and allows interaction with the host OS if necessary. This might, however, have performance penalties from a machine utilisation perspective.
此外，
Robot Class is used to generate native system input events for the purposes of test automation, self-running demos, and other applications where control of the mouse and keyboard is needed. The primary purpose of Robot is to facilitate automated testing of Java platform implementations. Using the class to generate input events differs from posting events to the AWT event queue or AWT components in that the events are generated in the platform's native input queue. For example, Robot.mouseMove will actually move the mouse cursor instead of just generating mouse move events.
最后，根据Internet Explorer and Native Events：
As the InternetExplorerDriver is Windows-only, it attempts to use so-called "native", or OS-level events to perform mouse and keyboard operations in the browser. This is in contrast to using simulated JavaScript events for the same operations. The advantage of using native events is that it does not rely on the JavaScript sandbox, and it ensures proper JavaScript event propagation within the browser. However, there are currently some issues with mouse events when the IE browser window does not have focus, and when attempting to hover over elements.
浏览器焦点：
The challenge is that IE itself appears to not fully respect the Windows messages we send the IE browser window (WM_MOUSEDOWN and WM_MOUSEUP) if the window doesn't have the focus. Specifically, the element being clicked on will receive a focus window around it, but the click will not be processed by the element. Arguably, we shouldn't be sending messages at all; rather, we should be using the SendInput() API, but that API explicitly requires the window to have the focus. We have two conflicting goals with the WebDriver project.
First, we strive to emulate the user as closely as possible. This means using native events rather than simulating the events using JavaScript.
Second, we want to not require focus of the browser window being automated. This means that just forcing the browser window to the foreground is sub-optimal.
结论
始终将测试环境与开发环境分开，并且绝对避免手动干预 .
浏览器是显示在您当前的浏览器之上，还是出现在后台，取决于驱动程序的实现和浏览器之间的变化——它不依赖于 Selenium 或 Serenity。但是我通常 运行 在无头模式下 chrome 中的测试，这完全消除了问题。