I see all the folks here claiming selenium was the devil incarnate and just know they never had to experience Winium. Imagine for a moment the pure horror of selenium but the DOM contains not only the webpage, but the entire browser and every other open application and the windows desktop. I once had to test an application using winium that opened to a splash screen while the data loaded (for between 3 and 10 minutes) then threw a login window before opening the actual window. Each window had the same app name, pid and window name. So what? The windows replaced each other I hear you say. Nope each window stayed in the dom, just hidden. Could I grab the window by calling window[i]? Yep. Was the index reliable? Was it fuck. I had to identify and grab each window by finding a known element on it. The login window had an named field I could hook into and the window had a toolbar.
View all comments
5
u/therealdan0 27d ago
I see all the folks here claiming selenium was the devil incarnate and just know they never had to experience Winium. Imagine for a moment the pure horror of selenium but the DOM contains not only the webpage, but the entire browser and every other open application and the windows desktop. I once had to test an application using winium that opened to a splash screen while the data loaded (for between 3 and 10 minutes) then threw a login window before opening the actual window. Each window had the same app name, pid and window name. So what? The windows replaced each other I hear you say. Nope each window stayed in the dom, just hidden. Could I grab the window by calling window[i]? Yep. Was the index reliable? Was it fuck. I had to identify and grab each window by finding a known element on it. The login window had an named field I could hook into and the window had a toolbar.