As a user of the Gambit tool, I have noticed an issue with the function-call-mutation, where the require statement is being treated as a function call.
According to the Gambit documentation, the function-call mutation is intended to replace function call with one of its operands. However, I have observed that the require statement, is also being mutated by this operator.
I am unsure if this is the intended behavior of the function-call mutation. If not, I would like to suggest that the Gambit team review this behavior and make the necessary adjustments to the mutation operator.
If it is the intended behavior, I would like to request that the Gambit documentation be updated to clarify that the require statement is considered a function for the purposes of mutation testing.
Thank you for your attention to this matter.
As a user of the Gambit tool, I have noticed an issue with the function-call-mutation, where the require statement is being treated as a function call.
According to the Gambit documentation, the function-call mutation is intended to replace function call with one of its operands. However, I have observed that the require statement, is also being mutated by this operator.
I am unsure if this is the intended behavior of the function-call mutation. If not, I would like to suggest that the Gambit team review this behavior and make the necessary adjustments to the mutation operator.
If it is the intended behavior, I would like to request that the Gambit documentation be updated to clarify that the require statement is considered a function for the purposes of mutation testing.
Thank you for your attention to this matter.