Hi there: I was looking at a few videos, etc and I just cant help but wonder why Pex usage seems to be so low?
Are there any problems that are not obvious, or is it just a licence issue?
Hi there: I was looking at a few videos, etc and I just cant help but wonder why Pex usage seems to be so low?
Are there any problems that are not obvious, or is it just a licence issue?
It s a very new tool and to work really well you need to use Code Contracts as well. It also catches a lot of issues like possible integer overflows that a lot of developers think they can just ignore. Pex is amazing and will take off eventually but it has a learning curve so it s going to take some time to percolate through the .Net ecosystem.
I ve used it on a few new development projects and it has saved me two major bugs (not caught by normal unit tests) that would have taken at least a week to track down and fix normally plus a few smaller issues so I m a big proponent of Pex. That said it takes a lot of work to get it producing good results on an existing code base of any size so how cost effective it is will need to be determined on a project by project basis.
HI there i noticed that when I generate a pex test solution the default encoding of the files is UCS-2 Little Endian, this is not really cool, because all the rest of the files are normally encoded ...
Is there any way to make pex work when the classes under test are internal? how about sealed classes? I mean after all this type of tool is really good for API testing, you are likely to want to keep ...
Hi there: I was looking at a few videos, etc and I just cant help but wonder why Pex usage seems to be so low? Are there any problems that are not obvious, or is it just a licence issue?
Yes, it is possible to generate tests on boundary values for functions like "Sum" or "Divide". Pex is a good tool here. But more often we create tests on business behaviour. Let s consider example ...
I am trying to get Pex to work with linq in my project. I got this explanation on what I need to do: In order for Pex to support Linq, make sure you add a reference to Microsoft.Pex.Linq.dll and add ...