Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.groff.bug > #1747

[bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff"

From "G. Branden Robinson" <INVALID.NOREPLY@gnu.org>
Newsgroups gnu.groff.bug
Subject [bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff"
Date 2020-02-13 05:40 -0500
Message-ID <mailman.778.1581590423.2412.bug-groff@gnu.org> (permalink)
References <20190317-171436.sv93188.53378@savannah.gnu.org> <20190318-063608.sv97361.84088@savannah.gnu.org> <20190319-111042.sv93119.26542@savannah.gnu.org> <20200118-054735.sv108747.99939@savannah.gnu.org> <20200213-104019.sv108747.89369@savannah.gnu.org>

Show all headers | View raw


Follow-up Comment #4, bug #55941 (project groff):

I have a new appreciation for Bjarni's request now that I've had to actually
write a test for nroff.  :P

Because of the variable runtime environment, influenced by the configuration
parameters, we can't just ship canned tests for it: we have to generate them,
then run them.

I solved this problem in dd725dce808dcff643d33f180ed7ac73e32b0760 but it took
a little bit of effort and thought, mainly due to my lack of familiarity with
automake.

Just a comment.  Future nroff tests can ape my example and we still won't need
a 'test-nroff', but if generating the tests comes to be viewed as ugly or
excessively weighty, it might be wise to reconsider this report.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55941>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/

Back to gnu.groff.bug | Previous | Next | Find similar | Unroll thread


Thread

[bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff" "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> - 2020-02-13 05:40 -0500

csiph-web