To test a change well, you need to know what it reaches. Niro lists what calls the changed code, through as many levels as you ask. It also lists the routes, tables and events on the way.

How

niro ask get_reverse_call_chain method_fqn=PriceCalculator.total depth=3
niro ask get_blast_radius method_fqn=PriceCalculator.total

Things to know

Playbook

Test a change finds, in one call with answer=locations, the six Keycloak tests the code makes possible three levels up through an interface, of which four really run JpaUserCredentialStore.createCredentialEntity. Two use a user stored outside Keycloak's database, so at run time they go to another store. It also checks the list against a grep.