The Latest
|
Practical Approach to Test Object-Oriented Classes[article] This paper explains about testing the object-oriented classes at unit level for their functionality. A new approach has been developed to test the functionality of the object-oriented classes at unit level. |
||
|
Why Trace Requirements?[article] Requirements traceability isn't difficult to understand or implement. As with many process improvements, the hard part is to convince the development team that the practice will benefit them and their project in some meaningful, practical way. This brief article looks at some of the benefits of requirements tracing and offers advice for overcoming resistance to implementation. |
Henrietta Foster
October 1, 2001 |
|
|
Testing in the Bazaar[article] Open source development projects typically include a testing phase, just like their commercial counterparts. But how do open source projects manage the testing process? What tools and resources do these projects use? This article discusses the ways that open source projects accomplish testing goals, and how open source testing compares to testing in a commercial project environment. |
||
|
Implementing Test Automation in an Independent Test Unit[article] This case study is a result of the work that Peterborough Software has done since 1996 in evaluating and using "QARun"--Compuware's 32-bit test execution tool, on their new product "PSenterprise." |
Lloyd Roden
September 28, 2001 |
|
|
A Comparison of IBM's Orthogonal Defect Classification to Hewlett Packard's Defect Origins, Types, and Modes[article] In the last three years, the author has worked with seven Software Development teams to help them categorize defects using Hewlett Packard's Defect Origins, Types, and Modes. More recently, the author has assisted a software testing and development organization analyze the results of defects categorized using IBM's Orthogonal Defect Classification (ODC). |
John Huber
September 28, 2001 |
|
|
How Did I Get So Jaded?[article] Churning out medium-grade software to meet deadlines, and experiencing critically defective projects over the years, can easily wear down optimism till it gives way to cynicism in the software testing and quality professions. In this column, Eileen Strider empathizes with that tendency and offers ideas that may improve the quality of your experience. |
Eileen Strider
September 24, 2001 |
|
|
Software Test Incident Report IEEE 829-1998 Format (template)[article] 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. |
||
|
Master Software Test Plan IEEE 829-1998 Format (template)[article] 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. |
||
|
Software Test Summary Report (template)[article] 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 Plan Template IEEE 829-1998 Format (template)[article] This 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. |
||
|
Software Test Design Specification IEEE 829-1998 Format (template)[article] This Software Test Design 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. |
||
|
Software Test Case Specification IEEE 829-1998 Format (template)[article] 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. |
||
|
Software Test Procedure Specification IEEE 829-1998 Format (template)[article] 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. |
||
|
Software Test Activity Log IEEE 829-1998 Format (template)[article] 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. |
||
|
Mindless Process Improvement[article] 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
September 19, 2001 |
Pages
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.