Weekend Testing Session 27

06th March 2010

3PM IST to 5 PM IST

Tester: Ravisuriya
Model/Application to be tested: Google Buzz
Test Mission: To generate Test ideas to Test Google Buzz with quality criteria
Performance.
Start Time: 3:05 PM IST (machine time)

Assumptions made while brainstorming:

1. Was not sure what the ‘performance’ means in the test mission.
2. A thought, does the performance mean – “how well was Google Buzz was
performing among with similar other available social networking services”?
3. Or how well the desired purpose of application satisfies the desired claims with given
constraints by processing user actions and its throughput interval.
4. Did assume for this session, the ‘performance’ is how quick and responsive it is.
5. Various users are using Google Buzz at present, with no similar internet connectivity
speed.

Few questions that I got while brainstorming about users and Google
Buzz performance:

1. Performance test ideas in what context?

2. Who are the users and what kind of users are using Google Buzz?
3. How often they have used and using Google Buzz? What are their observations and
perceptions of performance?
4. What devices did they use to browse the Google Buzz? Did this device too have any
influence on their perception of Google Buzz performance?
5. How long did they use Google Buzz in a stretch i.e., without any break?
6. What environment did they have do they have while using Google Buzz? Did it have
any influence?
7. Any tools are used to know or understand the performance parameters of application
under test?
8. How the performance is being measured? What are the units of measurement of
performance in this context?

Mental Modeling:

Testing Google Buzz for the performance (how quick and responsive it is) test ideas as a
tester and not as an end user for this session.
Brainstorming – Session_1

1. Identify the kind of users, their ages, business, purpose, environment, consistency of
using Google Buzz. Few to mention here. This keeps growing as and when
brainstorming and testing sessions is on.
2. Identify the possible and potential contexts with each of this environment
above said.
3. Usage of analytics and log files of Google Buzz. The log files and
analytical information regarding performance of application under test to have time
of request processing and of throughput.
4. Test on various possible hardware and *software configurations and
network topologies. Note: *software and hardware may be that are installed on
device from where Google Buzz is browsed and on Google Buzz server.
5. Does Google Buzz can be accessed by mobile phones? If yes how the configuration
and applications can have influence on time factor with Google Buzz responsiveness?
6. Type of database Google Buzz makes use of.
7. Handling the incorrect or invalid entries. How quick the application is responsive to
user here?
8. How quick does it handle if I keep buzzing with a very **small interval of
gap between two buzz? Note: **small – will be decided on application’s minimum
and maximum tolerance value.
9. Does any other application using internet or network will have influence on Google
Buzz’s performance?
10. Study of features available or provided by Google Buzz. This might give more ideas
how performances tests can be devised.
11. Tests for knowing how the performance of application goes, when number of parallel
users increased and decreased, number of transactions in a given time period varied
to threshold and least, time consumed to recover from these two edges of variations
etc.
12. Performance of application when it’s potential reaches to the extreme. What time it
takes to handle the requests from clients.
13. Type of server being used. Type of connections. Any data stored by application
on client is not stored or stored partially – how the performance of application
goes here.
14. How Google applications being used by user simultaneously along with Google Buzz
choke up the time. Need to identify such application(s) of Google and need to be
tested along with Google Buzz.
15. Other vast applications used over internet and Google Buzz.
16. Maximum requests that can be handled at a given time. (This includes
various actions using various features of Google Buzz).
17. Usage of Google Buzz over ***network that is not comfort for using
of application. Note: ***network – properties of network.
18. If any tools or program used to look into the performance rating of application, what
time is taken by tool to work on this? Does the time taken here by tool or program
instructions have any influence?
19. How the request of client is sent to server?

End Time: 4:10 PM IST (machine time)