commit 8775ed722072c70cd0e89f2ddc85937f9ab4dc62 parent 8a34087269826681b23f28ecce170cbb8b3dfde6 Author: Sebastian <sebasjm@gmail.com> Date: Fri, 1 Aug 2025 22:25:19 +0200 int tests Diffstat:
| M | design-documents/067-merchant-self-provisioning.rst | | | 12 | +++++++++++- |
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/design-documents/067-merchant-self-provisioning.rst b/design-documents/067-merchant-self-provisioning.rst @@ -127,7 +127,7 @@ Definition of Done ================== * Children of tracking bug (https://bugs.taler.net/n/10224) all closed - +* Integration tests passing Drawbacks and Alternatives ========================== @@ -150,6 +150,16 @@ Explicitly out of scope *for now* are: * 2FA for login * 2FA for particular operations (e.g. changing bank account) +Integration Tests +================= + +These are scenarios that we consider basic and we should have an integration test for every one of them to know that the spec is implemented properly: + + - A merchant doing an account's registration should get an email/phone notification with the comfirmation code. The merchant account should be in created state and only after using the confirmation code the account can be activated. + - A merchant with an activated account can call "forgot password". Merchant should get a notification with the confirmation code that can be used to call the endpoint to change the password. A new login the with new password needs to be tested. + - An user that is that makes an amount of request about the threshold should get 429 to "sign up" or "forgot password" endpoints. + + Related Efforts ===============