I am running a test on some c# code and pex did not cover the statement with Math.Acos( it is part of a large switch statement). I am curious if anyone know why pex has this limitation? I looked online and could not find anything.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am running a test on some c# code and pex did not cover the statement with Math.Acos( it is part of a large switch statement). I am curious if anyone know why pex has this limitation? I looked online and could not find anything.
Pex builds up a system of constraints (a path condition) of the path it tries to cover next. It then relies on a constraint solver to generate a satisfying assignment for that constraint system. In some cases the constraint solver is not able to find values (within reasonable time). At the moment this mainly occurs for code that involves floating point variables or variables of decimal type.
For example, assume you want to satisfy the condition Math.Acos(x) <= y. Unless Pex can trace the path taken through the Math.Acos function by the input x in a previous execution (where Math.Acos(x) > y), the constraint solver would have to understand how Math.Acos works in order to solve that constraint.
Even if Pex has access to the implementation of Math.Acos, the resulting constraint system might still be too complicated for a constraint solver to handle within reasonable time.