C-3PO Testing Ideas

Get Started. It's Free
or sign up with your email address
Rocket clouds
C-3PO Testing Ideas by Mind Map: C-3PO Testing Ideas

1. UI

1.1. Obeserve if the app adapts for all the different screen sizes

1.1.1. Are the images stretched?

1.1.2. Observe colors

1.1.3. Observe the text size

1.1.4. Scrolls

1.1.5. Overlap of text, imagens, content

1.2. Observe the readability of the content

1.3. For Samsung, try to change the OS fonts and observe the app UI behavior

1.4. Try the available inputs

1.4.1. Text

1.4.2. Emojis

1.4.3. Special chars

2. Usability

2.1. Are content and texts easy to read?

2.2. Does all the screens of the app use the same UI patterns?

2.3. Number os steps to perform an action

2.4. Is the system status always clear to the user?

2.5. Does the system speak the final users' language?

2.6. Does the app contain a Help or documentation?

2.7. Does the app adapts to personalize it to the user?

2.8. Is the interface easy to interact?

2.8.1. How about the touch areas?

2.9. Evaluate if the app was design observing the mobile world constraints

2.9.1. Different screen sizes

2.9.1.1. and Resolutions

2.9.2. One single windows open per time

2.9.3. Operational System events

2.9.3.1. Receive a call/message/etc

2.9.4. Input data

2.9.5. Limited processing capability and power

2.9.5.1. Battery life

2.9.5.2. Network connectivity

2.9.5.3. Limited memory

2.10. If the app is available on the Stores (Apple and Google Play) see the users comments

3. Installation/Launching

3.1. Install the app

3.2. Uninstall the app

3.3. Reinstall the app

3.4. Kill the app process

3.4.1. Launch the app

3.5. Turn off/Turn on the phone

3.5.1. Launch the app

4. Device Platform Interaction

4.1. Events

4.1.1. Receive call

4.1.2. Receive SMS/MMS

4.1.3. Charge

4.1.3.1. Connected

4.1.3.2. Disconnected

4.1.4. Sleeping mode

4.1.4.1. Enter

4.1.4.2. Resumes from

4.1.4.3. Does the app go to sleep mode when running in the background (prevent battery drain)?

4.1.5. Resumes from lock screen

4.1.6. Local message is coming from another app

4.1.6.1. Calendar

4.1.6.2. Alarm

4.1.6.3. Reminders

4.1.7. Push message is coming from another app

4.1.7.1. Twitter mentions

4.1.7.2. Whatsapp message

4.1.8. Low battery message

4.2. Buttons

4.2.1. Menu

4.2.2. Back

4.2.3. Search

4.3. Battery

4.3.1. Validate the app in different battery levels

4.4. Memory

4.4.1. Test the app with

4.4.1.1. Available memory

4.4.1.2. Memory full conditions

4.5. Connectivity

4.5.1. Airplane mode

4.5.1.1. Turn it ON

4.5.1.1.1. Observe how the app behaves

4.5.2. Test the App in different data networks

4.5.2.1. 2G

4.5.2.2. 3G

4.5.2.3. 4G

4.5.2.4. Wifi

5. Performance

5.1. Explore main scenarios that can be possible performance bottlenecks

5.1.1. Measure the performance

5.1.1.1. Internet through 100% lost packets

5.1.1.2. Internet through very bad network

5.1.1.3. App resume working when it gets back into network reach from outside reach of the network

5.1.1.4. Update transactions are processed correctly after re-establishing connection

5.1.1.5. App switches between networks (Wi-Fi, 3G, etc)

5.1.1.6. App still work correctly when tethering or otherwise connected to another device

5.1.2. Use different realistic networks

6. Stress

6.1. Select the more important screens/functionalitis of the software

6.1.1. Run stress test

6.1.1.1. To find Force Closes

7. Responsiveness

7.1. Validate if the app UI adapts for

7.1.1. Different screen sizes

7.1.2. Screen orientations

7.1.2.1. Portrait

7.1.2.2. Landscape

8. Functional

8.1. Access

8.1.1. User authentication

8.1.1.1. Login

8.1.1.1.1. Enter invalid credentials

8.1.1.1.2. Enter valid credentials

8.1.1.1.3. By Google

8.1.1.1.4. By Facebook

8.1.1.2. Logout

8.1.1.2.1. Does the system saves the user login information to later new authentication?

8.1.1.2.2. The user should not be able interact with the app without making the log in

8.1.1.3. Concurrent login

8.1.1.3.1. Does it make sense the app support the same user logged at the same time in differents devices?

8.1.2. Permissions

8.1.2.1. Does the app request any permissions?

8.1.2.1.1. Location

8.1.2.1.2. Contacts

8.2. Data

8.2.1. Time

8.2.1.1. Does the app use serve time ou phone time?

8.2.1.1.1. If possible, change the time

8.2.2. Contacts

8.2.2.1. If the app request access to contacts make sure

8.2.2.1.1. The contacts are loaded correctly

8.2.2.1.2. From

8.2.3. Language

8.2.3.1. If the app supports multiple languages

8.2.4. Purchase

8.2.4.1. Is the app downloaded from the stores?

8.2.5. Locations

8.2.5.1. Allow the use

8.2.5.2. Turn OFF the GPS

8.2.5.2.1. Observe how the app behaves

8.2.5.3. Try to move around to observe if the location is impacted

8.2.6. Recovery

8.2.6.1. Turn off the connection

8.2.6.1.1. Observe if the data is preserved

8.3. Sound

8.3.1. Validate the sound of the app is listened on

8.3.1.1. Phone speaker

8.3.1.2. Bluetooth headset

8.3.1.3. Wired headset

8.3.2. Turn off the sound of the device and observe the app sound

8.3.3. Increase and decrease volume

8.3.4. Play musics and observe the app sound

9. Vulnerability Analysis

9.1. Does the app using oauth1 or oauth2?

9.2. Does the app saving any information in its memory?

9.2.1. Is it being encrypted?

9.2.1.1. Which kind of encrypt method is being used? MD5, SHA1, BASE64?

9.2.1.1.1. Once the app is using oauth, is needed salt in any part of the data storing?

9.3. Check if the app is vulnerability for any "static check" issue from OWASP report

9.3.1. https://drive.google.com/file/d/0BxOPagp1jPHWYmg3Y3BfLVhMcmc/view

9.4. SSL or TLS is being used to encrypt the data transferred?

9.4.1. Is it really needed?

9.4.1.1. What kind of impact the performance it does?

9.5. All the softwares (APIs, frameworks, services) used to build the app are in the newest version?