为什么 Pex 规模不大
您好：我正在看一些视频等，我只是忍不住想知道为什么 Pex 使用率似乎如此之低？
是否存在任何不明显的问题，或者只是许可证问题？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个非常新的工具，要真正正常工作，您需要使用代码契约 也是如此。它还捕获了许多问题，例如可能的整数溢出，许多开发人员认为他们可以忽略这些问题。 Pex 非常棒，最终会取得成功，但它有一个学习曲线，因此需要一些时间才能渗透到 .Net 生态系统中。
我已经在一些新的开发项目中使用了它，它为我节省了两个主要错误（正常单元测试没有发现），这些错误通常需要至少一周的时间来跟踪和修复，再加上一些较小的问题，所以我Pex 的大力支持者。也就是说，要让它在任何规模的现有代码库上产生良好的结果都需要做大量的工作，因此它的成本效益如何需要根据每个项目来确定。
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.