Testingcraft-News Mail Archive

To subscribe to testingcraft-news, click here. Your mailer will appear.
Put "subscribe" (without quotes) in the body of the message, then send it.

02001/02/09

• "Useful Features of a Test Automation System", by James Bach.
• Some advice from Keith Stobie about testing code that handles exceptions (PDF).

02000/09/14

• Chris Agruss and Bob Johnson describe an ad hoc test as one you intend to run only once, unless it discovers a defect. In their paper, they have a justification, examples, and techniques.
• Joseph Tate produced a Word template from the MickeyMake test plan.
• Brian Marick provides a case study of fixing a bug. It's an example of writing the tests before writing the code. There are also new links to off-site articles on developer testing on the Techniques page.

02000/07/30

• "Does a Bug Make a Noise When It Falls in the Forest?", by Noel Nyman, discusses whether you should report a bug that you don't believe a customer could see. (This is a variant of the version in Software Testing and Quality Engineering Magazine, Volume 1, Number 4, July/August 1999.)
• A ten-item checklist, by Rex Black, for writing a good bug report.

02000/07/20

• Cem Kaner's slides on bug advocacy. "A bug report is a tool that you use to sell the programmer on the idea of spending her time and energy to fix a bug." (This is a 743kb PDF file, but well worth the download.)
• An article of Len DiMaggio's: "Reflections on Scheduling Software Tests, the Project Life Cycle, and the Last Minute Bug"

02000/06/30

• A sample test plan for a small project.
  <http://www.testingcraft.com/mickeytest.html>
• A subjective approach to evaluating a test suite.
  <http://www.testing.com/writings/evaluating-test-suites-paper.pdf>

02000/01/17

• A trip report for a workshop on exploratory testing. Summaries of techniques. Tips for using exploratory testing.
  <http://www.testingcraft.com//exploratory-pettichord.html>
• Three experience-based writeups on using coverage tools.
  <http://www.testingcraft.com//coverage.html>
• Documentation for three test drivers that exercise code interfaces (as contrasted to GUIs)
  <http://www.testingcraft.com//automation-code-interface.html>

02000/01/08

• A new section on Exploratory Testing has been added to Techniques. James Bach has a writeup of one way to do exploratory testing. Harry Robinson and Brian Marick have separate pieces that describe why exploratory testing is useful.
  <http://www.testingcraft.com//exploratory.html>
• There is now a Privacy statement and Disclaimer.
  <http://www.testingcraft.com//privacy.html>
  <http://www.testingcraft.com//disclaimer.html>

02000/01/03

• Some groups review bug reports before putting them in the bug database. I'd like to hear people's experiences with that.
  <http://www.testingcraft.com//reviewing-bug-reports.html>
• Modifying the product to reveal internal data can make testing more effective and efficient.
  Here's a case study.
  <http://www.testingcraft.com//wv-case-study/test-support-example.html>
  

01999/12/17

• The data about regression test bugs has been improved with a discussion of interpreting such data. <http://www.testingcraft.com//regression-test-bugs.html>

01999/12/10

• Two more pages continuing a case study of failure improvement.
  <http://www.testingcraft.com//wv-case-study/failure-improvement-2.html>
• A brief description of staked application testing, a test design technique.
  <http://www.testingcraft.com//staked-application-testing.html>
• Some data about what percent of bugs in a project are found by regression
  tests. <http://www.testingcraft.com//regression-test-bugs.html>