TorXakis Shrinking / Isolating the defect

When a issue is found the trace might contain unnecessary steps and data. For example, •loops might be removed while the bug still occurs. •only the x and y values are relevant to trigger the bug.

Can TorXakis shrink the path and the relevant data? Can TorXakis summarize the data? For example, providing the constraint x+y > MAX_INT will help the developer to the root cause of a bug (in this case probably overflow).

Aug 15 '17 08:08 keremispirli

needs #122

Oct 06 '17 07:10 pjljvandelaar

Look at the literature. For example, A. Zeller and R. Hildebrandt, 2002. Simplifying and isolating failure-inducing input. IEEE Trans. Softw. Eng 28(2), 183-200.

Oct 31 '17 10:10 pjljvandelaar

Shrinking is also called isolate: see e.g. https://reqtest.com/testing-blog/3-simple-tricks-to-make-exploratory-testing-more-efficient/

see also https://testkeis.wordpress.com/2011/06/22/rimgea/ and https://testkeis.wordpress.com/2009/03/29/bug-isolation/

Should TorXakis use and automate RIMGEA?

Feb 22 '18 15:02 pjljvandelaar

Seems also to be related to Model Slicing. See e.g. Slicing MATLAB Simulink models by Reichert and Glesner in Proc. of ICSE 2012

Mar 29 '18 13:03 pjljvandelaar

Having a default behaviour might help. For example, fill in webform: allowed behaviour all fields in any order, yet default top-down order. Simplifies reporting to user.

Aug 28 '18 14:08 pjljvandelaar