Test mobile apps

上一篇 / 下一篇  2014-03-20 15:38:37 / 个人分类:mobile testing

1: definition of a bug

A bug is something that bugs someone who matters

2:Never, under any circumstances, blame yourself for feeling confused by the technology!

(Always remember, technology exists to serve you, not the other way around. Technology should help you do a job, entertain or delight you. It should not make you feel stupid.)

3:First Launch Test

> Locate the icon for the app on you device home or apps screen

.Can you tell what the app does, and what problems it might solve by reading the title and looking at the icon picture?

> Tap the icon to start the app

.Does it load quickly, or does it sit there for a while before you can do anything?

> Examine the splash screen as the application loads

.Does it give you an idea of what the app will do?
.Does it create a positive image of the company?
.How long does the app take to load? Is it reasonable, or does it seem to take too long?

> Once the app loads, stop and look at it carefully

.Does it ask your permission if it needs to use location services, or other privacy features?
.Is the design clean and uncluttered, or overly busy and confusing?
.Can you easily tell what components you can interact with(tap on links, buttons, etc)or are you left wondering what to do next?
.It is obvious to enable features of the app? Can you quickly and easily use the app for the purpose it was intended for, or are you left wondering?

4:Some reasons why delete an app within seconds of installing it:
> The app is difficult to use
> Poor performance - it's too slow
> The app is unreliable, it crashes, freezes up or is inaccurate
> The app is lame - it has a poor visual design and execution
> I am forced into sharing private, personal information with an organization I don't know and trust yet
> App doesn't work as advertised
> The app doesn't provide me with any value over other mobile apps I already have(maps, location, web content, etc.)

4:A Tester's Mindset

Here is a rule of thumb, if something unexpected occurs, don't blame yourself, blame the technology

5:Reporting issues

When starting out testing, there are two simple categories of problems you must report:
> A clear program malfunction occurs(application crashes, freezes, ruins data, provides incorrect results, etc.)
> Something bothers me(annoyances, app or workflows within it are awkward, poor performance, lack of feedback, etc.)

TAG:

 

评分:0

我来说两句

Open Toolbar