Anyone already using selenium for automated testing of D6/head ? We've been doing some testing against postgres, and now have a bunch of selenium tests we can contribute. What now?
Hi Brenda, I'm certainly interested in those. If you have a cvs account perhaps you could stick them in a sandbox. If you don't, I guess attach them to an issue for "provide basic set of selenium tests". I'll certainly get some use out of those and contribute some back. Thanks, Greg On 9/11/07, Brenda Wallace <brenda@wallace.net.nz> wrote:
Anyone already using selenium for automated testing of D6/head ?
We've been doing some testing against postgres, and now have a bunch of selenium tests we can contribute. What now?
-- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
I've placed them in sandbox/Shiny/selenium They're created by a QA-er extraordinaire whom i work with - Cristina. We've been testing HEAD for a couple days and found very few issues to report. There is one a strange warning i've given up on finding the cause: "warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/brenda/projects/drupal/HEAD/includes/bootstrap.inc on line 669. We've been seen it randomly, and un-reproducably about 5 times now. After discussions on #drupal, we're moving to testing the upgrade path now. On Tue, 11 Sep 2007 20:14:10 Greg Knaddison - GVS wrote:
Hi Brenda,
I'm certainly interested in those. If you have a cvs account perhaps you could stick them in a sandbox. If you don't, I guess attach them to an issue for "provide basic set of selenium tests".
I'll certainly get some use out of those and contribute some back.
Thanks, Greg
On 9/11/07, Brenda Wallace <brenda@wallace.net.nz> wrote:
Anyone already using selenium for automated testing of D6/head ?
We've been doing some testing against postgres, and now have a bunch of selenium tests we can contribute. What now?
Brenda Wallace (Shiny) wrote:
I've placed them in sandbox/Shiny/selenium
They're created by a QA-er extraordinaire whom i work with - Cristina. We've been testing HEAD for a couple days and found very few issues to report.
There is one a strange warning i've given up on finding the cause: "warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/brenda/projects/drupal/HEAD/includes/bootstrap.inc on line 669.
We've been seen it randomly, and un-reproducably about 5 times now.
After discussions on #drupal, we're moving to testing the upgrade path now The way I track these down is using xdebug2. There's a function called xdebug_get_function_stack that prints the function stack.
Edit bootstrap.inc and put this code at the top of check_plain (the function that's really getting the error), it will print the function stack out when you would get the error: if (is_array($text)) { print_r(xdebug_get_function_stack()); } Of course, it means that you have to get xdebug installed and working, and this might take a bit of an effort. -- Doug Green douggreen@douggreenconsulting.com 904-583-3342 Bringing Ideas to Life with Software Artistry and Invention...
Doug Green wrote:
The way I track these down is using xdebug2. There's a function called xdebug_get_function_stack that prints the function stack. Edit bootstrap.inc and put this code at the top of check_plain (the function that's really getting the error), it will print the function stack out when you would get the error:
if (is_array($text)) { print_r(xdebug_get_function_stack()); }
Of course, it means that you have to get xdebug installed and working, and this might take a bit of an effort.
You don't need xdebug to print a backtrace in PHP: debug_backtrace()
And since we have our own handling, couldn't we just have a debug_backtrace() sitting in there, and perhaps an extra mode on the error handling settings that lets errors or warnings do a backtrace? David Strauss wrote:
Doug Green wrote:
The way I track these down is using xdebug2. There's a function called xdebug_get_function_stack that prints the function stack. Edit bootstrap.inc and put this code at the top of check_plain (the function that's really getting the error), it will print the function stack out when you would get the error:
if (is_array($text)) { print_r(xdebug_get_function_stack()); }
Of course, it means that you have to get xdebug installed and working, and this might take a bit of an effort.
You don't need xdebug to print a backtrace in PHP:
debug_backtrace()
Robert Douglass wrote:
And since we have our own handling, couldn't we just have a debug_backtrace() sitting in there, and perhaps an extra mode on the error handling settings that lets errors or warnings do a backtrace?
I have implemented such things in the form of debug_assert() on sites we're working on. One example is checking that node_load() is called with a valid argument. If not, a backtrace is far more helpful than an error within node_load(). I do clean up the backtrace to only show the essentials and the top few items in the stack. I really don't care to see everything all the way down to the bootstrap process.
participants (6)
-
Brenda Wallace -
Brenda Wallace (Shiny)
-
David Strauss -
Doug Green -
Greg Knaddison - GVS -
Robert Douglass