Use Base.checkConsistency to test constraints instead. This is the method which real users are using.

Add an action on the category tool. See tips on the dialog to know how to use it.
This script is based on category file import

add step to create a Person to avoid duplicated code and add test to check that to prove that ERP5Site_newCredentialRecovery will work correctly in case if no question/answer is provided

update tests to follow last changes in erp5_credential. The changes were: 57e6dbf6, ee9adc59, 8ac9c40f

remove script because Base_getDefaultAssignmentArgumentDict is not required anymore and ERP5Site_registerCredentialRequest was merged with ERP5Site_newCredentialRequest.

refactor ERP5Site_newCredentialRequest to get categories from portal_preferences. Add condition to check if the alarm will be called to approve credential requests or one mail will be sent to user to approve it.

add new property to System Preference. This preference is used to know if the alarm will be called automatically or not.

TemplateTool API can find the appropriate name for the file.

Refactor code to follow last changes in SystemPreference_viewCredential form. Now all categories are returned in list and setCategoryList method is used to set all properties in assignment.

update to add category list in portal_preferences. This change is to follow the changes in erp5_credential

Refactor code to not hardcode of base categories. Now is possible use all base categories possible(and others non existing yet).