Is Pex (and its output) suitable for the corporate environment?

I like the idea of ​​Pex - tests for auto-generation using static code analysis, but the tests that the tool actually generates are terrible, ugly, closely related to Pex modules that are difficult to read and understand, etc.

Is such a tool really suitable (in its current state) for use in a corporate environment where the emphasis is on ease of maintenance?

Or did I misunderstand the intended use of Pex?

+5
source share
4 answers

In fact, you misunderstood the intended use.

Pex - . , . . , .

Pex. .

+1

...

, , , /API, . Pex - "" , . , - , , , .

, , . , , Pex , , .

+1

pex , . , pex , ( , , ), , .

pex . , Pex. , , , .

, pex .

+1

Pex is very useful for testing complex algorithms that are independent of external ones. For example, this does not help you find extreme cases in SQL operations or file access. However, to search for extreme cases and increase code coverage, it is extremely useful in addition to your regular modules.

0
source

All Articles