The purpose of this paper is to help library technology staff understand the process of beta testing software, determine if it is appropriate for them to engage in the process, and provide suggestions on how to the time invested in the process.
The paper explains what beta testing is, why it should be used and how to become a beta tester.
The paper reveals that beta testing is not convenient for everyone, but those taking place in these activities should be thorough, positive and generous in order to maximize the return on investment in this kind of testing.
While beta testing new software features can take a significant amount of time, the resulting benefits of early access to new features and improved vendor‐staff relations can make it a worthwhile investment.
The paper provides useful information on beta testing software.
