Are you going to start on a new project for testing? Don’t forget to check this Testing Checklist in each and every step of your Project life cycle. List is mostly equivalent to Test plan, it will cover all quality assurance and testing standards.
Testing Checklist:
1 Create System and Acceptance Tests [ ]
2 Start Acceptance test Creation [ ]
3 Identify test team [ ]
4 Create Workplan [ ]
5 Create test Approach [ ]
6 Link Acceptance Criteria and Requirements to form the basis of
acceptance test [ ]
7 Use subset of system test cases to form requirements portion of
acceptance test [ ]
8 Create scripts for use by the customer to demonstrate that the system meets
requirements [ ]
9 Create test schedule. Include people and all other resources. [ ]
10 Conduct Acceptance Test [ ]
11 Start System Test Creation [ ]
12 Identify test team members [ ]
13 Create Workplan [ ]
14 Determine resource requirements [ ]
15 Identify productivity tools for testing [ ]
16 Determine data requirements [ ]
17 Reach agreement with data center [ ]
18 Create test Approach [ ]
19 Identify any facilities that are needed [ ]
20 Obtain and review existing test material [ ]
21 Create inventory of test items [ ]
22 Identify Design states, conditions, processes, and procedures [ ]
23 Determine the need for Code based (white box) testing. Identify conditions. [ ]
24 Identify all functional requirements [ ]
25 End inventory creation [ ]
26 Start test case creation [ ]
27 Create test cases based on inventory of test items [ ]
28 Identify logical groups of business function for new sysyem [ ]
29 Divide test cases into functional groups traced to test item inventory [ ] 1.30 Design data sets to correspond to test cases [ ]
31 End test case creation [ ]
32 Review business functions, test cases, and data sets with users [ ]
33 Get signoff on test design from Project leader and QA [ ]
34 End Test Design [ ]
35 Begin test Preparation [ ]
36 Obtain test support resources [ ]
37 Outline expected results for each test case [ ]
38 Obtain test data. Validate and trace to test cases [ ]
39 Prepare detailed test scripts for each test case [ ]
40 Prepare & document environmental set up procedures. Include back up and
recovery plans [ ]
41 End Test Preparation phase [ ]
42 Conduct System Test [ ]
43 Execute test scripts [ ]
44 Compare actual result to expected [ ]
45 Document discrepancies and create problem report [ ]
46 Prepare maintenance phase input [ ]
47 Re-execute test group after problem repairs [ ]
48 Create final test report, include known bugs list [ ]
49 Obtain formal signoff [ ]
Source: Jarvis and Crandall, Inroads to Software Quality, Prentice-Hall, 1997, p. 323.
38 comments ↓
Very Very useful information for any QA Engineer
aspiring to climb the ladder in testing
It is very helpful site for the QA and QC teams.
And thanks for all;
Hi ,
I want Weekly status report format and bug reports format, if anybody have plz send to my mail id
regards
Tirru
Hi All,
Plz anybody send me the Format or Template for Test Scenarious. I need to write test scenarious for my new project.
My Mail Id is : thirust5@gmail.com
plz help me out, send me ASAP
regards
TIRRU
Well Thiru ,
As such there is no template . Every company has its own format and that is confidential.
You can create your format where in you can the scenario ( What are you testing ) and the outcome of that
hai
my name is shamith, i want formats of testing reports
This is an very very important article for test engineers
This is very useful for Test engineers
Hello
i want total guideline @ testing interview.
i hv 0 exp in testing n will face interview first time so pls help me.i want to do job.u can contact me
contact me on dikshapatil@gmail.com
Hi,
I have 3.5 years exp in manual testing. I had 1 year gap due to health reasons.
Now from past 3 months I am searching for job I am not getting any calls at all.
Can any one help me please? Are there no such manual testing openings or because of 1 yr gap I am not getting job?
hi friends,
Plz anybody send me the real time process of qtp and one small sample script, my mail id is venki.cnr@gmail.com
regards,
venki.
Very helpfull site
Hi ,
I want manual testing faq’s and some sample tst case’s , if anybody have plz send this my mail id
vickyultratech@yahoo.com .
regards
vicky
Very Useful
Send Details for checklist for smoke testing ,functional testing, validation testing ,GUI testing, browser testing, regression testing,web testing,
@ dikshapatil@gmail.com
it very simple go through all testing term and SDLC,TLC,BLC,Status Report .You could bag more jobs..
Cheers!!
Rahul Kumar
I want to know are B.Com Graduates are suitable for testing field,or can they opt software testing are their carrear,pls do the need full
Please anybody send me GUI checklist .
I really need and example of a GUI checklist…. Anyone out there has one?
I really need and example of a GUI checklist…. Anyone out there has one? Or where I can turn to get one..
Sir,
I wish to be emailed notes on Manual Testing and Interview questions for manual testing. ……..Also I have shifted from a NOn-IT work-environment to IT industry in Testing…….is it necessary for me to certify myself as CSTE before I get good opprtunities.. I have been trying for the past one year……but I have not been able to get into any good Organisation
QA will reject the application wholly and the product will be sent back to development accompanied with a full report as to why the rejection occurred.Is there any document template for the report to be given to the development team when the build is rejected?
Send Details for checklist for smoke testing / sanity testing / BVT (Build Verification Testing)?
Hi,
Friends…
Please give me the template of Traceability Matrix..
If anybody have…
This is my email_id kasappasutar@gmail.com
GUI check list
User Interface Testing Checklist
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.9 Does the site look good on 640 x 480, 600×800 etc.?
1.6.10 Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
1.6.11 Is all terminology understandable for all of the site’s intended users?
Performance & Security Testing Checklist
1. PERFORMANCE
1.1 LOAD
1.1.1 Many users requesting a certain page at the same time or using the site simultaneously
1.1.2 Increase the number of users and keep the data constant
1.1.3 Does the home page load quickly? within 8 seconds
1.1.4 Is load time appropriate to content, even on a slow dial-in connection?
1.1.5 Can the site sustain long periods of usage by multiple users?
1.1.6 Can the site sustain long periods of continuous usage by 1 user?
1.1.7 Is page loading performance acceptable over modems of different speeds?
1.1.8 Does the system meet its goals for response time, throughput, and availability?
1.1.9 Have you defined standards for response time (i.e. all screens should paint within 10 seconds)?
1.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?
1.2 VOLUME
1.2.1 Increase the data by having constant users
1.2.2 Will the site allow for large orders without locking out inventory if the transaction is invalid?
1.2.3 Can the site sustain large transactions without crashing?
1.3 STRESS
1.3.1 Increase both number of users and the data
1.3.2 Performance of memory, CPU, file handling etc.
1.3.3 Error in software, hardware, memory errors (leakage, overwrite or pointers)
1.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?
1.3.5 Verify that the application is able to meet the requirements and does not run out of memory or disk space.
1.4 SECURITY
1.4.1 Is confidentiality/user privacy protected?
1.4.2 Does the site prompt for user name and password?
1.4.3 Are there Digital Certificates, both at server and client?
1.4.4 Have you verified where encryption begins and ends?
1.4.5 Are concurrent log-ons permitted?
1.4.6 Does the application include time-outs due to inactivity?
1.4.7 Is bookmarking disabled on secure pages?
1.4.8 Does the key/lock display on status bar for insecure/secure pages?
1.4.9 Is Right Click, View, Source disabled?
1.4.10 Are you prevented from doing direct searches by editing content in the URL?
1.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, try using the
Hi Very nice keep post like this.
Hi
It’s a good article on Testing stuff. I enjoyed reading this one.
Hi friends,
If anybody is having idea about MANTIS(defect tracking tool).Please give some idea about that.It will be very helpful to me.
Regards,
Usha.
pls. can anyone help in helping secure a testing job, am new to this IT work environment, and i’ve been sending my CV since march 2008, but till date i haven’t got a single call, what is the key break into this IT industry, pls. help. Loads of thank you
very very very useful article for every tester.
Hey..
This will be useful material who are working as a fresher as well as Experience.
Nice site.
cool.
usha:
hey usha
go through http://www.testingfaqs.org/t-track.html link for MANTIS
Thank you so much to Charita for posting the GUI checklist. I had been looking for something similar to build on and this list is a life saver, exactly what I was looking for. Thanks!!!!
Hi Everybody,
I have seen this site recently.
this is very nice site to the learners and who wants to share their knowledge.
Thanks alot for everyone who participate in this site.
Hi
I would like to learn software testing by own.
please give suggestions how to start it and how to plan to study the concepts.
It’s very urgent.
please help me.
Hi All,
When developer release product to tester team before that from developer point of what parameters has to check from developer end . I want that check list for Developer & after that tester what to do next .
Can i have both check list for Developer as well as Tester.
Pls send me on my mail id if anybody have.
Darshan
Leave a Comment