Test case failed because of bug

I’m getting this error

image

Do you know what type of bug is that ?

Yes. I’ve seen this, but never in a Test Case, only in a class/method (keyword).

You have a clash of names somewhere. In my case (if I remember correctly) it was something clashing with the name of a class causing the compiler to “think” I was accessing a constructor.

I realize that’s a sketchy way to describe it, but it’s hard to think back and recall all the details.

Take the binary-chop (A/B) approach…

In your Test Case…

  1. comment out 50% of the problem code.
    1.1 If you still get the error, the problem is in the remaining 50%.
    1.2 If you don’t get the error, the problem is in the commented 50%.

  2. Once you have identified a problem half, add 50% of it (25% of the original) to the commented code, leave 50% of it uncommented.

  3. Repeat from #1 until you have one line of code.

You are basically trying to chase down the problem line until you have it trapped in a corner.

Notional binary-chop worked example, first pass:

imports ...
/*
1 Test step 
2 Test step
3 Test step
4 Test step
*/
5 Test step
6 Test step
7 Test step
8 Test step

Next…

imports ...
/*
1 Test step 
2 Test step
3 Test step
4 Test step
*/
5 Test step
6 Test step
/*
7 Test step
8 Test step
*/

Last…

imports ...
/*
1 Test step 
2 Test step
3 Test step
4 Test step
*/
//5 Test step

**6 Test step** // Problem

/*
7 Test step
8 Test step
*/
1 Like

hello,

Russ_Thomas probability math :smile:

Once was a discussion about the same message:

1 Like

yeah. a nasty one which require patience, skills and code sharing to debug it :slight_smile: