Skip to main content

Randall W. Rice

Profile picture for user Randall W.Rice

Member for

22 years 11 months

Randall W. Rice is a leading author, speaker, and consultant in the field of software testing and software quality. Rice, a Certified Software Quality Analyst (CSQA) and Certified Software Test Engineer (CSTE), has worked with organizations worldwide to improve the quality of their information systems and automate their testing processes.

Rice is a regular speaker at international conferences on software testing and is also publisher of The Software Quality Advisor. He is co-author with William E. Perry of the book, Surviving the Top Ten Challenges of Software Testing, published by Dorset House Publishing Company.

Rice has over twenty-five years of experience building and testing mission-critical projects in a variety of environments, including defense and private sector projects.

Company
Rice Consulting Services
Job Function
Consulting
Interests
Project Management
Requirements
Security
Testing
Country
United States

Randall W. Rice is a leading author, speaker, and consultant in the field of software testing and software quality. Rice, a Certified Software Quality Analyst (CSQA) and Certified Software Test Engineer (CSTE), has worked with organizations worldwide to improve the quality of their information systems and automate their testing processes.

Rice is a regular speaker at international conferences on software testing and is also publisher of The Software Quality Advisor. He is co-author with William E. Perry of the book, Surviving the Top Ten Challenges of Software Testing, published by Dorset House Publishing Company.

Rice has over twenty-five years of experience building and testing mission-critical projects in a variety of environments, including defense and private sector projects.

All Articles by Randall W. Rice


All Stories by Randall W. Rice

Surviving the Top Ten Challenges of Software Test Automation

These ten challenges are certainly not the only ones seen in test automation, but they are very common and have been the cause for many test automation projects to fail.