You say that the error "RuntimeException: Assertion operator name 'BeInRange' has been added multiple times." is a bug fixed after version 4.1 but I'm using version 4.9 and get that error if I modify the custom assertion code after loading the module and then I execute again the tests. There is any solution for this? (any distinct of close PS and open it again :) )
I’m a Senior DevOps Engineer at Oneview Healthcare, automating our way towards Continuous Delivery.
I work primarily on deployment, release engineering and configuration management.
Hi, thanks for this AWESOME Tutorial!
You say that the error "RuntimeException: Assertion operator name 'BeInRange' has been added multiple times." is a bug fixed after version 4.1 but I'm using version 4.9 and get that error if I modify the custom assertion code after loading the module and then I execute again the tests. There is any solution for this? (any distinct of close PS and open it again :) )
Hmmm, interesting.
There has been a lot of changes in Pester since I've written this article.
If you can easily reproduce this with Pester 4.9.x, I would suggest to open an issue at the Pester repository.