Articles

Please enter an article title, author, or keyword
Software Test Case Specification IEEE 829-1998 Format (template)

This Software Test Case Specification 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.

Wayne Middleton's picture Wayne Middleton
Software Test Procedure Specification IEEE 829-1998 Format (template)

This Software Test Procedure Specification 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.

Wayne Middleton's picture Wayne Middleton
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.

Wayne Middleton's picture Wayne Middleton
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.

Wayne Middleton's picture Wayne Middleton
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.

Wayne Middleton's picture Wayne Middleton
Master Software Test Plan IEEE 829-1998 Format (template)

This Master Software Test Plan template is based on the IEEE 829-1998 test standard specification and additional information added from various sources—actual test plans, instructor experience, student comments, etc.

Wayne Middleton's picture Wayne Middleton
Mindless Process Improvement

In this paper, we will explain an approach to scoping an improvement program based on problems and goals of the organization. By adopting this approach, organizations are able to make significant progress on real issues, and make progress on the process improvement model or standard they are trying to achieve. The problems and goals of an organization can scope and sequence your improvement program.

Neil Potter
License to Hack

Is your organization doing Extreme Programming or one of the other agile methods? Are they considering it? Before you jump on the latest methodology bandwagon, you should make sure you're not just giving your developers a license to hack. Karl Wiegers provides some insight into how agile development models can be misused and how you can ensure that your process improvement effort has the best chance to be effective.

Karl E. Wiegers
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
development and test automation methods that reduce the time and resources necessary to develop high quality systems. The focus is how organizations have implemented this approach of model-based verification to reduce requirements defects, manual test development effort, and development rework to achieve significant cost and schedule savings.

Mark Blackburn
Automation Test Tools Comparison

This document has been created as a guide to help testing professionals select, understand, and implement functional test tools in their organisation. Due to the large number of test automation tools available, I have followed the 80/20 rule and selected the most popular as a base for this document. However, where necessary, other products, including test management, performance test, and defect tracking suites will be mentioned.

Ray Robinson

Pages

Upcoming Events

Jun 02
Sep 22
Oct 13