Black box test from System test to app test

From August 15-to date, from system testing to app testing has been April, afraid to forget the short-term system test results, in this contrast the similarities and differences:

First, the focus is different

System test:

1, the system built-in app function is stable, no flash back and other bad phenomenon

2, the system is stable, does not appear black screen, freezing, lag phenomenon, the use of smooth

3, response time, power consumption to meet the requirements

4. Boot time

5, the system comes with the function of the settings are normally available, testing should be aware of settings and built-in apps and other features do not conflict

6, can be normal switch machine, the test should consider abnormal power, shutdown restart, lock screen restart and other phenomena

7, the system needs to do performance testing, before often with An and other software to do performance testing

8. Simple stress test (whichever is the number of clicks)

9, compatibility testing, mainly from the current mainstream market download different apps, in the system to do simple function traversal, to see if compatible

10, upgrade test, to build their own data-based, upgrade, check whether the data is still saved

11, internal app interference with each other, whether normal

App Test:

1, the app needs to test front-end UI, function, background interface

2, combined with the device's own settings, such as network, gestures, calls, etc. for testing

3, upgrade test, need to consider background database upgrade, Web upgrade, front-end upgrade is normal

4, compatibility testing needs to consider: different devices, different systems and versions, equipment other items, new background for the old front end, iOS and Android interaction, etc.

5, non-mainstream app performance test can be a little bit after the test, and so on when the user reaches a certain number of applications online, and then as a key test item

Second, the test method is different

System test:

1, before the test is YunOS system, similar to Android system, you can use the ADB command to collect log, using monkey run stability

2, response time and power consumption testing, third-party software-based, automated testing

App Test:

1, currently mainly in the Andorid and iOS two systems for testing, no use of app automation testing tools, manual function testing mainly

Three, case writing method is different

System test:

1, the system is relatively stable, testers in 6-8, each responsible for only a few modules

2, for the module, detailed writing case, including every step of execution

App Test:

1, the demand changes, the test staff of 1

2, the test task is heavier, the use of a relatively simple test method, did not write a detailed test case, with a mind map in lieu of set of case

3, the exploratory test, easy to forget the test steps, reverse thinking test in case form, to prevent the test time is too tight and forgotten

Open a deserted: when testing, the more afraid to test that piece or deliberately avoid which piece, there must be a problem

Iv. Similar project flow

Analyze requirements--basic unit tests--modular testing--comprehensive test-and-upgrade testing

↓↓↓↓

——— bug submission, tracking, Management ————— > Release--Project Wrap-up

Testimonials: Although know their own style can not, knowledge reserves is not enough, but still bite the bullet to write this article, hope to see themselves a little progress. Every time you read it, you know what you're missing and what you need to fill.

Transfer from Testtao

Black box test from System test to app test