It'd be a lot easier to test the upcoming changes to batches if we had a single test user defined per role, rather than just testing with an admin account. The prep_for_testing command (from the "localdev.sh" script) already includes admin users (admin and sysadmin) due to the wonky migrations (a topic for another time, but those should not be part of migrations). But instead of just using migration-built users, the command could invoke something in NCA to iterate over all assignable roles and generate users for each.
It'd be a lot easier to test the upcoming changes to batches if we had a single test user defined per role, rather than just testing with an admin account. The
prep_for_testingcommand (from the "localdev.sh" script) already includes admin users (adminandsysadmin) due to the wonky migrations (a topic for another time, but those should not be part of migrations). But instead of just using migration-built users, the command could invoke something in NCA to iterate over all assignable roles and generate users for each.This would support #330