but the point is that the page load timeout is less useful than using a proper explicit wait (a.k.a. WebDriverWait) for the proper element on the succeeding page.
ortho
I see, so usage of "page timeout" should be scarce and only when going to pages via driver.get()? which I am rarely using in my case
jimevans
s/less useful/less commonly useful/
ortho
that's what I was trying to understand...why one versus or over the other
jimevans
even in the case of doing a driver.get(), if you're concerned about the driver moving on before the page is seen as "loaded," the right thing to do is still use WebDriverWait.
usually, anyway.
ortho
got it
then I really have to wonder, mind you I wrote that code many months ago...where the heck did I get that particular snippet of code
if not here...
either Intellisense...or maybe the original tutorial that I came across....
ashwa joined the channel
I guess I never tripped up on an exception b/c they are both set to 30 secs.
ashwa
hi...i have an issue with teamcity...could anyone help with this
jawn_ has quit
need to run nunit tests using teamcity....could configure and trigger the tests but its just generating the build log and no info regarding the test case execution
ortho
again I appreciate the input guys...not trying to be dense, just stubborn in understanding the why of things
rhp has quit
swampdragons joined the channel
phasze
Is there a known bug with IE11 on windows 10 and dealing with a input type 'file' element?
jimevans
phasze: known bug?
phasze
I can't get it to select a file
jimevans bristles at the phrase
only happens on my windows 10 boxes
jimevans
phasze: you know the drill. what version of IEDriverServer? do you have a log file? you're using send_keys on the element (as opposed to click), right?
and, by the way, i'm running file upload tests routinely on windows 10, without issue.
phasze
ok, so not known off the top of your head then? I'll get that info, what bug system is selenium using right now?
but be aware, i'm likely to close the issue immediately if there's not a full repro case.
phasze
that's good to know you can do it without issue though, that means there is a light at the end of the tunnel which hopefully won't take much effort on my end hehe
I understand jimevans, I'll be as thorough as possible
merike has quit
jimevans
remember, folks, if you're doing something common with selenium, something that it seems like dozens or hundreds or thousands of users should already be doing, it's likely we already have a test for that in our test suite. and that test suite gets run against 5 versions of IE, 4 versions of firefox, and chrome on every. single. commit.
merike joined the channel
phasze: but, some things you can try are setting the `ie.fileUploadDialogTimeout` capability to something other than the default of 3000 milliseconds.
(assuming you're using the most recent 2.52.1 of IEDriverServer.exe; if you're using a version other than that, i can't help you)
phasze
pretty sure I am, just verifying now
got them all on auto-update, making sure the update is actually there
jimevans
sorry. i misspoke. it's not that i can't help you if you're using a different version. it's that i won't help you.
phasze: and that's not "you" specifically, that's "you" as in "anyone"
merike has quit
merike joined the channel
jimevans wonders what auto-update phasze is referring to, since there's no auto-update facility for the core selenium library and its components
phasze
correct it's not a built in feature ;)
jimevans: IE 11.0.10240.16384
Selenium 2.52.0
IEdriverserver 2.52.1.0 (32-bit)
windows 10 enterprise (64-bit)
ah sorry, didn't mean for that to come in in multiple lines....
using .SendKeys
jimevans
phasze: then you'll need to provide a log from IEDriverServer.exe that shows the failure.
min joined the channel
phasze
could you direct me on how to turn on logging of that level?
jimevans
though i'd also recommend using the file upload dialog timeout capability (InternetExplorerOptions.FileUploadDialogTimeout property in .NET)
phasze
I'll try that next
jimevans
are you using .NET, or am i misremembering that?
phasze
I am using .net
jimevans
is this local or remote execution?
phasze
remote
jimevans
(local is easier from .NET)
PaulB has quit
tyang has quit
phasze
I'll see if any of my testers with a windows 10 machine and replicate this locally
jimevans
then you'll have to send the right capabilities across the wire. i don't know what "the right capabilities" are for turning on logging for .NET. i'd suspect they're probably documented at :wiki desiredcapabilities
jimevans: I can control the machine at the time of execution if that would help determine another "hidden" window
jimevans
the clue in the log is that the caption of the dialog window it found is ''. it should be something like 'choose file to upload'
phasze
that's the title of the dialog when I watch it
"Choose File to Upload"
errant_rider1 joined the channel
errant_rider has quit
jimevans
which means that the driver is finding some other dialog with window class '#32770' that is visible, has a caption bar, is not disabled, and has a process id that is the same as the IE browser main window.
phasze
so should I run it and watch for that?
or I guess if it has the same process id it wouldn't show in the task manager details would it...
jimevans
i suspect you won't see the window it's finding. by "visible" i mean "has a window style that includes the WS_VISIBLE bit set"
if you had access to spyxx.exe (which comes with visual studio), you could look at the window tree and maybe see what it was finding.
but you could also take a screenshot at the moment the test fails too. that might be instructive.
phasze
the test fails with the file selection dialog open