mahara-contributors team mailing list archive

[Robert Lyon <1892265@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently we can do 
And I should not see "Call stack"

But it would be better to have some fast way of checking after every
step if a callstack error has been generated

But rather than check the DOM (which will be slow) we could have the
lib/error.php set a session flag to check for.

Also we might not want to throw behat error / make it a failed step but
just alert us to the fact that backtrace has been generated so we can
check if it's valid or not

** Affects: mahara
     Importance: Wishlist
         Status: New

** Changed in: mahara
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1892265

Title:
  Add to behat an after step check to see if there is an error call
  stack

Status in Mahara:
  New

Bug description:
  Currently we can do 
  And I should not see "Call stack"

  But it would be better to have some fast way of checking after every
  step if a callstack error has been generated

  But rather than check the DOM (which will be slow) we could have the
  lib/error.php set a session flag to check for.

  Also we might not want to throw behat error / make it a failed step
  but just alert us to the fact that backtrace has been generated so we
  can check if it's valid or not

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1892265/+subscriptions