You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posted on Mar 12, 2012 by Happy Lion
I'd like to test the end-result, e.g. a function call that includes a llWhisper() or llMessageLinked() to another script somewhere else. Under some conditions, I want to make sure those llWhisper() or llMessageLinked() calls are not made.
Currently, to test that, I have to do Normal or Exhaustive. This means keying in every single call along the way leading up to this and every one proceeding after this.
We need a nice-plus: (1) Nice, but we can flag selected calls as must be there. (2) In addition, we can flag selected calls that must not be there (perhaps include wildcats for parameters)
This would speed up Unit Testing entry without sacrificing meaningfulness.
The text was updated successfully, but these errors were encountered:
https://code.google.com/archive/p/lslforge/issues/16
Posted on Mar 12, 2012 by Happy Lion
I'd like to test the end-result, e.g. a function call that includes a llWhisper() or llMessageLinked() to another script somewhere else. Under some conditions, I want to make sure those llWhisper() or llMessageLinked() calls are not made.
Currently, to test that, I have to do Normal or Exhaustive. This means keying in every single call along the way leading up to this and every one proceeding after this.
We need a nice-plus: (1) Nice, but we can flag selected calls as must be there. (2) In addition, we can flag selected calls that must not be there (perhaps include wildcats for parameters)
This would speed up Unit Testing entry without sacrificing meaningfulness.
The text was updated successfully, but these errors were encountered: