Test::A...a::Class(3)

πŸ“¦
version 1.002 Β· 2 versions
, in fedora 43

πŸ’– Test::A...a::Class β€” the manual, but make it make sense πŸ’–

okay bestie, welcome to the Test::A...a::Class(3) page β€” that's the perl man page for Test::Able::Runner::Role::Meta::Class, and yes the title got chopped up by the man renderer, we don't talk about it. sit down, grab a boba, we're learning a metaclass role for test runners. no cap. 🧚✨


🌸 NAME 🌸

Test::Able::Runner::Role::Meta::Class β€” it's the metaclass role for test runners. periodt. πŸ‘‘


✨ VERSION ✨

version 1.002 β€” that's the one, that's the version. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so basically this class is where all the real work lives when it comes to loading up the test objects you're about to run. it's the backstage crew. the stagehands. the ones making the magic happen while everybody's looking at the shiny runner. πŸŽ€

but lowkey? you probably do not need to use this directly. only touch it if you're doing something fancy, iykyk.

for the normal, everyday, just-trying-to-run-my-tests case, go look at Test::Able::Runner instead. that's your main character. this one's the supporting role. 🌈


πŸ’œ ATTRIBUTES πŸ’œ

base_package

this gets set by the -base_package option that you send into use_test_packages. and if you're wondering "was it actually set tho?" β€” there's a has_base_package predicate that will tell you. yes ma'am, a whole predicate just for the vibe check. βœ…

test_packages

same situation, different attribute β€” this one is set by the -test_packages option sent to use_test_packages. and yeah, there's a has_test_packages predicate to confirm whether it's been set. bestie check-in, built right in. 🫢

test_path

this one is set by the -test_path option sent to use_test_packages. that's it, that's the whole lore. ✨


πŸŽ€ METHODS πŸŽ€

test_classes

this hands you back all the packages that are gonna get loaded for testing. important note: it does not filter out classes that have $NOT_A_TEST set. it's giving "i show you everything, you decide." 😌

as for how it finds them: if base_package has been set, it'll go search for test classes. otherwise, it just returns you the contents of test_packages. simple. elegant. slay. πŸ’…

build_test_objects

this one returns all the test objects that this runner should actually run. it does it in three lil steps, and honestly? the process is kinda iconic:

  1. it grabs a list of potential test classes by calling test_classes. πŸ“‹
  2. it goes through each package and throws away any of them that have a package global variable named $NOT_A_TEST set to a true value. bye felicia. πŸ‘‹
  3. it instantiates the surviving test classes and returns an arrayref full of those test objects. boom. πŸ”₯

setup_test_objects

calls build_test_objects and then sets the test_objects accessor that comes from Test::Able::Role::Meta::Class. it's the little wrapper that could. 🌟


πŸ‘‘ AUTHOR πŸ‘‘

Andrew Sterling Hanenkamp <hanenkamp@cpan.org> β€” the legend, the icon, the moment. πŸ’–


Copyright 2010 Qubling Software LLC.

This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself. fr fr, it's free, go wild (within the terms of Perl itself, obviously). πŸ“


and that's the whole page bestie!! πŸŽ‰ this masterpiece was rendered by perl v5.42.0 on 2025-07-25, brought to you by the fine folks at User Contributed Perl Documentation. mwah. πŸ’‹βœ¨

πŸ“¦ where this page comes from