An easy recipe to do this is to include a dependency on a module version which only development releases reached that far.
That will provoke installations by the CPAN shell to fail complaining about a bad dependency. These actually will generate NA test reports because of dependencies which could not be satisfied.
I saw such an example the other day. The dist KSx-Analysis-StripAccents declared a dependency on 0.2 version of KinoSearch. The latest stable release of KinoSearch is 0.162 and the current devel release is 0.20_05. That filled CPAN Testers with NA reports on SPROUT's module.
Note that this is not a major fault from author's part. It is just how the toolchain works nowadays. There is no automated way to have a dependency on development versions, which seems a good thing, but which cannot be circumvented (unless it is done manually).
Maybe, that has some resemblances with declaring dependencies on third-party modules which are not in CPAN (like SVN::Core and modules in the list kept by Module::ThirdyParty,
and company-specific code).
