I suspect this is caused as a side-effect of previously not having silo'ed the testcode correct. E.g a having a single FB and several different testmethods that access the single FB. This way of programming should be avoided in the future.
If I encounter this specific issue, I'll post the code which causes the behaviour.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@aliazzz do you have a sample code where this can show this?
I suspect this is caused as a side-effect of previously not having silo'ed the testcode correct. E.g a having a single FB and several different testmethods that access the single FB. This way of programming should be avoided in the future.
If I encounter this specific issue, I'll post the code which causes the behaviour.
We should use this on the List FB, so that you cannot assign a list to a list.
eg: List1 := List2;
{attribute 'no_assign'}
When you do assign a list to a list, both lists think they own the same objects, but they don't, and that's all kinds of mess.
{attribute 'no_assign'}
Smart addition! => Saves a lot of headaches 💪
Done, List is now decorated with;
{attribute 'no_assign'}