[Sent originally to bug-groff, bug #64509; Wed 02 Aug 2023]; see https://savannah.gnu.org/bugs/?group=groff]]
An example is "an_MR-works.sh". After adding .ds MF I to the INPUT in a line before '.TH ...' I get the expected result. Tests should be independent of the surroundings and should provide the data, on which the results are based. Tests are not to test the value of some used variable(!), but the code! Tests also need to be tested! ----- End of original mail ----- Brandon's answer is in comment #1 "1. I do not require this lecture." This is in your mind. What is this in other readers mind? In mine it is a reminder, and a criticism, as I have earlier pointed out tests that produce a false result caused by an alternative environment (surroundings). "1. I do not require this lecture. Please refrain from uttering it." I do not censor myself. You are actually asking me to do so! You do not give any (valid) reason why I should stop telling a truth, as you keep producing some tests that fail wrongly. "2. What surroundings? Please attach the tmac/man.local file from your build tree." Should you not be aware of your (programs) surroundings? Why should (must) content of files influence the results of tests, instead of them being immune to it. Why should the content of files have to make a test deliver wrong results? N.B. people on this list should also check http://lists.gnu.org/archive/html/bug-groff/ to see what decisions are made. -.-.-. "For what one has forbidden so far as a matter of principle has always been - truth alone.". These words are valid for the history of humankind as well as for Nietzsche's family. Alice Miller "The Untouched key". Virago Press 1990, Page 122. # A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it. Max Planck, "A Scientific Autobiography", 1949. #
