-
Interfaces
-
WEB
- Chrome(chromium ) browsers
- Firefox
- Safari
-
Mobile APP
- Android
- iOS
- Windows 8
-
Desktop
- Linux
- Windows
- MacOS
- API
-
Test scenarios
- Documentation: https://telegram.org/faq#groups-and-channels
-
pre conditions
- Group is creared(private or public)
- atleast one member is added
- more group members to be added for various scenarios
-
Conversation
- send and recieve messages as memebr(if permission enabled as "Send messages"
- restricted or banned user should not be able to join or chat
-
Admin user features
- promote member to admin
- remove member
- restrict member
-
Delete messages
- member can delete own messages but not other's
- member can delete own messages for self or everyone
- admin can delete self or other's messages for everyone
-
edit message
- member or admin can edit own messages only
-
reply message
- member or admin can do In line message reply
-
pin message
- Only admin can pin message(s)
-
froward message
- to contacts
- to groups(enabled messeges only)
-
Select message
- Select single or multiple messages
- Forward or delete or cancel selected messages
-
Copy text
- Copies the selected text to clipboard
-
Seen by
- Message read by members or admins represents double tick and username
-
Test Approach
- Understand the technical funtionalities
of Group Discussion
-
Identify the endpoints related to the feature
- Authentication flow and endpoints
- Authorization with different roles such as admin, member
- Prepare Test scenarios or ideas for related endpoints
- Perform exploratory tests around the related endpoints with respect to features
-
Perform integration tests of API with different interfaces and platforms such as mobile, web and desktop
- Refer the "Interfaces" section for more details
-
Security Testing
- security scan of API layers for vulnerabilites
-
Performance Testing
- Measure the API performance with various numbers of users both active and inactice
- Measure the app performances (all interfaces) for contineous flow of messages withing group