What kind of parameterization are you thinking of? The test definitions are already in a table-like format where you can define the sets of principals, resources and actions and Cerbos automatically tests the combinations of those. You only need to provide expectations for cases where the result should be ALLOW. You can use
YAML anchors to avoid repeating things as well.
If you're thinking about something more advanced than that, you'd need to generate the tests yourself using a script or a templating tool. Here's an example of doing that with ytt:
https://github.com/cerbos/cerbos/issues/2183#issuecomment-2165903543