UI-Tests (01-05)

[steffenkux]

TESTED VERSION: STAGING 2024-05-08T10:20:55 a0ddf4

PRIO1 ... critical bug, blocks release PRIO2 ... bug, but doesn't block release PRIO3 ... not nice, not critical for release

• [x] PRIO1 Chain needs to be changed automatically (Optimism) When I select Optimism for the dm3 name, write a name, and press "Claim", I get the error message "Invalid chain..." (see pic 01) EXPECTED: The app must automatically switch to the correct chain (in this case Optimism) (e.g., trigger a change in Metamask...)

• [x] PRIO1 Chain needs to be changed automatically (Gnosis) When I write my GNO name to publish the profile, I get the error "invalid chain..." (see pic 02) EXPECTED: The app must automatically switch to the correct chain (in this case Gnosis) (e.g., trigger a change in Metamask...)

• [x] PRIO1 Title wrong When I change to "Gnosis GNO", it still says "ENS Name" EXPECTED: It must change to "GNO Name"

• [x] PRIO2 Long time, full app overlay in config notifications When I switch to notifications, there comes an overlay over the whole app saying "Fetching notification channels", it takes about 3 seconds, the full component overlay comes at other actions, too. EXPECTED: The fetching information (if needed) must be overlayed only on the notification page in the property dialog, do we really need to fetch something every time I visit this tab? The same is true for other overlays called from inside the notification configuration page.

• [x] PRIO2 Email notification setup - copy and paste When I receive the email with the OTP, I copy the number, go to the dm3 config, and paste it. Only the first digit is pasted. (see pic 03) EXPECTED: All numbers are added correctly.

• [x] PRIO1 Email address of the notification I receive an email from "[email protected]" REQ: Change it to "[email protected]" -> what needs to be prepared for this?

• [x] PRIO1 Email text How to edit the email template text (OTP message, notification message? OTP Email template : https://github.com/dm3-org/dm3/blob/develop/packages/lib/delivery/src/notifications/templates/otp.ts New message Email template : https://github.com/dm3-org/dm3/blob/develop/packages/lib/delivery/src/notifications/templates/newMessage.ts

• [x] PRIO2 Email registration lost, if deactivated When I deactivate email as a notification, it is correctly deactivated. When I return to the notification config page, the email address is removed and I have to register it. EXPECTED: The registration is still there and can be reactivated by setting the checkmark (without the registration process). (It works, if I deactivate notifications completely and later reactivate it.)

Pictures

01

02

03

[Bhupesh-mfsi]

@steffenkux Here is the link for Email templates :

OTP template : https://github.com/dm3-org/dm3/blob/develop/packages/lib/delivery/src/notifications/templates/otp.ts MSG template : https://github.com/dm3-org/dm3/blob/develop/packages/lib/delivery/src/notifications/templates/newMessage.ts

[Bhupesh-mfsi]

To setup email [email protected]

1. Choose an Email Hosting Provider: Look for email hosting providers that offer services suitable for your company's needs. Popular options include Google Workspace (formerly G Suite), Microsoft 365, Zoho Mail, and Rackspace Email.
2. Select a Plan: Review the plans offered by your chosen email hosting provider and select one that fits your requirements in terms of storage, number of email accounts, features, and pricing.
3. Register Your Domain: If you haven't already registered your company domain, you'll need to do so. Domain registration services are offered by various companies known as domain registrars. Some popular registrars include GoDaddy, Namecheap, and Google Domains.
4. Set up DNS Records: Once you've registered your domain, you'll need to set up the necessary DNS (Domain Name System) records to point to your email hosting provider. This typically involves adding MX (Mail Exchange) records to your domain's DNS settings. Your email hosting provider will provide you with the specific MX records to add.
5. Create Email Accounts: After setting up your DNS records, you can usually create email accounts using your email hosting provider's administration panel. You'll need to choose the usernames and passwords for each email account you create.

After this setup we need HOST, PORT No, EMAIL ID, USERNAME & PASSWORD to be used in backend