>>Get the developer to fix his bug?
>Good plan. All I need now are developers who never check in bugs and I
won't need to wrestle with smoke tests at all.
Ideally, you should be wanting to get rid of the developers, and then you
won't have to do /any/ tests.
>Unfortunately, fixing the bug doesn't get rid of the orphan IE window
from the last run of the test suite. And because of the way my team
develops smoke tests for this app, this is a common pattern for a bug in
smoke tests; the smoke test system ought to be able to catch and handle
it gracefully.
Ah. Well, the lovely thing about open-source interpreted code is that you
can duplicate it and hack it. One very inelegant but brutally effective way
that I might do it is to set a global variable and put a conditional (and an
error message) around the call to check_http_error, thus
if SMOKE_TEST
puts "Ignoring call to check_http_error"
else
check_http_error
end
Another would be to use the Windows API to find the handle of the IE window
and send the message to kill the process.
---Michael B.
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
