The following issue registered for the behat tests:
In the test. N1 credit 22 EUR created and payeed back by cache
Than same amount (22) appears in another (absolutely different) test N2 for the same user:
Analysis show that it caused by:
at this step balance == remainingcredit == 0
but once we tried to set data
by getting data from cache - remainingcredits has been restored to previous value
I have tried to fix this way
but it does not work for some reasons...
Potential problem - it could "renew" credits for the same user after being paid back.
Manually I was unable reproduce that case. But I still worried if I missed something during manual tests...
by now - 5 behat tests fails at 1st run because of above issue but than all passed OK during 2nd run...
Temporary decisioin by @georgmaisser:
"leave it for now. It's a reminder that we should look into this once again."
PS: I have created a custom step to reset credits cache It works OK and no behat error. But it destroy credit cache explicitly and in test only... So - original issue not solved yet.
The following issue registered for the behat tests:
Analysis show that it caused by:
at this step balance == remainingcredit == 0 but once we tried to set data
by getting data from cache - remainingcredits has been restored to previous value I have tried to fix this way
but it does not work for some reasons...
Potential problem - it could "renew" credits for the same user after being paid back.
Manually I was unable reproduce that case. But I still worried if I missed something during manual tests...
by now - 5 behat tests fails at 1st run because of above issue but than all passed OK during 2nd run...
Temporary decisioin by @georgmaisser: "leave it for now. It's a reminder that we should look into this once again."
PS: I have created a custom step to reset credits cache It works OK and no behat error. But it destroy credit cache explicitly and in test only... So - original issue not solved yet.