|
|
Re:videos on testing - Prospecting for Bugs
|
|
Date: 2006/11/23 23:40
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
Ross Collard - Prospecting for Bugs ( 377 MB, 61:46 min ) Google TechTalks April 28, 2006 video.google.com/videoplay?docid=5423188099670429665
ABSTRACT Testers' ability to identify, assess and prioritize risk is critical to having the right test focus. Objective, quantitative methods for risk assessment generally do not work well. And s ubjective, intuitive methods for risk assessment are derived as much or more from emotion and psychology rather than "logic". A possible new breakthrough is "prospect theory", which won the Nobel Prize in 2004 in Economics. This theory identifies the circumstances under which people are likely to overestimate or underestimate probabilities. It also shows how attitudes about risk affect behavior. The purpose of this presentation is to examine how we can use this work to improve our test effectiveness. I am confident you will find these ideas are applicable to your work, and can provide quick, tangible pay-off for your investment of an hour to hear this presentation.
Ross Collard is with Collard & Company, a Manhattan-based consulting firm which specializes in software quality. A Google search on his name reveals about 100 citations in this area. He has computer science degrees from Caltech and Stanford, and has taught for UC Berkeley and Harvard.
Post edited by: erkan, at: 2006/11/23 23:41
|
|
The administrator has disabled public write access. |
|
|
|
Re:videos on testing - Using Test Oracles
|
|
Date: 2006/11/23 23:43
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
Douglas Hoffman - Using Test Oracles in Automation ( 477 MB, 89:28 min )
Google TechTalks April 25, 2006 video.google.com/videoplay?docid=-753663485306555503
ABSTRACT Software test automation is often a difficult and complex process. The most familiar aspects of test automation are organizing and running of test cases and capturing and verifying test results. A set of expected results are needed for each test case in order to check the test results. Verification of these expected results is often done using a mechanism called a test oracle. This talk describes the use of oracles in automated software verification and validation. Several relevant characteristics of automated test oracles are included with some advantages, disadvantages, and implications for test automation. Real world oracles vary widely in their characteristics. Although the mechanics of various oracles may be vastly different, I've identified a few classes of oracles and some strategies for automated results verification. The five basic types of oracle strategies are identified and outlined: True, Heuristic, Consistency, Self Referential and the all-too-popular None.
Douglas Hoffman is an independent consultant with Software Quality Methods, LLC. He has been in the software engineering and quality assurance fields for over 30 years and now consults in it.
|
|
The administrator has disabled public write access. |
|
|
|
Re:videos on testing - A Canary in a Coal Mine
|
|
Date: 2006/12/09 23:56
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
Ken Schwaber - A Canary in a Coal Mine (69:14 min) Presented: November 2006 at Agile2006 www.infoq.com/presentations/agile-quality-canary-coalmine
ABSTRACT: Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. Schwaber discussed how a degrading core codebase paralyses a team and negates any Agility gained through process improvement. He proposed strategies for management to identify, track and stop this downward spiral.
content: the way product owners and teams should work together the place that product owners and teams come from using waterfall how Scrum falls apart, if these habits persist how organizations have fallen apart because of these habbits how to undo these habbits
|
|
The administrator has disabled public write access. |
|
|
|
Re:videos - Modeling Application Usage Visually
|
|
Date: 2006/12/21 00:59
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
Scott Barber - Modeling Application Usage Visually (213 MB, 37:17 min) Google TechTalks April 24, 2006 video.google.com/videoplay?docid=3604103307694983622&q=Scott+Barber&hl=en see here for comments: www.testingreflections.com/node/view/4536
ABSTRACT Modeling application usage is more than just parsing log files and calculating page frequencies. Whether we are analyzing navigation path effectiveness, planning for scenario testing, documenting performance test workload models or mapping services or objects to user activity having a single, intuitive picture to reference makes the job easier. In this session, we'll explore a highly adaptable method for visualizing application usage and how to use this model to improve cross-functional team communication without requiring team members to invest time learning some new fad of a modeling language that they'll probably never use again. This method references UCML™ which has been described as "what collaboration diagrams should have been."
Scott Barber is the CTO of PerfTestPlus, Inc. and Co-Founder of the Workshop on Performance and Reliability (WOPR). Scott's particular specialties are testing and analyzing performance for complex systems, developing customized testing methodologies, group facilitation and authoring instructional materials.
|
|
The administrator has disabled public write access. |
|
|
|
Re:videos - Failure Data from Real, Large Systems
|
|
Date: 2006/12/21 01:12
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
Bianca Schroeder - Failures in the real world: Collecting, Analysing, and Exploiting Failure Data from Real, Large Systems (248 MB, 49:56 min) Google Tech Talks October 27, 2006 video.google.com/videoplay?docid=-7292853442549739965&q=failure
ABSTRACT Component failure in large-scale IT installations is becoming an ever larger problem as the number of processors, memory chips, and disks in a single cluster approaches a million. Yet, virtually no data on failures in real systems is publicly available, forcing researchers to base their work on anecdotes and back of the envelope calculations. In this talk, we will present results from our analysis of failure data from 26 large-scale production systems at three different organizations, including two high-performance computing sites and one large internet service provider. Our results indicate that several commonly made assumptions about failures might not accurately reflect field experience. For example in the case of disk failures, we find that failure rates in the field can be by an order of magnitude higher than one might predict on disk's datasheet mean-time-to-failure, and that significant wear-out effects set in much earlier than commonly assumed. We will also talk briefly about our efforts on creating a Usenix-supported failure data repository to provide researchers with a wide variety of real failure data.
the goal of the group is: 1. create a public failure data repository with the help of the Usenix association 2. analyze this data 3. exploit data
Post edited by: admin, at: 2006/12/21 01:34
|
|
The administrator has disabled public write access. |
|
|
|
Re:videos on testing - Model-View-Presenter
|
|
Date: 2007/01/08 16:36
|
By: erkan
|
Status: User
|
|
|
Karma: 3  
|
|
Platinum Boarder  | Posts: 98 |  | |
|
A Model-View-Presenter movie: One example of one interpretation of Atomic Object's version of model view presenter Brian Marick, Sat, 06/01/2007 (23,3 MB, 20:23 mins) www.testing.com/movies/fremtoh-mvp.mov
What Brian Marick tells: Earlier,I promised some thoughts about how Fit and annotated wireframes can beused to test-drive user interfaces with a model-view-presenterarchitecture behind them—specifically, an architecture in the style advocated bythe good folk at AtomicObject.
In order to motivate those thoughts, I need you to understand Atomic Object's style and also get a glimpse of what lies beneath my application's UI. What lies beneath is one of those OO programs where no method does much of anything other than ask another object to do something.
Those are hard to understand from a picture, so I made a movie.
Click the image below if you want to see the first draft version. It requires QuickTime. The movie is 20Mbytes, but should start up promptly. It's 20 minutes long.
Let me know if you think the movie could be a helpful introduction to model-view-presenter. If so, I'll edit it to clean up transitions, dub over mistakes, tighten parts up, etc.
|
|
The administrator has disabled public write access. |
|
|