Software Testing and Development Blog Posts

Practical Experiences With Graph Based Software Testing

Alan Richardson gave a talk at StarEast 2003 based around his experiences with Graph Based Testing.

You can read the 27 page supporting paper as a pdf file here.

Tool Changes and New Tools

Some tools have new versions since the paper was written and I have stumbled across some new tools.

• Graphopt has a new version
• Tintfu has been updated
• here is another dot editor for windows DynaGraph
• Tulip is designed to visualise large graphs, and uses its own graph file format, but can import from GML. It does have some fairly complicated install dependencies.
• PAJEK is another visualisation tool for large graphs.

Simple Spreadsheet

In the paper I mention how simple it would be to construct a spreadsheet that you can use to create the graphs and use to build extra functionality with.

This is a fantastic phrase, it has been popular and it has worked; testing now starts earlier and testing has a higher profile than ever before, but despite all that, it isn’t what we meant or even what we really needed.

…Meyerhold’s bio-mechanical actor said, “I make these movements because I know that when I make them what I want to do can most easily and directly be done.” [1]

What is a fault?

Software Test Scripting

This essay explores the test scripting in terms of software development as the two processes are very similar and share many of the same techniques and pitfalls. It is primarily aimed at manual test script construction because automated test script construction is software development.

Path Analysis for Software Testing

TLDR; This essay explores the use of graph models in testing and the practice of structural path derivation using 3 coverage concerns: node coverage, link coverage and loop coverage. Predicate coverage is considered but is not covered in detail. An exploration of, and notes on, model path analysis for testing:

Lessons learned from Nicola Tesla for Software Testing.

People blame Software Testing for issues rather than the whole development process.

Quality is in the eye of the beholder. We can work through issues, but it doesn’t leave a good impression.

I used to have a lot of book reviews on the site. I decided to delete most of them because books are such a subjective topic. Every book is perfect for someone at the right time. I don’t want to put anyone off finding the right book at the right time. What follows are extracts from deleted book reviews for any segements that have longer term value.