Release 2.5 testing notes

[sergei-maertens]

I'm adding some notes for release-testing (by hand) that are relevant and need to be double/triple checked.

• Hash based routing (or not) @SilviaAmAm
  • Validate against ODRU (see Taiga)
  • Embed a form in a "third party CMS" with hash based routing, on a subpath with the ?form=<form-id> query string
  • Ensure that a form can be started from this embed page
  • Ensure that a form can be paused and resumed from this embed page
  • Ensure that the co-sign flow still works (form with co-sign and have another person do the cosign check/confirmation)
  • Appointment with demo plugin
  • Check the appointment cancellation flow
• Test the above flows in our own backend without hash based routing:
  • Pause and resume
  • Cosign
  • Appointment cancellation

Test task orchestration refactor @vaszig :

• Test a form with payment and cosign:
  - Ensure that upon submitting the form, no confirmation email is sent but a cosign request is sent.
  - Upon payment, a confirmation email is sent
  - Upon cosign a confirmation email is sent with the cosigner in the CC
  - Check that registration works
• Test a form without payment:
  - Upon completion the confirmation email is sent
• Test retrying to register submissions
• Test a form with appointments

Styling refactors: @SilviaAmAm

• Styling tests when submitting a form as registrator on behalf of a customer

PDF generation: @SilviaAmAm

• Check styling of confirmation/summary PDF (following WeasyPrint upgrade)

React 18 upgrade (#3697) @Viicos

• Check form designer (tabbed interface, adding/modifying/removing components...)
• Check form definition admin (add / edit)
• Design token editor for style/theme page
• Plugin configuration in global configuration page
• Form versions, viewing + restoring
• Session timeout widget (bottom right in admin, counter + popup)

[SilviaAmAm]

SDK styling problems noticed:

• Dropdown (missing the arrow and a bit too short): (@sergei-maertens)
  
  
• The asterisk has moved further down
  
• Error styling in embedded form misses the red stripe on the left:
  Odru was still loading the CSS from their production environment (not on 2.5 yet)
  

Admin styling problems noticed:

• missing padding in form definition configuration (not present if edited via the form): @vaszig
  This was an existing error and will be tackled in the new design (Wontfix).

Backend frontend styling problems

• The page to log in as administrator looks off: padding between fields/buttons, error styling: @SilviaAmAm
  
  

[Viicos]

• Empty time component can't be saved by default: the placeholder for min/max time is incorrect (same for datetime/date when Fixed value is set):
  

• Default value for cosign component says (this only work when the component was saved, and will happen when reopening it):
  

[vaszig]

• Completion retry flag is not properly updated

If we force a form with a registration to fail and then try to register again the submission in the admin, the registration succeeds but the flag still shows a red cross (needs_on_completion_retry=True - but it should be False)

Tested again and working as expected.

• Generated pdf of an appointment has unresolved variables in it

[sergei-maertens]

Embed a form in a "third party CMS" with hash based routing, on a subpath with the ?form=<form-id> query string

Tested and it's broken - the query string parameter does not get sent along to the backend (SDK issue).

edit: SDK 2.1.1 has the fix