On Thu, September 8, 2005 22:31, Jim Arnold said: > Selenium seems to be a bit fickle about refreshing test fixtures: > sometimes reloading the whole frameset works, sometimes we have to reload > just the test fixture frame, sometimes we have to switch to a brand new > browser instance... We can't seems to get a handle on exactly why or when > Selenium doesn't refresh, but it certainly isn't consistent. Are there > any recommended practices for refreshing tests?
I presume you're talking about reload of a test after having changing the test? (By the way, they're not really test "fixtures"). Selenium doesn't do anything special to force reload of suite or test documents ... they're just treating like normal HTML documents. Perhaps your server isn't correctly notifying the browser that the test-document has changed? Or perhaps your browser is configured to always use it's cache without checking for a new version? Have you tried disabling your browser cache? -- cheers, Mike _______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
