Project Demo. Ubiquitous and Mobile Computing /17

Size: px

Start display at page:

Download "Project Demo. Ubiquitous and Mobile Computing /17"

Gervais Hugo Mosley
5 years ago
Views:

1 Project Demo Ubiquitous and Mobile Computing /17 Scenario Setup: Users: Alice: Username: 'Alice' Password: 'passa' Sport: Volleyball Favorite TV Show: Friends Bob: Username: 'Bob' Password: 'passb' Sport: Basketball Favorite Movie: Matrix Joe: Username: 'Joe' Password: 'passj' Sport: Football Favorite Movie: Tron Test 1: User Registration, Login, and Logout Setup: Load server without any state. Start two emulators E1 and E2. Step 1: Register user Alice in E1 and user Bob in E2 Expected output: registration should succeed. 1/5

2 Step 2: Login Alice using E2 and Bob using E1. Expected output: login should succeed as the application asks the server for login validation. Step 3: Logout Alice and Bob. Expected output: logout should succeed. Step 4: Try login for Alice in E2 but with wrong password. Expected output: login should fail. Step 5: Try login for Alice in E2 with fake username (i.e., other than Alice) but correct password. Expected output: login should fail. Test 2: Configure Profile Keys for Alice and Bob. Step 1: Edit profile keys for Alice (using E1) and Bob (using E2). Expected output: both Alice and Bob should be able to add their profile keys Step 2: Look for keys belonging to other users. Expected output: Alice should be able to see the key 'Favorite Movie' (which she doesn't use) and Bob should see the key 'Favorite TV Show' (which he doesn't use). Test 3: List and Create locations Step 1 [using E2, logged in with Alice]: List locations. Expected output: There are no locations available. Step 2 [using E2, logged in with Alice]: Create a new location for the GPS coordinates ( , , 50m), corresponding to 'Terreiro do Paço'. Expected output: A new location should be available in the server. Step 3 [using E1, logged in with Bob]: List locations. Expected output: Bob should be able to see the new location created by Alice. Step 4 [using E1, logged in with Bob]: Create new location for 'eduroam'. 2/5

3 Expected output: A new location should be available in the server. Alice should be able to see it. Test 4: Post and read centralized messages Setup: Launch Termite and create (and setup) three devices: one for E1, one for E2, and one for 'edoroam'. Step 1 [using E2, logged in with Alice]: Post a new message with white list profile 'Sport = Basketball' and location = 'Terreiro do Paço'. Expected outout: A new message should be created and should be available in the server. Step 2 [using E1, logged in with Bob]: Move E1 to somewhere close to 'Terreiro do Paço'. Expected output: Bob should receive a notification saying that there is a message available. Step 3 [using E1, logged in with Bob]: Read message and then, move E1 close to 'edoroam' and away from 'Terreiro do Paço'. Finally, read the message again. Expected output: Bob should be able to see the message before and after E1 being moved. Step 4 [using E1, logged in with Bob]: Again, move E1 to somewhere close to 'Terreiro do Paço' and away from 'eduroam'. Expected output: Bob should not receive a notification again. Test 5: Unpost centralized messages Step 1 [using E2, logged in with Alice]: Same as 4.1 Expected output: Same as 4.1 Step 2 [using E1, logged in with Bob]: Same as 4.2 Expected output: Same as 4.2 Step 3 [using E2, logged in with Alice]: Unpost message. 3/5

4 Expected output: the message should no longer be available to other users. Step 4 [using E1, logged in with Bob]: Read message from post. Expected output: Bob shouldn't be able to open the message since the post is no longer available. Test 6: Centralized unread post Step 1 [using E2, logged in with Alice]: Post a new message with white list profile 'Sport = Basketball' and location = 'Terreiro do Paço'. The message timeout should be 60 seconds. Expected output: A new message should be created and should be available in the server. Since Bob is already at 'Terreiro do Paço', he should receive a notification. Step 2 [using E1, logged in with Bob]: Move E1 away from 'Terreiro do Paço' and try to read the message. Expected output: Bob shouldn't be able to read the message since he is no longer in its target destination. Test 7: Centralized post timed out Step 1 [using E2, logged in with Alice]: Same as 4.1 Expected output: Same as 4.1 Step 2 [using E1, logged in with Bob]: Same as 5.2 Expected output: Same as 5.2 Step 3 [using E2, logged in with Alice]: Wait for 60 seconds. Expected output: the message should no longer be available to other users. Step 4 [using E1, logged in with Bob]: Same as 5.4. Expected output: Same as 5.4 Test 8: Exchange decentralized messages Step 1 [using E1, logged in with Bob]: Post a new decentralized message with white list profile 'Sport = Volleybal' and location = 'eduroam'. 4/5

5 Expected output: A new message should be created and should be available to distribute from E1. Step 2 [using E2, logged in with Alice]: Move Alice to 'eduroam'. Expected output: Alice should not receive any message since Bob is not close to 'eduroam'. Step 3 [using E1, logged in with Bob]: Move Bob to 'eduroam'. A new ad-hoc network should be created between Bob and Alice. Expected output: The message should be send from Bob to Alice. Step 4 [using E2, logged in with Alice]: Alice should receive a notification of a new message and should be able to read it. Test 9: Exchange decentralized messages using a relay node Setup: Create an additional emulator (E3). Register and login user Joe in E3. Using termite, setup E3. Move E2 and E3 to 'Terreiro do Paço'. Move E1 to 'eduroam'. Step 1 [using E2, logged in with Alice]: Send a decentralized message using a relay node with black list profile 'Sport = Volleybal' and location = 'eduroam'. Expected output: The message should be forwarded to E3 (Joe). Joe is now a mule. Step 2 [using E3, logged in with Joe]: Move Joe away from 'Terreiro do Paço' and near to 'eduroam'. Expected output: The message should be sent to Bob. 5/5

BDD and Testing. User requirements and testing are tightly coupled

BDD and Testing. User requirements and testing are tightly coupled BDD and Testing User requirements and testing are tightly coupled 1 New Concept: Acceptance Tests Customer criteria for accepting a milestone Get paid if pass! Black-box tests specified with the customer