Acadia --  we used to have an initial step in the product testing process which was called "pre-testing", where we'd only check for things like readme problems and folder structures, etc..  But "pre-testing" was strictly a preliminary step -- and it was always followed by a full-on test.  We've changed the testing procedures since then, but that was the old methodology.

Perhaps that's what you're remembering.

With the backlog of testing results from many years past that I've seen, we never as a matter of policy merely checked readme's and such without testing the product's functionality.

Something To Do At 3:00AM