Summarize and summarize the key nodes of bugs that often appear in the
Android
APP
test
process , I hope it will be helpful to everyone!
start up:
1. Startup entry: the desktop starts normally, the most recent operation starts, it starts in the list of all programs, and the lock screen starts quickly.
2. Other entrances: open the application from other programs, open the application as a file from the outside (if any)
3. Return: When returning from other programs, return to the application under test, and the application under test opens other applications and then starts from the desktop icon
The above requires cross-combination testing.
4. Abnormal start: start after crash, start after being forced to kill the process when writing a file, start after forcibly killing the process when the network request does not receive a return packet, start when the network times out (start needs to have a timeout mechanism)
Function introduction, guide map, traffic tips, etc.:
1 When the new installation program is started for the first time, there will be some initialization, or pop-up prompts, and function introduction. When the external opening, such as a third-party opening (generally not counted as the first startup), start the program and check the actions. Are there any.
Permissions:
1 When certain permissions are prohibited by security software or the system, can they be used normally? Permissions that need to be paid attention to: permissions such as microphone/camera/location/short message—_luguo
2 When doing compatibility testing, you need to pay special attention to Rom with strict permission management, such as Meizu's camera and other permissions are closed by default
3 When the third-party security software pop-up box requests permission to prohibit, after selecting, will it affect the normal process of the application under test?
file error
1 Use the wrong file type (but with the correct suffix) instead of the file used by the app under test
2 adb push If the file uploaded from the pc to the device has a Chinese name, an incorrect file will be generated, and the application under test needs to adapt to this error situation
Screen rotation:
1 Confirm which interfaces need to allow horizontal screen or prohibit horizontal screen
2 Lock the screen to portrait or landscape, and jump between several interfaces. Is the interface normal?
3 When adapting to landscape, whether to adapt to landscape
flow:
1 Whether the traffic on the first launch of the app is as expected
2 When there are many pictures in the main interface, whether the balance between picture file size and display effect has been reached
3 When large network traffic needs to be used (loading large pictures, buffering video playback, downloading update packages), it displays the current network speed or progress, which is more user-friendly
Cache (/sdcard/data/com.your.package/cache/):
1. After uninstalling, the cache will be deleted, whether there are files that should not be deleted (download files, user data)
2. The cache is easy to be cleaned by
360
Mobile
Guard, Cheetah Clean Master, etc. It is necessary to check whether the folder contains suitable files
Normal interrupt:
1. Perform the lock screen operation on all interfaces, and check whether it works normally after unlocking
2. Perform a long-time lock screen operation on all interfaces, and check whether it works normally after unlocking
3. In all interfaces and all processes, press the home button to switch to the background, and then switch back to observe whether it is normal
4. During all loading processes, press the back key
5. During all loading processes, press the home button
6. Try pressing the back key multiple times when the interface switches animations
7. Normal click action, try pressing twice quickly
8. The rear camera and the front camera cannot be activated at the same time, and the activation of the rear camera also includes turning on the flash (compatibility with flashlight applications)
9. Check the timing of opening and closing the keyboard, and test it in combination with home, back, and lock screen
10. After starting from a third party, return the home button to the desktop, and then open the application under test from the desktop to see if the display is correct (it should be determined whether to display the third-party startup interface or the normal startup interface of the program, the former such as WeChat, the latter such as QQ )
Abnormal interruption:
1. Restart after power off
2. When the interface crashes unexpectedly, is it possible to restart the interface and restore it to the state before the crash
3. After the call ends, return to the application interface under test
4. 在某些特殊情况下，来电后，移动网络会被切断
用户体验：
1. 以最挑剔最无理的用户角度来使用应用的主打功能
2. 是否每个动作都有反馈
3. 每个按钮都有按下的状态
4. 当界面有返回按钮时，back将执行同样的操作
5. 当图片需要网络拉取，或者无图片时，是否有默认图片替代
6. 开启开发者选项，勾选显示布局边界，检查每一个按钮的可点击范围是否合理
多语言：
1. 其他语言的语言习惯（如繁体）
2. 英文注意复数
3. 多语言下，需要特别检查以图片形式展示的文案（如果功能引导，启动引导图）
4. 一致性。（一方面是代指的一致性，一方面如果有系列应用共用功能的文案也需要保持一致）
5. 如果在简体下载了一个文件or创建了一个快捷方式or进行了一笔购买，马上切换语言去做一次同样的动作
6. 检查英文语言下的切断、断行是否正确
7. 当文字长度不一致时，UI界面是否能正常适配
升级：
1. 是否有完整的升级策略（强制升级，灰度发布）
2. 下载升级包过程中是否可以取消
3. 升级包下载是否可以续传
4. 升级过程是否可以中断（取消按钮，back键）
5. Android系统第一次安装非官方市场应用，需要手动取消限制，此过程是否会影响到apk包安装（正对预装应用的测试）
6. 在没有更新或者网络时，需要给予用户正确的信息表达
7. 如果升级有忽略本次版本升级，那么当有新的升级版本时，是否还有提示升级
8. 收到升级提示后，下载了apk并未安装，同名替换该apk，下次再收到升级提示后，是否正常升级
应用外部升级：
1 应用如果是跳网页下载安装包升级，需要在文件名加版本号或者标识，防止
浏览器下载时有缓存，而无法安装最新版本—_luguo
2 交由系统下载升级安装包，尝试进行两次版本升级
列表：
1. 列表中的文字长度超过限制
2. 点击列表项返回后的列表项的状态变化（尤其在有多个进度条存在时，需要注意状态）
3. 上下滑动时，是否可接受卡顿（帧率）
双卡双待：
1. 当手机为双卡双待时，影响到的功能有：需要获取手机号码的功能，如支付；自动读取短信息
网络：
1. 是否以较好的体验从网络问题导致的数据问题中恢复界面展示数据
2. 是否每个需要网络请求的操作，都有做超时处理，并且测试出他的超时时间
3. 检查每一个需要网路请求的动作在网络延迟，服务器发生错误时，界面的响应
monkey测试：
1. 必跑monkey，不要仅跑一次，不要到测试后期才跑
2. 更换不同的界面和不同的参数跑monkey
3. 记得
记录所有日志，如果能有日志筛选的工具更好
性能测试：
1. cpu占用，内存，流量，耗时等数据，必须有标准和参考值（可以是市场上同类应用的类似操作的表现，或者同应用的不同版本测试）
2 特定操作（一般为主打功能）的
压力测试，一般长时间大批量执行某个动作或者组合，尤其为该动作是通过JNI实现，或者使用了其他第三方sdk。一般写脚本或者录制脚本。
病毒检测：
1. apk文件在PC杀软上检测
2. 手机杀毒软件检测
如果对软件测试有兴趣，想了解更多的测试知识，可以加入我的QQ群 高级测试学习大家庭：652068511
如果对软件测试有兴趣，想了解更多的测试知识，可以加入我的QQ群 高级测试学习大家庭：652068511