Sciweavers

79 search results - page 3 / 16
» Finding Failure Causes through Automated Testing
Sort
View
WCET
2007
13 years 8 months ago
Finding DU-Paths for Testing of Multi-Tasking Real-Time Systems using WCET Analysis
Memory corruption is one of the most common software failures. For sequential software and multitasking software with synchronized data accesses, it has been shown that program fa...
Daniel Sundmark, Anders Pettersson, Christer Sandb...
SIGSOFT
2006
ACM
14 years 8 months ago
Finding failure-inducing changes in java programs using change classification
Testing and code editing are interleaved activities during program development. When tests fail unexpectedly, the changes that caused the failure(s) are not always easy to find. W...
Barbara G. Ryder, Frank Tip, Maximilian Störz...
USITS
2003
13 years 9 months ago
Why Do Internet Services Fail, and What Can Be Done About It?
In 1986 Jim Gray published his landmark study of the causes of failures of Tandem systems and the techniques Tandem used to prevent such failures [6]. Seventeen years later, Inter...
David L. Oppenheimer, Archana Ganapathi, David A. ...
ICWSM
2008
13 years 9 months ago
Predicting Success and Failure in Weight Loss Blogs through Natural Language Use
We explore the emerging phenomenon of blogging about personal goals, and demonstrate how natural language processing tools can be used to uncover psychologically meaningful constr...
Cindy K. Chung, Clinton Jones, Alexander Liu, Jame...
ICSE
2010
IEEE-ACM
14 years 10 days ago
A methodology to support load test analysis
Performance analysts rely heavily on load testing to measure the performance of their applications under a given load. During the load test, analyst strictly monitor and record th...
Haroon Malik