Some of the 'brp' (build root checks) can be disabled with NO_* variables, e.g.
the following checks on Tumbleweed:

# grep NO_ $(rpm -ql brp-check-suse)
grep: /usr/lib/rpm/brp-check-python.data: Is a directory
[..]
/usr/lib/rpm/brp-suse.d/brp-15-strip-debug:if [ "$NO_BRP_STRIP_DEBUG" = "true"
] ; then
/usr/lib/rpm/brp-suse.d/brp-15-strip-debug:     echo "NO_BRP_STRIP_DEBUG is
set: skipping strip"
/usr/lib/rpm/brp-suse.d/brp-25-symlink:     test "$NO_BRP_STALE_LINK_ERROR" !=
"yes" && had_errors=1
/usr/lib/rpm/brp-suse.d/brp-35-rpath:if [ "$NO_BRP_CHECK_RPATH" = "true" ] ;
then
/usr/lib/rpm/brp-suse.d/brp-35-rpath:        echo "NO_BRP_CHECK_RPATH is set:
skipping check"
/usr/lib/rpm/brp-suse.d/brp-45-tcl:if [ "$NO_BRP_TCL_INDEX_CHECK" = "true" ] ;
then
/usr/lib/rpm/brp-suse.d/brp-45-tcl:        echo "NO_BRP_TCL_INDEX_CHECK is set:
skipping brp tcl index check"
[..]

Unfortunately not all checks can be disabled, because they have no NO_*
variables. For instance someone may want to test Amarok 2.8.90 which contains
some policy problems in *.desktop files. But the desktop test can not be
disabled:

# cat /usr/lib/rpm/brp-suse.d/brp-30-desktop 
#!/bin/sh

perl -I/usr/lib/rpm/brp-desktop.data -MXML::Parser
/usr/lib/rpm/brp-desktop.data/xdg_menu --root-menu
/usr/lib/rpm/brp-desktop.data/applications.menu  --format validate

The packages description of brp-check-suse-13.2+git20150521.971ea2f from
Tumbleweed contains a typo:

# rpm -qi brp-check-suse
[..]
Description :
This package contains all suse scripts called in the
build root checking or in parts implemeting SUSE policies.
                                       ^