Specific requirements: have an account, a password input box, a submit button, study purposes
1. Understand the needs of
2. Whether the ability of Design Example
3. Are familiar with the various test methods
4. Is there a wealth of experience in testing web
1. Understand the requirements:
Test requirements analysis process can start from the quality requirements, to expand the testing requirements analysis, from the various quality features, performance, security and compatibility requirements, the continued refinement of its contents, tap the corresponding test requirements, covering quality requirements, available from development needs, to break down each development requirements for the test items, combined with the quality requirements, these test items then broken down into test tasks, including functional testing tasks and non-functional testing tasks, while finishing the test requirements, need to be classified , refinement, combined and arranged according to the priority list of test requirements formed
1> login screen should pop-up, or displayed directly on the inside pages
2> length account and password (eg: length, case sensitive, special characters mash)
3> whether the interface is beautiful with special needs (UI test)
Example 2. Design:
function test:
1> Enter the correct user name and password, click on the submit button to verify whether the correct login
2> enter the wrong user name or password, click on the submit button to verify that the login fails, an appropriate error message prompts
3> After a successful login can jump to the correct page
4> account name or password is too long or too short, how they deal with (security, password is too short if prompted)
5> account and password with special characters (spaces), whether made filter
Whether 6> Encryption display
7> to enter a password, uppercase keyboard open time to have prompt information
8> input nothing, just click submit (non-null check)
9> After the login fails, you can not remember the password function
10> Lost Password login page links to jump correctly, etc.
11> involve verification code, but also consider whether the distortions caused by excessive text large difficult to identify
UI testing:
1> is reasonable layout, a two textbox and buttons are aligned
2> textbox length and height meet the requirements
3> interface design and UI design style is consistent
4> interface written in simple and easy to understand, no typos
Performance Testing:
1> Open the login screen, take a few seconds
2> enter the correct user name and password, the login is successful jump to a new page, you need a few seconds
Security testing:
1> cookie after a successful login if there HttpOnly (to reduce the risk of script)
2> account number and password are encrypted by the way, is sent to the web server
3> Verify the account and password, and server authentication should be used, not just on the client side validation with javaScript
Input box 4> account number and password, should be shielded SQL injection attacks
5> account and password input box, enter the script should be banned (to prevent XSS attacks)
6> limit number of errors logged (to prevent brute force)
7> whether to support multi-user login on the same machine
8> a user is logged on multiple machines
Usability Testing:
1> if the input box can be toggled with the tab key
2> enter the account number, password and press Enter, you can log on
3> is available with a full keyboard, if there are shortcuts
Compatibility test:
1> under the mainstream browser can display normal function has been normal
2> different platforms if it works, eg: windows, mac
3> is working on a mobile device, such as iPhone, Android
4> different resolutions