-
Notifications
You must be signed in to change notification settings - Fork 1
Test plan
General remark: There are three java libs which perform most of the algorithms. All features below are tested with those libraries but no in combination with the ASAPAndroid lib and with this application. Potential errors will be originated (in most cases) in some bad use of API, wrong states, or similar stuff that comes from the combination of all those parts.
Don't even think of writing test which check behaviour of ASAP (see ASAPJava), the chat implementation (makan) or certificate exchange. Debugging and testing must be done in those libs. It is much easier. SN2 is too complex.
Thank you in advance for testing our pre-release. Please, write a test log. Note
- date
- devices (hardware / software (Android API Level)
- some specifics if there are some (floating around in a low orbit, seriously: Very crowded (lot of BT phones around - something like that))
Install app on an phone. Start app. A screen must appear that forces to enter a user name and creates an RSA key pair.
Feedbacks makes clear that anything was ok and app can be used.
Two phones (A and B) are required
- Create a new makan M1 on phone A
- Enter a message in M1
- Start Bluetooth on both phones.
- create a connection - wait until connected
- Open makan view in B
Makan M1 and the message of A should be visible on B.
Two phones (A and B) are required
- Start Bluetooth on both phones.
- create a connection - wait until connected
- Create a new makan M1 on phone A which does not exist on B
- Enter a message in M1
- Open makan view in B
Makan M1 and the message of A should be visible on B.
- enter a new message on B
- enter a new message on A
Both message must be visible on both sides
Two phones (A and B) are required. Both exchanged messages in an open makan.
- switch off Bluetooth
- enter a new message on A and on B
- reconnect with Bluetooth
Both messages must now be visible on both sides.
Three phones (A, B, C) are required. Assumed, that A and B exchanged message in an open makan.
- connect phone A with C with Bluetooth
All message from any open makan on A is now visible on C
- enter a new message on C
All messages shall now be visible on A and C
- connect A with B
All messages are now visible on B
Two phone A and B required
- Connect both phones with Bluetooth (or another protocol in version 2 and higher)
- Let A add another person. A is going to wait for credential information.
- Let B send credential information.
- A must receive credential information and make an identity check with transmitted secret.
- A accepts this credential.
There must be a new person entry on A. Person B is know known with an identity assurance of 100% (best value).
- change roles of A and B and do it again. Both should know each other with IA of 100%
Three phone A, B, C required. It is assumed that A and B already exchanged credentials.
- Connect A (or B) with C
C should know see B (or A) in its person list. IA must be 0%
- A (or B) sends its credential to C. C should now see A in its person list with IA 100%. IA of B shall now be at 90%.
Two phone A and B required. Assumed that A and B have exchanged credentials. A and B are not connected.
- A creates a closed chat, add member B and enters a message
- A and B connect
B sees now the newly created chat and the message
A and B required. Assumed that test closed chat creation was performed
- Connect A and C That's a funny test: Nothing should happen on both side. C must not see the newly created chat nor messages inside it.