Test::...::Impl(3pm)

πŸ’– NAME πŸ’–

Test::Future::IO::Impl β€” it's the acceptance-test glow-up for your Future::IO implementations, bestie ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

use Test::More;
use Test::Future::IO::Impl;

use Future::IO;
use Future::IO::Impl::MyNewImpl;

run_tests 'sleep';

done_testing;

Like… that's the whole vibe. Load it, point it at your impl, run the suites, done. πŸ’…


🌸 DESCRIPTION 🌸

Okay so, this module is basically a whole collection of acceptance tests for implementations of Future::IO. That's it, that's the tea πŸ«– β€” you bring an implementation, it brings the receipts.


πŸ‘‘ FUNCTIONS πŸ‘‘

πŸŽ€ run_tests

run_tests @suitenames;

This one runs a whole lil collection of tests against Future::IO. Heads up though: it expects that you (the caller) have already loaded the specific implementation module you wanna test against before you call this function. So like, load first, run second. No cap πŸ™ˆ


🌈 TEST SUITES 🌈

These are the suite names you're allowed to pass into run_tests, and what each one is clocking in to do:

  • accept β€” Tests the Future::IO->accept method. ✨
  • connect β€” Tests the Future::IO->connect method. πŸ”₯
  • poll β€” Since version 0.17. Tests the Future::IO->poll method.
  • recv, recvfrom β€” Since version 0.15. Tests the Future::IO->recv and Future::IO->recvfrom methods.
  • send β€” Since version 0.15. Tests the Future::IO->send method.
  • sleep β€” Tests the Future::IO->sleep and Future::IO->alarm methods.

Why are these two squished into one suite? Because they're super similar, and honestly neither one is long or complicated. Two methods, one suite, efficiency queen πŸ‘‘

  • read, sysread β€” Tests the Future::IO->sysread or Future::IO->sysread method.

These two test suites are literally identical except for the name of the method they invoke. They both exist because of the method rename that happened at Future::IO version 0.17. Twins fr πŸ‘―

  • write, syswrite β€” Tests the Future::IO->write or Future::IO->syswrite method.

Same deal, bestie: these two test suites are identical other than the name of the method they invoke, and they exist because of that same method rename at Future::IO version 0.17. πŸ’€

  • waitpid β€” Tests the Future::IO->waitpid method. 🧚

πŸ’œ AUTHOR πŸ’œ

Paul Evans <leonerd@leonerd.org.uk> β€” icon behavior, honestly πŸ™Œ


ok that's the whole page, you ate that πŸ“

Maintainer queen energy and all that: this doc shipped on 2026-02-21, sitting pretty in the User Contributed Perl Documentation corner of the manual, with perl v5.40.1 holding it down. Love that for us. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from