I found from reading in perlop a suggestion to use chomp() to get rid of the extra newline at the end of my here-doc. For testing purposes I would like my test function to return exactly what the file contains. This is the first time I have noticed or cared about this so I thought I would share what I learned.

I'm working on my first module to upload to CPAN and I plan to put this function in a module in 't/lib'. Is there a nicer way to handle retrieving this? I could just make the function slurp the json file and return it. I've been looking at other modules but haven't found a good example yet. Thanks. 

use warnings;
use strict;
use Test::More tests => 1;

print "-------\n";
print json_q();
print "-------\n";
print json_here();
print "-------\n";

is(json_q(), json_here(), "should be the same");

sub json_q {
q(      "Type": 0,
      "Width": 504,
      "X": 18,
      "Y": 18
    }
  ]
});

}

sub json_here {
    chomp(my $json = <<'END_JSON');
      "Type": 0,
      "Width": 504,
      "X": 18,
      "Y": 18
    }
  ]
}
END_JSON

$json
}

[download]

The output looks like:

1..1
-------
      "Type": 0,
      "Width": 504,
      "X": 18,
      "Y": 18
    }
  ]
}-------
      "Type": 0,
      "Width": 504,
      "X": 18,
      "Y": 18
    }
  ]
}-------
ok 1 - should be the same

[download]

In reply to Is a here-doc a good way to retrieve data file contents for testing? by Lotus1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.