Bug #18409
closed
Some method reports seem to be affected by previous method calls
Description
When trying some configuration using the method "variable_string_from_command" and "Variable_match" with several "variable_match" on the same variable inside the same technique
it looks like the reports are not independant. I had 3 calls to the method and the third one always had the same result than the first one, even if I changed the expected match to change its result.
Unfortunately I did not have access anymore to the faulty technique, but we should try to reproduce this.
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
Updated by Nicolas CHARLES about 4 years ago
We should sanitize the old_class_prefix, and leaving the class_prefix alone, and also advertizing that the full class_prefix can be used (variable_string_match_${variable_name}_${expected_match} ) so that we can do several match one after the others and use the results afterwards
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.7 to 6.1.8
Updated by François ARMAND almost 4 years ago
- Related to Bug #18505: when sum of length of parameter is larger than 1000 characters, reporting leaks too much from one method to another added
Updated by François ARMAND almost 4 years ago
- Status changed from New to Resolved
Resolved by correction of related ticket #18505