-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scenarios for mail_base, mail_archive, mail_private #144
Comments
Scenarios should depend on built-in modules |
@yelizariev Updated |
Check Private Channels is for |
@yelizariev It's not about mail_private. I put tests with checking all channels |
@yelizariev Updated |
yelizariev
pushed a commit
that referenced
this issue
Dec 2, 2021
commit is created by 👷♂️ Merge Bot: https://odoo-devops.readthedocs.io/en/latest/git/github-merge-bot.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenarios
Check Inbox (Demo User)
Check Starred
Check Archive
Check Direct messages
Check Private Channels
mail_private scenario:
1 .Go to Discuss menu
2. Click on message from any partner and open his form
3. Write message "Hello"
4.Click on the button
Send internal message
5. Choose recepients: Demo User, for example
6. Click on
Send
button7. Log out
8. Log in as Demo User
9. Check Inbox and find message "Hello"
10. Repeat steps 3-7 for Demo User 2
11. Log in as Demo User
12. Open the same form
13. Check that Demo User didn't get private message adressed to Demo User2
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: