Monday, May 20, 2013

States' Test Security Policies and Procedures: GAO Report

According to a GAO nationwide survey of state testing directors, all states reported that their policies and procedures included 50 percent or more of the leading practices to prevent test irregularities in the following five areas—security plans, security training, security breaches, test administration and protecting secure materials. Additionally, of the 28 states that administered computer-based assessments, the majority reported including half or more of the leading practices in computer-based testing. However, states varied in the extent to which they incorporated elements of certain categories of leading practices.

For example, 22 states reported having all of the leading practices for security training, but four states reported having none of the practices in this category. Although state officials reported having a variety of security policies and procedures in place, many reported feeling vulnerable to cheating at some point during the testing process.

States reported using various tools, such as statistical analyses of student data, monitoring, and audits of testing procedures, to oversee districts’ implementation of test security policies and procedures, and most states have used this oversight to identify cheating in recent years.

For example, officials in 40 states reported allegations of cheating in the past two school years, and officials in 33 states confirmed at least one instance of cheating. Further, 32 states reported that they canceled, invalidated, or nullified test scores as a result of cheating.

States reported receiving assistance with test security from several sources, with testing contractors being the most frequent source of support. States also identified areas where additional assistance with test security would be useful. In particular, officials from the majority of states reported that it would be very or extremely useful if the Department of Education gathered and disseminated information on best practices in test security.

No comments: