Testing check list
-
Upload
sudheer-pridhvi -
Category
Documents
-
view
225 -
download
0
Transcript of Testing check list
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 1/25
S.No
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 2/25
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 3/25
Software Requirements
Does each requirement specify only one thing?
Do all parts of the requirement belong together
Is each requirement self contained with no missing information?
If the requirement is not a part of the current release, then is it specified as completely and as thoroughly as is curren
Are separate requirements specified separately?
Is each requirement semantically correct (i.e., have the correct meaning) ?
Is each requirement syntactically correct (i.e., have the correct form)?
Is each requirement phrased in the language of the appropriate stakeholders (e.g., members of the customer and user
Does each requirement only specify behavior and/or characteristics that are externally observable when treating the s
Can each requirement be implemented given the existing hardware or software technology?
Can each requirement be implemented given the endeavor’s:Budget,Schedhule,Constraints on staffing?
Does each requirement has Clear and precise meaning
Does each requirement Objective has meaning
Does each requirement has Single interpretation
Does each requirement has Understandable meaning
Does each requirement has Concrete terms
Does each requirement avoid vague words and phrases
Is each requirement specified in a quantitative manner whenever possible and practical?
Does each requirement include all necessary conditions
Does each requirement associate with the Quality factor
Are the Abbreviations, acronyms, and/or technical terms of the requirement defined.
Are the reference associated with requirement, if present should be explicit, precise, and unique
Is the requirement conflicting with other software requirements or with system or business requirements?
Has the customer verified this requirement?
Is there any design dependency in the requirement?
Is the requirement in consistence with corresponding system requirement?
Can the requirement be traced to higher-level system requirement, a use case, or a voice-of-the-customer statement?
Can the requirement be traced to design elements, source code, and test cases that are constructed to implement and
Is the requirement priority established by customers/ users?
Is each requirement essential to the success of the system, application, or component under development?
Is each requirement truly necessary (i.e., a true requirement that must be met and implemented)?
Is each requirement truly required by a legitimate stakeholder that is authorized to mandate requirements (e.g., the c
Is each requirement free from unnecessary constraints (e.g., architecture, design, implementation, testing, and other
Does each requirement specify a “what” (e.g., functional, data, or interface requirement) or “how well” (e.g., quality
Is each requirement usable by the customer representatives and user representatives who must use it for scope control
Is each requirement usable by managers who must use it for scope control as well as cost, schedule, and progress metri
Is each requirement usable by the designers and programs who must implement it?
Is each requirement usable (e.g., testable) by the testers who must verify and validate it?
Is there an appropriate verification method (e.g., demonstration, evaluation, testing) for each requirement?
Can each requirement be verified against its source?
Can each requirement be verified against its associated standards (e.g., content and format), guidelines, and/or templ
Is it possible to ensure that each requirement is: Actually needed by some legitimate stakeholder,Acceptable to the cu
Is each requirement allocated to the team or individual who will implement it?
Are all significant assumptions associated with each requirement properly documented?
Does each requirement have its own unique identifier that can be used for tracing purposes?
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 4/25
When lists should be used, are numbered lists used instead of bulleted lists?
Is each requirement not redundant with any other requirement at the same level of abstraction (e.g., within the same
Is each requirement prioritized for scheduling and trade-off purposes?
Does each requirement have a reasonable rationale associated with it that justifies it being specified as a requirement
Is each requirement scheduled for implementation by a specific milestone or release?
Is this schedule based on the priority of the requirement?
Does each requirement have an associated status (e.g., identified, analyzed, specified, approved, and frozen)?
Is this status updated as the requirements goes through its lifecycle?
Is each requirement traced to its source goal, document, person, team, and/or organization?
Does each requirement include both forward and backward tracing information?
Does each system requirement include a trace back to system goals?
Does each system requirement include traces down to data, hardware, personnel, and software:
Does each software requirement include a trace back to its system component and system requirements?
Does each software requirement include traces down to data, hardware, personnel, and software components?
. ., ,Implementation precedence,The minimization of project risk?
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 5/25
Y/N/NA Comments
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 6/25
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 7/25
S.No Static testing Y/N/NA
1
2
3
4
5 After the static testing, the document need to be udpated as per the changes
6
7 Have You followed the process below
Have important interfaces to all system elements been described?
Have all data objects been described? Have all attributes been identified?
Have functions been refined (elaborated) to an appropriate level of detail?
Is information flow adequately defined for the problem domain?
Are diagrams clear; can each stand alone without supplementary text?
Have events and states been identified?
Are design constraints realistic?
Have technological risks been fully defined?
Have alternative software requirements been considered?
Are you with IT-BA, Business and Project manager with the requriements thathave been finalized or signed off
Do you development team with you while you review or walkthru the
requirements? If yes where are they are located locally or remotely
As a tester what are the main parameters, you are looking into therequirements? If you used any pls elaborate
Testers, parallely need to correlate, the requirements that can be testable.In terms of traceability of the test cases that they are going to write against
the requirements
A formal sign off after the requriements gone thru the static testing phase byall in presence of Business, Development, Testing, PM.
Do stated goals and objectives for software remain consistent with systemgoals and objectives?
Do major functions remain within scope and has each been adequatelydescribed?
Is the behavior of the software consistent with the information it mustprocess and the functions it must perform?
Have validation criteria been stated in detail; are they adequate to describea successful system?
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 8/25
Have inconsistencies, omissions or redundancy been identified and corrected?
Is the customer contact complete?
Has the user reviewed the Preliminary User's Manual or prototype?
How are the Software Project Plan estimates affected?
When a calculation is specified, work at least two examples.
clearly, obviously, it follows that), ask why? most, mostly); ask for clarification.
Keys to look for: "etc., and so forth, and so on, such as." range from 10 to 100. Integer? Real? Hex?)
eliminated." There are many ways they can be interpreted. data validation module and its control flag is set. Whose control flag?)
never), then ask for proof. for other occurrences of the term
understanding.
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 9/25
Comment
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 10/25
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 11/25
S.No Unit testing Y/N/NA
1 Are the Unit test cases are written prior to the start of coding
2
3 Are the Unit test cases are written in the template that are currently in usage
4 Are the Unit test case data is ensured to be available for testing
5 Does the Unit test data should cover for postive & negative scenarios
6
7
8
9 Did your Unit testing artifacts are stored and preserved for Audits
10
11 Did you plan to automate the Unit test cases?
12 When debugging a issue, are you creating new unit test cases?
13 Does your code has been complied without errors before review
14 Are your unit test cases have been reviewed
15 Are you providing your unit test cases to Regression suite?
Are Unit test cases are written based on the final signed off techinicalspecification
Does the unit tests is based on the White Box techniques, these include code,branch and check based on LoC
Does the development environment meets the current expectations in terms of Hardware/Software
Does the Deployment strategy document has been completed after the Unittesting is completed
Did all the open issues found during the Unit testing are closed prior the build ismoved for Testing
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 12/25
Comments
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 13/25
S.No Integration testing
1
2
3
4
5 Did you close all the pending issues that are found during the Integration testing
6
7
8
9 Are Integration testing test cases been reviewed and updated
10
All the Integration test cases are written with the template that are currently in use, If no template available, Intelligoup can be provided
All the Integration test cases should cover end to end scenarios, that is spreading more
than one module and also covers the third party tools as well as the Interfaces
Integration test data is need be ready for testing, since data required for integrationtesting is voluminous and also it is cross modular, we suggest that there need to be a
support from Application support team . Did you have the support
All the integration test cases need to reviewed before they get signed off or before theexecution, by business as well as Service Mangers, who system is getting impacted. Has
these been signed off
Did you get the closing orders of Unit testing from developers for continuing theintegration testing
Ensure any open issues that are identified need to be closed before the code moves forSystem testing
Does the development environment meets the current expectations in terms of Hardware/Software for Integration testing
Are Integration test cases baselines and stored for future usage in building theregression test suite
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 14/25
Y/N/NA Comments
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 15/25
S.No System testing Y/N/NA Comments
Entry Criteria
1 Did you evidence that All the code of the application has been unit tested
2
3
4
5 Have you done Smoke testing?
6
7 What are the testing techniques, you followed, If yes pls provide evidence
Exit Criteria
8 All the test cases have been completed in execution
9 All the defects found during this phase have been retested and closed
10
10 All relevant test documents are in place
11
13If you had the report, has it been submitted to Business
14
13 Have you retested all your defects, If yes pls provide evidence
14
15
Do you have evidence that all the code has been build for the applicationunder test
All your test plan, test cases have been reviewed and approved. Thesetest cases has traceability to the requirements. Do you have the evidence
Test environment/test ware get prepared for the application testing. Isthe software/hardware been in sync with production. Is the test database
been refreshed
Do you have valid test data ready for the testing activities. Has this databeen verified by the Business
Ensure the test cases have been covered as per the requirements. Plsprovide the evidence
Do you have the final test summary report is ready. If yes, pls provideevidence
Did you your defects, mapped with Test cases and requirements, if yespls provide evidence
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 16/25
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 17/25
S.No Performance testing
1 Did you have Performance requirements defined by Business?
2 Did you build the test scenarios for the Performance testing?
3 Are these test scenarios validiated by Business against the performance requirements?
4
5
6
7
8 When was performance testing is done? Is before UAT or After or In Parallel
9 Did you had Performance Objectivies
10 Did you have Set pass/fail criteria
11 Did you Establish profiles of expected real users
12 Did you Create test scripts and executed by yourself
13 Did you Identify targeted transaction volumes and user mix
14 Did you Identify SLA in terms of through put or response times
Are you inolved during the feasbiliy phase to understand, how the system meets theperformance criteria
What are the different performance testing techniques you have employed, if Yes plsprovide the evidence
During the bottlenecks, what was your communication channel you followed, if yes, plsprovide the evidence
Did you have a stable build of the application which resembled the Production environment
or as close to it
a. Understand the current solution and infrastructure and performance
b. Find existing bottlenecks
c. Verify scalability of the system
d. Verify performance requirements
e. Verify impact of new features/functions
f. Determine optimal hardware/application configuration
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 18/25
Y/N/NA Comments
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 19/25
S.No Bug Reporting Y/N/NA Comments
1
2
3
4
5
6
7
Are your Bug details are Specificto the context
Are you able to do a detailedreproduction strategy
Are you ensured that there is nodefect with same ID in the Issuelog
Did your bug report havesummary, that catches theauidence ( here the mainaudience are developers &business )
What branch of the code you havenoticed the Bug
Have defined your defect onSeverity & Priority
Are you showing the screendumps of the defects, do youhave tool called "Snagit" forscreen dumps or any other tool tocapture the screen shots
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 20/25
S.No User Acceptance Y/N/NA Comments
1
2
3
4
5Has the UAT group been defined?
6
7
8
9
10
11
12
13
14
15
16
Has the project team been made aware of its role inadvising on changes to business processes and procedures?
Has the project team been made aware of its role inproviding support for all testing issues and concerns?
Has the project team been made aware of its role intracking and managing test problems?
Has the project team been made aware of its role inchanging system functionality?
Does the UAT group understand its responsibility in
executing the test cases and ensuring that the finaloutcomes of the tests are satisfactory?
Has the UAT group been explained its role andresponsibility in ensuring that all test case input sourcesand output results are documented and auditable?
Has the UAT group agreed that the test cases providecomprehensive and effective coverage of all aspects of functionality?
Has the UAT group been explained its role in documentingproblems and working with the project team to resolve
problems identified during testing?
Does the UAT group agree upon and understand the rangeof severity levels discussed with the project team andproject stakeholders?
Does the UAT group understand the responsibilities andrequired actions for each category of problem identifiedduring testing?
Does the UAT group understand that it must sign off on alltest cases by signing the completed test worksheets?
Has the UAT group been made aware of its role inaccepting the results on behalf of the relevant user
Does the UAT group understand that it must recognize anychanges necessary to existing processes and take a leadrole in ensuring that the changes are made andcommunicated to other users?
Does the UAT group understand its role in confirming use of the system in performing business processes?
Does the UAT group understand its role in verifyingperformance on business critical functions?
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 21/25
17
18
19 Has the plan for acceptance testing been submitted?
20Have all possible system functions been described?
21 Is all input data available that is required for testing?
22
23Have all user specific constraints been considered?
24Has the testing procedure been defined?
25
26
27Were all steps of the test run documented?
28
29Did the users review the test results?
30
31
32
Did each user sign off on output?
Does the UAT understand its role in confirming theintegrity of data?
Does the UAT understand its role in assessing system go-live readiness?
Has acceptance criteria be defined on which thecompletion of the acceptance test will be judged?
Have test cases been created to discover contradictionsbetween the software product and the requirements?
Have test cases been created to review whether timingconstraints are met by the system?
Was the acceptance test performed according to the testplan?
Are the services provided by the system in compliance withuser requirements?
Did the users judge acceptability in accordance with thepredetermined criteria?
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 22/25
S.No Operational Acceptance Y/N/NA
1
2
3
4
5
6
7
8
9
10
Did you ensure all the UAT related issues have beenaddressed/retested/Closed
Did youensure all the non-functional aspects of the system are tested toensure that the system is within the specified parameters. Performancetesting need to be performed for the system to meet the non-functionalaspects of the system. Has this been done? If yes Pls provide evidence
Has the system been tested against the requirements, this addressessthe test coverage done against the defined requriemnts, Dotyou have
the evidence?
Did you the Backup recovery Plan. This need to be backed by having abackup plan that covers, like the baseline configuration so a computercan quickly be restored to its prior state, Backing up servers beforethey are upgraded, Backing up the most recent system and user data
before you begin switching systems, and testing the restore process foreach of the above processes using the backup files, Pls provide
evidence if you say yes
Did you have means to address the Data Integration test. The dataintegration testing should prove that the data is accurate,
Completeness, validy and consistency. We strongly encourageautomation for this process. Pls provide evidence, if you say yes
Have you addressed the Security testing aspects, Such as considering indoing Pen testing. If you say yes, Pls provide evidence
Did you reviewed the manuals and maintained for end user usage? If yes Pls provide evidenceIs the training plan in place for user, how to use the system. Pls provide
the training plan, if you answered yes
Does the User has a point of contact to reach if the systems fails to
respond,If you say yes, Pls provide the evidence.
Is there a disater recovery plan in place, the plan should havePreparedness, response, Recovery and Mitigating the risk henceforth
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 23/25
Comments
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 24/25
S.No Regression testing Y/N/NA
1
2 Is the regression suite has been baselined to production
3
4
5
6 Is the regression suite an automation suite
7 Who is providing the test data to run the regression test suite
8 Are you regression testing focus maintly on functional aspects of the system9 Does your tests include to test how the system behaves
10 Have you considered using unit test cases for regression?
Did you use Integration test cases & System test cases for building forregression testing suite
When was the last time the regression suite has been run againstpreproduction system
Did you run the regression test suite, due to project changes happening? If yes elaborate is it for Project or Change requests
Are you the member , who maintains the regression test suite? If yes, plselaobarate how you maintain the suite
8/7/2019 Testing check list
http://slidepdf.com/reader/full/testing-check-list 25/25
Comments