GUI Testing的檢查清單
很多QA只會做functional testing, 除了這些之外, 其他種類的測試便不知道要如何進行. 尤其在GUI方面, 因為缺乏資料, 即使有心想做的人也不知道要如何進行. 再加上無人重視, 更不容易會將這項工作納入處理.
這篇是我在網路上, 找到對GUi的檢查清單. 我想這是一份很好的入門指引, 讓你快速瞭解到, 專業的 GUI應該要注意到哪些事情. 你可以把這份清單當做起始點, 然後來建立你自己的知識庫.
Enjoy it!!
GUI Checklist
http://jaanujeeva.blogspot.com/2008/12/gui-checklist.html
1. USER INTERFACE
1.1 COLORS
1.1.1 Are hyperlink colors standard?
1.1.2 Are the field backgrounds the correct color?
1.1.3 Are the field prompts the correct color?
1.1.4 Are the screen and field colors adjusted correctly for non-editable mode?
1.1.5 Does the site use (approximately) standard link colors?
1.1.6 Are all the buttons are in standard format and size?
1.1.7 Is the general screen background the correct color?
1.1.8 Is the page background (color) distraction free?
1.2 CONTENT
1.2.1 All fonts to be the same
1.2.2 Are all the screen prompts specified in the correct screen font?
1.2.3 Does content remain if you need to go back to a previous page, or if you move forward to another new page?
1.2.4 Is all text properly aligned?
1.2.5 Is the text in all fields specified in the correct screen font?
1.2.6 Is all the heading are left aligned
1.2.7 Does the first letter of the second word appears in lowercase? Eg:
1.3 IMAGES
1.3.1 Are all graphics properly aligned?
1.3.2 Are graphics being used the most efficient use of file size?
1.3.3 Are graphics optimized for quick downloads?
1.3.4 Assure that command buttons are all of similar size and shape, and same font & font size.
1.3.5 Banner style & size & display exact same as existing windows
1.3.6 Does text wrap properly around pictures/graphics?
1.3.7 Is it visually consistent even without graphics?
1.4 INSTRUCTIONS
1.4.1 Is all the error message text spelt correctly on this screen?
1.4.2 Is all the micro-help text(i.e tool tip) spelt correctly on this screen?
1.4.3 Microhelp text(i.e tool tip) for every enabled field & button
1.4.4 Progress messages on load of tabbed(active screens) screens
1.5 NAVIGATION
1.5.1 Are all disabled fields avoided in the TAB sequence?
1.5.2 Are all read-only fields avoided in the TAB sequence?
1.5.3 Can all screens accessible via buttons on this screen be accessed correctly?
1.5.4 Does a scrollbar appear if required?
1.5.5 Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
1.5.6 Is there a link to home on every single page?
1.5.7 On open of tab focus will be on first editable field
1.5.8 When an error message occurs does the focus return to the field in error when the user cancels it?
1.6 USABILITY
1.6.1 Are all the field prompts spelt correctly?
1.6.2 Are fonts too large or too small to read?
1.6.3 Are names in command button & option box names are not abbreviations.
1.6.4 Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas “Group Box”
1.6.5 Can the typical user run the system without frustration?
1.6.6 Do pages print legibly without cutting off text?
1.6.7 Does the site convey a clear sense of its intended audience?
1.6.8 Does the site have a consistent, clearly recognizable “look-&-feel”?
1.6.9 Does User cab Login Member Area with both UserName/Email ID ?
1.6.10 Does the site look good on 640 x 480, 600×800 etc.?
1.6.11 Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
1.6.12 Is all terminology understandable for all of the site’s intended users?
Performance & Security Testing Checklist
2. PERFORMANCE
2.1 LOAD
2.1.1 Many users requesting a certain page at the same time or using the site simultaneously
2.1.2 Increase the number of users and keep the data constant
2.1.3 Does the home page load quickly? within 8 seconds
2.1.4 Is load time appropriate to content, even on a slow dial-in connection?
2.1.5 Can the site sustain long periods of usage by multiple users?
2.1.6 Can the site sustain long periods of continuous usage by 1 user?
2.1.7 Is page loading performance acceptable over modems of different speeds?
2.1.8 Does the system meet its goals for response time, throughput, and availability?
2.1.9 Have you defined standards for response time (i.e. all screens should paint within 10 seconds)?
2.1.10 Does the system operate in the same way across different computer and network configurations, platforms and environments, with different mixes of other applications?
2.2 VOLUME
2.2.1 Increase the data by having constant users
2.2.2 Will the site allow for large orders without locking out inventory if the transaction is invalid?
2.2.3 Can the site sustain large transactions without crashing?
2.3 STRESS
2.3.1 Increase both number of users and the data
2.3.2 Performance of memory, CPU, file handling etc.
2.3.3 Error in software, hardware, memory errors (leakage, overwrite or pointers)
2.3.4 Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? Test that the application is able to perform during those conditions. Will downtime be allowed or is that out of the question?
2.3.5 Verify that the application is able to meet the requirements and does not run out of memory or disk space.
2.4 SECURITY
2.4.1 Is confidentiality/user privacy protected?
2.4.2 Does the site prompt for user name and password?
2.4.3 Are there Digital Certificates, both at server and client?
2.4.4 Have you verified where encryption begins and ends?
2.4.5 Are concurrent log-ons permitted?
2.4.6 Does the application include time-outs due to inactivity?
2.4.7 Is bookmarking disabled on secure pages?
2.4.8 Does the key/lock display on status bar for insecure/secure pages?
2.4.9 Is Right Click, View, Source disabled?
2.4.10 Are you prevented from doing direct searches by editing content in the URL?
2.4.11 If using Digital Certificates, test the browser Cache by enrolling for the Certificate and completing all of the required security information. After completing the application and installation of the certificate.
很多QA只會做functional testing, 除了這些之外, 其他種類的測試便不知道要如何進行. 尤其在GUI方面, 因為缺乏資料, 即使有心想做的人也不知道要如何進行. 再加上無人重視, 更不容易會將這項工作納入處理.
這篇是我在網路上, 找到對GUi的檢查清單. 我想這是一份很好的入門指引, 讓你快速瞭解到, 專業的 GUI應該要注意到哪些事情. 你可以把這份清單當做起始點, 然後來建立你自己的知識庫.
Enjoy it!!
GUI Checklist
http://jaanujeeva.blogspot.com/2008/12/gui-checklist.html
1. USER INTERFACE
1.1 COLORS
1.1.1 Are hyperlink colors standard?
1.1.2 Are the field backgrounds the correct color?
1.1.3 Are the field prompts the correct color?
1.1.4 Are the screen and field colors adjusted correctly for non-editable mode?
1.1.5 Does the site use (approximately) standard link colors?
1.1.6 Are all the buttons are in standard format and size?
1.1.7 Is the general screen background the correct color?
1.1.8 Is the page background (color) distraction free?
1.2 CONTENT
1.2.1 All fonts to be the same
1.2.2 Are all the screen prompts specified in the correct screen font?
1.2.3 Does content remain if you need to go back to a previous page, or if you move forward to another new page?
1.2.4 Is all text properly aligned?
1.2.5 Is the text in all fields specified in the correct screen font?
1.2.6 Is all the heading are left aligned
1.2.7 Does the first letter of the second word appears in lowercase? Eg:
1.3 IMAGES
1.3.1 Are all graphics properly aligned?
1.3.2 Are graphics being used the most efficient use of file size?
1.3.3 Are graphics optimized for quick downloads?
1.3.4 Assure that command buttons are all of similar size and shape, and same font & font size.
1.3.5 Banner style & size & display exact same as existing windows
1.3.6 Does text wrap properly around pictures/graphics?
1.3.7 Is it visually consistent even without graphics?
1.4 INSTRUCTIONS
1.4.1 Is all the error message text spelt correctly on this screen?
1.4.2 Is all the micro-help text(i.e tool tip) spelt correctly on this screen?
1.4.3 Microhelp text(i.e tool tip) for every enabled field & button
1.4.4 Progress messages on load of tabbed(active screens) screens
1.5 NAVIGATION
1.5.1 Are all disabled fields avoided in the TAB sequence?
1.5.2 Are all read-only fields avoided in the TAB sequence?
1.5.3 Can all screens accessible via buttons on this screen be accessed correctly?
1.5.4 Does a scrollbar appear if required?
1.5.5 Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
1.5.6 Is there a link to home on every single page?
1.5.7 On open of tab focus will be on first editable field
1.5.8 When an error message occurs does the focus return to the field in error when the user cancels it?
1.6 USABILITY
1.6.1 Are all the field prompts spelt correctly?
1.6.2 Are fonts too large or too small to read?
1.6.3 Are names in command button & option box names are not abbreviations.
1.6.4 Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas “Group Box”
1.6.5 Can the typical user run the system without frustration?
1.6.6 Do pages print legibly without cutting off text?
1.6.7 Does the site convey a clear sense of its intended audience?
1.6.8 Does the site have a consistent, clearly recognizable “look-&-feel”?
1.6.9 Does User cab Login Member Area with both UserName/Email ID ?
1.6.10 Does the site look good on 640 x 480, 600×800 etc.?
1.6.11 Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
1.6.12 Is all terminology understandable for all of the site’s intended users?
Performance & Security Testing Checklist
2. PERFORMANCE
2.1 LOAD
2.1.1 Many users requesting a certain page at the same time or using the site simultaneously
2.1.2 Increase the number of users and keep the data constant
2.1.3 Does the home page load quickly? within 8 seconds
2.1.4 Is load time appropriate to content, even on a slow dial-in connection?
2.1.5 Can the site sustain long periods of usage by multiple users?
2.1.6 Can the site sustain long periods of continuous usage by 1 user?
2.1.7 Is page loading performance acceptable over modems of different speeds?
2.1.8 Does the system meet its goals for response time, throughput, and availability?
2.1.9 Have you defined standards for response time (i.e. all screens should paint within 10 seconds)?
2.1.10 Does the system operate in the same way across different computer and network configurations, platforms and environments, with different mixes of other applications?
2.2 VOLUME
2.2.1 Increase the data by having constant users
2.2.2 Will the site allow for large orders without locking out inventory if the transaction is invalid?
2.2.3 Can the site sustain large transactions without crashing?
2.3 STRESS
2.3.1 Increase both number of users and the data
2.3.2 Performance of memory, CPU, file handling etc.
2.3.3 Error in software, hardware, memory errors (leakage, overwrite or pointers)
2.3.4 Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? Test that the application is able to perform during those conditions. Will downtime be allowed or is that out of the question?
2.3.5 Verify that the application is able to meet the requirements and does not run out of memory or disk space.
2.4 SECURITY
2.4.1 Is confidentiality/user privacy protected?
2.4.2 Does the site prompt for user name and password?
2.4.3 Are there Digital Certificates, both at server and client?
2.4.4 Have you verified where encryption begins and ends?
2.4.5 Are concurrent log-ons permitted?
2.4.6 Does the application include time-outs due to inactivity?
2.4.7 Is bookmarking disabled on secure pages?
2.4.8 Does the key/lock display on status bar for insecure/secure pages?
2.4.9 Is Right Click, View, Source disabled?
2.4.10 Are you prevented from doing direct searches by editing content in the URL?
2.4.11 If using Digital Certificates, test the browser Cache by enrolling for the Certificate and completing all of the required security information. After completing the application and installation of the certificate.
