test execution
Articles
|
Do You Know What They Want? When you're testing software, you've got your priorities, right? Find as many of the worst bugs you can in the shortest possible time, of course. But what if the project manager has different priorities, such as reliability of a particular feature, or overall stability of the software under load? In this column, Elisabeth Hendrickson explains why it's best to ask a few questions before embarking on your bad-bug-hunting trek, or you might find yourself on a wild goose chase. |
||
|
How Should You Feel When You Find a Bug? How you feel about bugs can affect how productive your work is, how you feel about your job, and how others feel about you. In this column, Bret looks at how we respond to finding bugs and how a neutral, professional attitude can make a big difference. |
||
|
Boost Your Testing Super Powers Remember comic book and cartoon heroes who scaled tall buildings, had x-ray vision, and could turn back time? Software test expert James Bach sees some parallels in what testers need to do to root out bugs. In this week's column James shares some "secret tools" that will extend your testing powers! |
||
|
Take the "Groove Test" and Get Out of Your Rut When does a groove become a rut? Elisabeth Hendrickson has experienced both grooves and ruts while testing a seemingly endless software project or series of projects. Here she explores the subtle slippery slope from groove to rut. She also discusses common causes. Once you fall in, Elisabeth has some pointers to help you climb out. |
||
|
Software Test Summary Report (template) This Software Test Summary Report template is based on the IEEE 829-1998 test standard and additional information added from various sources—actual test plans, instructor experience, student comments, etc. |
||
|
Software Test Activity Log IEEE 829-1998 Format (template) This Software Test Activity Log template is based on the IEEE 829-1998 test standard and additional information added from various sources—actual test plans, instructor experience, student comments, etc. |
||
|
Software Test Incident Report IEEE 829-1998 Format (template) This Software Test Incident Report template is based on the IEEE 829-1998 test standard and additional information added from various sources—actual test plans, instructor experience, student comments, etc. |
||
|
Removing Requirement Defects and Automating Test Organizations face many problems that impede rapid development of software systems critical to their operations and growth. This paper discusses model-based |
Mark Blackburn
September 19, 2001 |
|
|
The Science of Catching Hidden Bugs Bugs that make a system crash are the most dramatic, but they may not be the most interesting. Subtle bugs hide where you don't expect them, causing systems to mislead users with incorrect results. Using scientific inquiry, you can expose these deceptive ne'er-do-wells lurking inconspicuously under the covers. Elisabeth Hendrickson offers good examples and pointers to using this investigative method. |
||
|
How Do You Spell Testing? Exploratory testing operates fluidly in real time. But that doesn't mean the process has to be random or scattered. The use of heuristics and mnemonics can serve as a road map to follow as you dive into the exploratory process. In this column, James Bach shares the mnemonic he relies on most for testing and how you can use it to make sure you're covering all the bases. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.