01559naa a2200253 a 450000100080000000500110000800800410001902400250006010000170008524500860010226000090018852007820019765300240097965300220100365300190102565300320104465300320107665300230110865300160113165300250114770000210117270000130119377300990120610004532020-01-17       2004    bl uuuu     u00u1 u    #d7 a10.1002/smr.2972DOI1 aCHAIM, M. L.  aA debugging strategy based on the requirements of testing.h[electronic resource]  c2004  aIntroduction. Background. Fault site. Data-flow testing requirements. Error-Revealing Data-Flow Testing Requirements. Dynamics of definition-use associations. Error-revealing definition-use associations. Candidates for error-revealing definition-use associations. DRT-the debugging strategy based on the requirements of testing. Use of the heuristics. A breakpoint mechanism for DUAs. New candidates for error-revealing DUAs. Case study. Measures of inclusiveness. Subject programs and test set selection. Collecting the results of the heuristics. Results and data analysis. Threats to validity. Implementation aspects of gdb/poke. Instrumentation. Tracking testing events. Selecting new DUAs. Discussion and related work. Discussion. Related work. Conclusions and future work.  aAutomated debugging  aData-flow testing  aDebugging tool  aDesenvolvimento de software  aDynamic testing information  aFault localization  aHeurística  aRequisitos de testes1 aMALDONADO, J. C.1 aJINO, M.  tJournal of Software Maintenance and Evolution: Research and Practicegv. 16, p. 277-308, 2004.