Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / rakesh
It Includes,
1. Test requirements,
2. Test planning,
3. Test design,
4. Test execution and Defect logging,
6. Test reports and acceptance,
7. Sign off.
Test Requirements
1. Requirement Specification documents
2. Functional Specification documents
3. Design Specification documents (use cases, etc)
4. Use case Documents
5. Test Trace-ability Matrix for identifying Test Coverage
Test Planning
1. Test Scope, Test Environment
2. Different Test phase and Test Methodologies
3. Manual and Automation Testing
4. Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
5. Evaluation & identification? Test, Defect tracking tools
Test Design
1. Test Traceability Matrix and Test coverage
2. Test Scenarios Identification & Test Case preparation
3. Test data and Test scripts preparation
4. Test case reviews and Approval
5. Base lining under Configuration Management
Test Execution and Defect Tracking
1. Executing Test cases
2. Testing Test Scripts
3. Capture, review and analyze Test Results
4. Raised the defects and tracking for its closure
Test Reports and Acceptance
1. Test summary reports
2. Test Metrics and process Improvements made
3. Build release
4. Receiving acceptance
Signoff
Signoff template provides a checklist format for customer
that can be used for reviewing a new system's functionality
and other attributes before closing a purchase order or
accepting a delivery. It includes checklist areas for
functional tests, documentation reviews, issue recording,
enhancement requests.
This form can be used standalone for this purpose, or it can
be used as the short-form checklist and signoff form
accompanying a written User Acceptance Test Plan or Beta
Test Plan (see our templates for those 2 documents).
NOTE: This form can also be adapted for review and
acceptance of any deliverable between a customer and a
provider. Whether the deliverable is a recommendations
report from consultants, a user manual from a technical
publications firm, a physical hardware system, a software
application, a plan for a marketing campaign, etc., this
form can be used to list what's expected by the customer,
record results of the acceptance review or tests, record
open issues to be corrected, and ultimately document
acceptance by the customer.
How to use?
When preparing to accept a deliverable—system, product,
report, etc.—from a supplier, fill out your version of this
form to include the items you want to test and/or review. If
possible, consider ahead of time whether any discrepancies
will be acceptable for each item. Schedule the review/tests
with the supplier and discuss expectations. When you perform
the reviews or tests, mark the performance of each item and
indicate whether each result is acceptable—will the
deliverable be accepted with this issue? Finally, review
overall results with supplier, timeline for issue
resolution, and whether re-test will be required.
| Is This Answer Correct ? | 15 Yes | 1 No |
Post New Answer View All Answers
Why is it often hard for management to get serious about quality assurance?
Explain the process of project tailoring.
How to know that we have to use which tool for this project?
Can you build a good audit trail using Compuware's QACenter products. Explain why.
How is retesting different from regression testing?
What is the quality audit?
Kindly tell me some good websites from where I can study about sqa and testing(advance and new material)
can you provide negative scenarios for ios alarm clock
Why are you in qa?
What if the project is not big enough to justify extensive testing?
When to start qa in a project?
A payroll system?
What are test driver and test stub and why we need them?
When we should continue testing?
What is a test strategy and what does it include?
