Testing the Google calculator

– If the big concern here is that testing would take a long time, break tests up into multiple jobs that rub across different servers simultaneously. You can run each input in parallel so you’re done in a fraction of the time it would take to run each test one after another on one machine.
– focus on the most frequently used functionality (Do most people convert Fahrenheit to Celsius? Or USD to GBP? Make sure your test coverage there is in-depth)
– focus on the most “risky” functionality. What are the most complex calculations? Make sure those are working correctly.
– Performance: make sure the calculator is performant when you’re doing large calculations, or many calculations at once
– Who are your customers? Are most users from China? US? Make sure you test extensively with their local currency, numbering systems, etc.
– Test each type of input and its edge cases: extremely small values (negative numbers), extremely large values (max value), zero (divide by zero), currency exchange while values are changing throughout the day, etc.
– test in different browsers: IE, Chrome, Firefox, Waterfox. Old versions, new versions. (if you care about old versions)
– Verify non-English numbers work (Right-to-left Arabic numbers, for example)
– Verify that the calculator’s UX is usable and that people are able to find the different functionality – otherwise a lot of your functionality might never even get used.
– Even though there’s a lot of possible inputs, are there important new ones that are missing?
– Are there inputs that no one ever uses that you should remove?
– Geopolitical issues: are there culturally-offensive aspects to the calculations, design, etc. that would cause people to stop using your product?
– Documentation: how do people find out about the different inputs that are supported?
– accessibility: are users without a mouse able to use their keyboard to navigate the page? are screenreaders supported/functional for blind users?
– heavy traffic: is the calculator still functional when millions of people are using it at the same time? What if a DDOS attack is causing a performance hit? Would you prefer to have the calculator “go dark” for a short period of time until activity returns to normal, or have some users be able to access the service and experience bad performance?
– competetive analysis: does someone else have a better calculator? How is ours better/worse than the competition?
– customization: can users who select the same inputs over and over have a setting that saves a default for them so they don’t have to keep changing to the input they want?



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s