1. Monkey test:
Question: Please write a monkey designation according to your needs, designate a model to run, generate the most detailed log, continue to run after failure, the number of runs is 1000, and save the run results in the D drive
Answer: adb -s 9889db35304c304137 shell monkey -v -v -v -p camera.pro --ignore-security-exceptions 1000 >d:\monkey.txt: After the failure, continue to run the log and save it on the D drive
2. Time test:
Q: If the WEB test is free of login within 7 days, 15 days without login, and 1 month without login, how should the test be tested?
Answer: First confirm the three implementation details:
1. When calculating the date, is the time calculated according to the server time, database time, user's local time or other calculations?
2. How is the exemption of login realized? Is it Cookie or Session?
3. Is the calculation calculated in hours, minutes and seconds or in whole days?
Test point:
Take 7 days as an example
1. Choose to avoid login within 7 days, log out after logging in and log in again, whether it is exempt from login
2. Choose to log in without login within 7 days, log in on the seventh day after login, whether to log in free
2. Choose to avoid login within 7 days. After login, log in on the eighth day. Whether to avoid login
4. Consider testing across weeks
5. Consider testing across months (28 days, 29 days, 30 days, 31 days)
6. Consider New year’s test
7. Re-log in manually during the free login period to confirm whether the validity period of the free login is updated.
8. Cache test (clear cache, overwrite installation, uninstall installation, etc.)
The methodology involved:
1. Equivalence class division method
2. Boundary value method
3. Error speculation method
3. High quality defect report:
Q: How to submit a high-quality defect tracking form
Answer: First of all, it must be clear that the defect tracking list is not only for yourself, so the most important criterion for a high-quality defect list is that others can understand it at first glance, the title is concise and clear, and the steps are clear.
It is also necessary to consider the completeness of the defect, such as defect level, belonging function module, version, reproduction steps, expected result, actual result, cause, log screenshot, etc.