I am creating a test case sheet for my mobile app testing. I will provide the cases,…
- User
I am creating a test case sheet for my mobile app testing. I will provide the cases, format it accordingly, beautify it and provide me the test case sheet.
Message signing test cases
Message data typetext only numerals only text and numerals text with links message with leading space message with trailing space message with both spaces message with spaces alone empty message message with SPAM text prefix message with 256 characters length message less than 256 characters message with more than 256 characters length Recipient cases
Single recipient Multiple recipient Valid recipient mobile number with +91 prefix Valid recipient mobile number without +91 prefix Invalid recipient Signer cases
xorkee app and SPOT app in same mobile TEE handle in Android (FCM mode) TEE handle in Android (socket) TEE handle in iPhone (FCM) TEE handle in iPhone (scoket) TEE handle in Android Tab (FCM) TEE handle in Android Tab (socket) TEE handle in iPad(FCM) TEE handle in iPad(socket) xorkee app and SPOT app in different devices TEE handle in Android (FCM mode) TEE handle in Android (socket) TEE handle in iPhone (FCM) TEE handle in iPhone (scoket) TEE handle in Android Tab (FCM) TEE handle in Android Tab (socket) TEE handle in iPad(FCM) TEE handle in iPad(socket) Token key only handle in windows Token key only handle as a transient in Android Token key only handle as a transient in iPhone User Type
Post handle registration, add in IDzone Two notifications case - (one for confirming enrollment and IDzone membership and another for message signing) decline first notification decline second notification and try signing don't approve first notification (timeout case) don't approve second notification (timeout case) Choose required attributes on the fly when user handle is in DND when user handle is blocked when user handle is locked perform key succession Post handle registration,enroll in xorkeesign and then add in IDzone Two notifications case - (one for confirming IDzone membership and another for message signing) decline first notification decline second notification and try signing don't approve first notification (timeout case) don't approve second notification (timeout case) Choose required attributes on the fly when user handle is in DND when user handle is blocked when user handle is locked perform key succession IDzone active user sign message decline timeout dnd locked blocked UNR Choose required attributes on the fly Key succession
IDzone member attribute modification Two notifications case - (one for confirming attributes change and another for message signing) decline first notification decline second notification and try signing don't approve first notification (timeout case) don't approve second notification (timeout case) when user handle is in DND when user handle is blocked when user handle is locked Choose required attributes on the fly perform key succession Not a IDzone user (TEE user alone or token key only user alone) Entity user Certificate user active expired revoked hold key succession dnd blocked unr Subscription cases
subscription active IDzone subscription expired for IDzone user error message display in SPOT when IDzone admin has no units IDzone subscription renewal when IDzone admin has units in xorkeesign balance( T and NT combinations) IDzone subscription renewal when IDzone admin has xorkeestore balance subscription expired for DSC user renewal through spot app renewal with xorkeesign balance( T and NT) renewal with xorkeestore balance SPOT app compatibility ( for update)
Sign a message from the old app of SPOT and verify it in new version of SPOT app Sign a message from the old app of SPOT and verify it in old version of SPOT app Sign a message from the new app of SPOT and verify it in new version of SPOT app Sign a message from the new app of SPOT and verify it in old version of SPOT app Verify Message
Message signed by IDzone user with one attribute alone with two attributes with more than two attributes with photo alone with one attribute and photo alone with IDzone logo and Photo alone with IDzone logo, photo and other details Message signed by individual Certifcate user check with signing certificate of different CAs with expired cert with revoked cert Message signed by Altasigna Enterprise with active cert with expired cert with revoked cert
Assistant
Mobile App Testing: Message Signing Test Cases
Message Data Type
- Text only
- Numerals only
- Text and numerals
- Text with links
- Message with leading space
- Message with trailing space
- Message with both leading and trailing spaces
- Message with spaces alone
- Empty message
- Message with SPAM text prefix
- Message with exactly 256 characters
- Message less than 256 characters
- Message exceeding 256 characters
Recipient Cases
- Single recipient
- Multiple recipients
- Valid recipient mobile number with +91 prefix
- Valid recipient mobile number without +91 prefix
- Invalid recipient
Signer Cases
Xorkee app and SPOT app in same mobile
- TEE handle in Android (FCM mode)
- TEE handle in Android (socket)
- TEE handle in iPhone (FCM)
- TEE handle in iPhone (socket)
- TEE handle in Android Tab (FCM)
- TEE handle in Android Tab (socket)
- TEE handle in iPad (FCM)
- TEE handle in iPad (socket)
Xorkee app and SPOT app in different devices
- TEE handle in Android (FCM mode)
- TEE handle in Android (socket)
- TEE handle in iPhone (FCM)
- TEE handle in iPhone (socket)
- TEE handle in Android Tab (FCM)
- TEE handle in Android Tab (socket)
- TEE handle in iPad (FCM)
- TEE handle in iPad (socket)
- Token key only handle in Windows
- Token key only handle as a transient in Android
- Token key only handle as a transient in iPhone
User Type
Post handle registration, add in IDzone
- Two notifications case:
- Confirming enrollment and IDzone membership
- Message signing
- Decline first notification
- Decline second notification and try signing
- Don't approve first notification (timeout case)
- Don't approve second notification (timeout case)
- Choose required attributes on the fly
- When user handle is in DND
- When user handle is blocked
- When user handle is locked
- Perform key succession
Post handle registration, enroll in xorkeesign and then add in IDzone
- Two notifications case:
- Confirming IDzone membership
- Message signing
- Decline first notification
- Decline second notification and try signing
- Don't approve first notification (timeout case)
- Don't approve second notification (timeout case)
- Choose required attributes on the fly
- When user handle is in DND
- When user handle is blocked
- When user handle is locked
- Perform key succession
IDzone active user
- Sign message
- Decline
- Timeout
- DND
- Locked
- Blocked
- UNR
- Choose required attributes on the fly
- Key succession
IDzone member attribute modification
- Two notifications case:
- Confirming attributes change
- Message signing
- Decline first notification
- Decline second notification and try signing
- Don't approve first notification (timeout case)
- Don't approve second notification (timeout case)
- When user handle is in DND
- When user handle is blocked
- When user handle is locked
- Choose required attributes on the fly
- Perform key succession
Not a IDzone user (TEE user alone or token key only user alone)
- Entity user
- Certificate user:
- Active
- Expired
- Revoked
- Hold
- Key succession
- DND
- Blocked
- UNR
Subscription Cases
- Subscription active
- IDzone subscription expired for IDzone user
- Error message display in SPOT when IDzone admin has no units
- IDzone subscription renewal when IDzone admin has units in xorkeesign balance (T and NT combinations)
- IDzone subscription renewal when IDzone admin has xorkeestore balance
- Subscription expired for DSC user
- Renewal through SPOT app
- Renewal with xorkeesign balance (T and NT)
- Renewal with xorkeestore balance
SPOT App Compatibility (for update)
- Sign a message from old SPOT app and verify in new SPOT app
- Sign a message from old SPOT app and verify in old SPOT app
- Sign a message from new SPOT app and verify in new SPOT app
- Sign a message from new SPOT app and verify in old SPOT app
Verify Message
Message signed by IDzone user
- With one attribute alone
- With two attributes
- With more than two attributes
- With photo alone
- With one attribute and photo alone
- With IDzone logo and photo alone
- With IDzone logo, photo and other details
Message signed by individual Certificate user
- Check with signing certificate of different CAs
- With expired cert
- With revoked cert
Message signed by Altasigna Enterprise
- With active cert
- With expired cert
- With revoked cert
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.