A. Zeller. Yesterday, my program worked. Today, it does not. Why? In Proceedings of the 7th European Software Engineering Conference, September 1999.  Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
The XP of TAO: eXtreme Programming of Large, Open-source.. - Kircher, Levine (2000) (Correct)
....every 7 file change, for maintaining file versions, for concurrent development, and for support of branches. Another important use of configuration management tools on large projects is bug isolation. While we have not yet resorted to an automated defect isolation approach, e.g. delta debugging [19], we have used simple scripts to crudely isolate specific problems. Defect tracking is essential for large software development projects. The DOC group uses Bugzilla [13] for tracking problem reports and enhancement requests. We currently do not require the use of problem reports, for ....
A. Zeller, Yesterday, My Program Worked. Today, It Does Not. Why? in Software Enginering -- ESEC/FSE '99, Lecture Notes in Computer Science Vol 1687, Springer Verlag, Sept. 1999.
Trace Analysis for Aspect Application - Stoerzer, Krinke, Breu (2003) (Correct)
....where all three aspects Timing, Billing and CostLimit have been applied. In that case it would not be obvious which of the three aspect has induced the failure. For large systems with a large set of aspects, identifying the failure inducing aspect is a cumbersome task. We use Delta Debugging [10] in that case: When aspects are seen as the deltas, this will automatically compute a minimal set of aspects responsible for the failure. 2.4 A Note on Multi threaded Programs Trace analysis can also be applied to multi threaded programs, as long as the execution inside threads is still ....
A. Zeller. Yesterday, my program worked. Today, it does not. Why? In Proc. 7th European Software Engineering Conference (ESEC/FSE 99), pages 253--267, 1999.
Causes and Effects in Computer Programs - Zeller (2003) Self-citation (Zeller) (Correct)
No context found.
Andreas Zeller. Yesterday, my program worked. Today, it does not. Why? In Proc. ESEC/FSE'99 -- 7th European Software Engineering Conference / 7th ACM SIGSOFT Symposium on the Foundations of Software Engineering, volume 1687 of Lecture Notes in Computer Science, pages 253--267, Toulouse, France, September 1999. Springer-Verlag.
Isolating Failure-Inducing Input - Zeller (2001) Self-citation (Zeller) (Correct)
No context found.
A. Zeller. Yesterday, my program worked. Today, it does not. Why? In Nierstrasz and Lemoine [11], pages 253--267.
Simplifying Failure-Inducing Input - Hildebrandt, Zeller (2000) (4 citations) Self-citation (Zeller) (Correct)
....to C ( all changes applied) We deliberately do not give a formal definition of a change here. In general, a # i can stand for any change in the circumstances that influences the execution of the program. In our previous work, for instance, we had modeled # i as changes to the program code [15]. In this paper, we search for failure inducing circumstances in the program input; hence, a change is any operation that is applied on the input. The only important thing is that applying all changes results in the failure inducing set C . In the case studies presented in this paper, we have ....
....are 2 n possible test cases for n changes. To determine whether a test case induces a failure, we assume a testing function. According to the POSIX 1003.3 standard for testing frameworks [5] we distinguish three outcomes: 1 The definitions in this section are adapted from our previous work [15]. See Section 8 for a discussion. The test succeeds (PASS, written here as 4) The test has produced the failure it was intended to capture (FAIL, written here as 8) The test produced indeterminate results (UNRESOLVED, written here as ) 2 Definition 3 (Test) The function test : 2 C ....
[Article contains additional citation context not shown here]
A. Zeller. Yesterday, my program worked. Today, it does not. Why? In Nierstrasz and Lemoine [10], pages 253--267.
Using Time Travel to Diagnose Computer Problems - Andrew Whitaker Richard (Correct)
No context found.
A. Zeller. Yesterday, my program worked. Today, it does not. Why? In Proceedings of the 7th European Software Engineering Conference, September 1999.
From Symptom to Cause: Localizing Errors in Counterexample.. - Ball, Naik, Rajamani (2003) (19 citations) (Correct)
No context found.
A. Zeller. Yesterday, my program worked. today, it does not. why? In FSE 99: Foundations of Software Engineering, pages 253 -- 267. ACM, 1999.
From Symptom to Cause: Localizing Errors in Counterexample.. - Ball, Naik, Rajamani (2003) (19 citations) (Correct)
No context found.
A. Zeller. Yesterday, my program worked. today, it does not. why? In FSE 99: Foundations of Software Engineering, pages 253 -- 267. ACM, 1999. 105
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC