candidate_parameters

[LeighMac]

Tasks:

• Review issues from previous release testing

Documentation Tasks

• Update test plans
• Review/update module READMEs (Interactions, configurations, permissions, widgets, …)
• Check user help content for accuracy and formatting (front end)

Testing Tasks

• Follow test plan (SEPARATE TICKETS)
• Check if automated tests are up to date
• Make sure RB is complete

Standards: Make sure the latest standards are upheld

Check the boxes below only if the statements are true !

• No ajax dir
• Data framework implemented
• React (no templates directory)
• Widgets (If module contains candidate information, at least 1 widget is implemented for the candidate profile module)

Issues

Closed, Done & Reviewed:

• [Candidate Parameters] - Update test plan : [candidate_parameters] - update test plan #8701
• [Candidate Parameters] - Edit date of birth issue : [candidate_parameter] - Edit date of birth issue #8574
• [Candidate Parameters] - Update README.md with permissions' frontend name : [candidate_parameter] - Update README.md with permissions' frontend name  #8557
• [Candidate Parameters] Outdated test plan : [Candidate Parameter] Outdated test plan #7709

Previously created & still open/re-opened:

• [Candidate Parameters] Help text kinda useless... : [Candidate Parameter] Help text kinda useless... #7707
• [Candidate Parameters] Inconsistent behaviour of button Candidate Info : [Candidate Parameter] Inconsistent behaviour of button Candidate Info #7708
• [Candidate parameters] DoB and DoD formats ignored : [Candidate parameter] DoB and DoD formats ignored #6994
• [Candidate parameters] Family table not updatedhttps://github.com/[candidate_parameters] family table not updated #7123
• [Candidate Parameters / Configuration] Add configuration to add consent to DB on front-end : [Candidate_parameter/Configuration] Add configuration to add consent to DB on front-end #5070
• [Candidate Parameters] Add genetic information to the module : [candidate parameter] Add genetic information to the module #4809

Status

• Testing COMPLETE
• Partially Tested
• Could Not Test (please specify reasons in comment)

[charliehenrib]

@ridz1208 I tested what I could, but there is a lot that I could not do due backend testing. I also noticed that no one else is testing this module and I am not confident to leave it with only my testing. So, I think it should be retested by a developer to make sure all is okay.