Sign In
Reed and Steve Stuff
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
certificates
consumer apps
deployment
developers
devices
Ecosystem
education
emulators
enterprise
fun and games
general
history compatibility
Hopper
Marketplace
mobile browsing
newbies
OneApp
robots
ROI
security
support
tech links
Tips
virtual memory
WP7 LOB
Archive
Archives
April 2011
(1)
September 2010
(1)
August 2010
(1)
July 2010
(2)
June 2010
(1)
May 2010
(1)
January 2010
(1)
October 2009
(2)
September 2009
(4)
August 2009
(3)
July 2009
(5)
June 2009
(4)
May 2009
(6)
April 2009
(2)
March 2009
(6)
February 2009
(3)
January 2009
(1)
December 2008
(8)
November 2008
(2)
October 2008
(4)
September 2008
(6)
August 2008
(5)
July 2008
(7)
June 2008
(5)
May 2008
(6)
April 2008
(1)
March 2008
(4)
February 2008
(5)
January 2008
(3)
December 2007
(3)
November 2007
(3)
October 2007
(3)
September 2007
(2)
August 2007
(4)
July 2007
(3)
June 2007
(8)
May 2007
(9)
April 2007
(1)
Microsoft Hopper Test Tool for Windows Mobile 6.0, 6.1, and 6.5
MSDN Blogs
>
Reed and Steve Stuff
>
Microsoft Hopper Test Tool for Windows Mobile 6.0, 6.1, and 6.5
Microsoft Hopper Test Tool for Windows Mobile 6.0, 6.1, and 6.5
Reed Robison
28 Jul 2009 4:34 PM
Comments
0
Hopper for 6.5 is live!
Hopper is a software test tool that simulates random user input on mobile devices providing a sometimes meaningful mean time to failure (MTTF) number. It is designed to find bugs and is not intended to run scenario tests or do "specific user things" - it is completely random. Hopper stresses the entire device and will execute anything accessible through the UI many, many times. It has no knowledge of where it is at any time and has limited ability to detect poor system health. Hopper executes randomly, thus different bugs might be encountered each time the tool runs. Fixing enough bugs to impact MTTF may take many runs. Reproducing specific runs and/or finding the particular bug that caused any specific failure can prove to be difficult. While Hopper excels at finding system stability bugs quickly, it was never designed to debug or diagnose the source of any particular problem. It utilizes a "system snapshot" log at regular intervals which can help you understand fault. Determining device MTTF via stress testing and debugging is a simple process: run a stress tool until the device fails, diagnose the failure, fix the bug, and re-start the stress tool. In theory, each time a bug gets fixed, MTTF increases because the tool runs longer without a failure.
Download it here
Thinking about my next blog post... what do you guys/gals want to hear about?
Cheers,
Reed
0 Comments
Hopper
Blog - Comment List MSDN TechNet
Comments
Loading...
Leave a Comment
Name
Comment
Please add 1 and 5 and type the answer here:
Post