Let's confirm that all possible user flows through the configuration screen result in the correct validation state (meaningful error/warning messages displayed, submit button enabled/disabled). This'll involve functional testing, code-reading, and ideally unit testing and refactoring. Some possible issues have already been identified:
Captcha errors are not displayed to the user.
Errors submitting the job to the backend might not be displayed to the user.
As soon as the user loads the page, copy and paste is selected and no sequences are entered in the box, but the “get the clean result” button is still enabled. I think it should be disabled.
Samarth found that in fasta headers, the frontend allows a space after the ">" but the backend does not.
Let's confirm that all possible user flows through the configuration screen result in the correct validation state (meaningful error/warning messages displayed, submit button enabled/disabled). This'll involve functional testing, code-reading, and ideally unit testing and refactoring. Some possible issues have already been identified: