Test2:...nderer(3pm)

💖 Test2:...nderer — it's the Test2::Harness::Renderer era 💖

okay so bestie, welcome to the User Contributed Perl Documentation corner of the internet, this is Test2:...nderer(3pm) and she's a whole mood ✨

---

🌸 NAME 🌸

Test2::Harness::Renderer — bestie, she's the base class for Test2::Harness event renderers. she's the blueprint, the blueprint-iest blueprint 🎀

---

🦋 DESCRIPTION 🦋

soooo this section is literally just vibes in the original, there's nothing here 💀 the description is empty, no cap. moving on, the real tea is below 👇

---

✨ ATTRIBUTES ✨

heads up bestie, these get set at construction time and they are NOT changeable after that. set once, slay forever, periodt 💅

• $settings = $renderer->settings — grab the Test2::Harness::Settings reference, it's giving "the receipts" 📋
• $int = $renderer->verbose — tells you the verbosity level, i.e. how chatty this thing is feeling 🗣️
• $bool = $renderer->progress — true if progress indicators should be shown. true = we're showing the little progress bar moment 🌈
• $bool = $renderer->color — true if color should be used 🎨 no color = sad beige terminal energy, honestly

---

👑 METHODS 👑

• $renderer->render_event($event) — called for EVERY single event. the return value? ignored. it's giving "not me, not my problem" 🙈
• $renderer->finish(%ARGS) — called once, after all the testing is done. this is the finale, the last episode, the closing credits 🎬

%ARGS: looks like this, bestie:

• settings => $settings — the Test2::Harness::Settings reference, she's back for the encore 📋
• pass => $bool — true if the tests passed ✅
• tests_seen => $int — how many test files we saw 👀
• asserts_seen => $int — how many assertions got made, count 'em 🧮
• final_data => $final_data — okay this one's the main character. final_data looks like the thing below, and note that some data may just not be present if it's not applicable to your situation. the whole structure can be as simple as "{ pass => $bool }", lowkey minimal, highkey iconic 🫶

{
    pass => $pass,    # boolean, did the test run pass or fail?

    failed => [       # Jobs that failed, and did not pass on a retry
        [$job_id1, $file1],    # Failing job 1
        [$job_id2, $file2],    # Failing job 2
        ...
    ],
    retried => [               # Jobs that failed and were retried
        [$job_id1, $times_run1, $file1, $passed_eventually1],    # Passed_eventually is a boolean
        [$job_id2, $times_run2, $file2, $passed_eventually2],
        ...
    ],
    hatled => [                                                  # Jobs that caused the entire test suite to halt
        [$job_id1, $file1, $halt_reason1],                       # halt_reason is a human readible string
        [$job_id2, $file2, $halt_reason2],
    ],
}

• $renderer->signal($signal) — called when the rendering process catches a signal 🚨 this is your moment to do any cleanup or report the signal. this is not an event, so you can literally just ignore it if you want, no pressure. but bestie, please do not exit or throw any exceptions here, we are NOT doing that in this house 💀

real talk: signal is a clean-up-and-be-chill zone. no exiting, no throwing. we keep it cute and we keep it calm 🧘‍♀️

---

🎀 SOURCE 🎀

the source code repository for Test2-Harness lives right here bestie, go look:

http://github.com/Test-More/Test2-Harness/

---

💜 MAINTAINERS 💜

Chad Granum <exodist@cpan.org> — carrying this whole thing on their back fr fr 🫡

---

💜 AUTHORS 💜

Chad Granum <exodist@cpan.org> — yes the same legend, we said what we said 👑

---

⚖️ COPYRIGHT ⚖️

Copyright 2020 Chad Granum <exodist7@gmail.com>.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

See http://dev.perl.org/licenses/

---

and that's the whole page bestie, you ate that 💅

this little treasure was brought to you by perl v5.40.1, dated 2026-05-10 — go forth and render those events, you gorgeous human 🌸🦋✨