How to Identify the Infeasible Test Requirements using Static Analyse? An Exploratory Study

Context: Software testing is an essential activity to ensure the quality of the software. However, the selection and generation of test cases can be an expensive and hard task. A large number of infeasible test requirements (e.g. infeasible paths) collaborate to increase the effort on test data generation, and it is not a trivial task to identify them. Objective: To investigate and analyze an process of properties of infeasible test requirements identification in a static way without inputs data through an exploratory study. Methodology: We gathered a set of statistical properties to identify infeasible test requirements without the use of input data. We manually verified the identification process using a benchmark with 19 Java programs. Results and conclusions: The alternative process identified infeasible requirements without using input data and proved effective. This study highlights the tester’s role in the process of identifying the infeasible elements and also the need to automate this process because level of complexity in decision making.