Selenium tends to mock the User Actions and some among them are:
- Sending Text :
sendKeys("LiamHarries")
- Special Keyboard Characters :
sendKeys(Keys.ENTER)
and sendKeys(Keys.RETURN)
- Mouse Hover :
moveToElement(element).perform()
- Click :
click()
All these User Actions are independent of the underlying os and Hardware Configuration. Hence if they run the same code and they will behave the same.
Update :
As per your comment ...if something is rendered one was on chrome on windows will it be the same on chrome on Linux..., it is worth to mention when new versions of Web Browsers are published in different formats (e.g. .tz
/.tr
/.gz
for Linux
and .zip
/.rar
for Windows
) and they contain the required components (separate for windows / linux and 32
/ 64
bit) to install the Browser as per underlying OS Architecture.
Though the install location and directory structure may vary within the os , the release candidate WebDriver goes through different Testing Procedures (e.g. Alpha Testing, Beta Testing, UAT and UX Control Testing) which does ensures that the User Experience is seamless and similar across all OS Variants.
Hence, from Selenium's perspective underlying hardware bears no impact
Note : There have been instances when the Headless Chrome feature was available in early Google Chrome builds but that was a well planned move following the Chrome Release Map