Review your results for Customer bug report collection widget
This customer bug report collection widget checks page covers customer bug report collection widget. First, choose one small task you can check by hand. Then follow the steps below and compare the result with your source information.
The download is an offline record workspace. This page explains one part of its use. For the full process, follow the ten linked guides in order or open the section you need. Keep your source notes with your working files.
Review against the promised outputs
For customer bug report collection widget, begin with the package capability list. Each output you rely on should be traceable to the input or edit that produced it.
- Check working task-specific fields: confirm that the result is present, complete and appropriate for your task.
- Review editable records or document output: confirm that the result is present, complete and appropriate for your task.
- Confirm search or preview where applicable: confirm that the result is present, complete and appropriate for your task.
- Check csv, print or document export: confirm that the result is present, complete and appropriate for your task.
- Review realistic demonstration inputs and backups: confirm that the result is present, complete and appropriate for your task.
- Confirm runnable customer website and owner dashboard: confirm that the result is present, complete and appropriate for your task.
- Check private customer receipts: confirm that the result is present, complete and appropriate for your task.
- Review python source and hosting instructions: confirm that the result is present, complete and appropriate for your task.
Check the details that affect decisions
The product exposes these inputs: Reporter; Page URL; Steps to reproduce; Expected result; Actual result; Severity; Status.
Compare the source entries with the resulting record or document. Check that edits and deletions affect the intended item and that exported text retains its meaning.
Separate checking from automation
Manual records and exports. No live portal, automatic monitoring, matching, notifications or multi-user access. Includes a runnable Python customer application; public hosting is configured by the buyer.
Keep a note of what you checked and which source information you used. Recheck results when the source data or your requirements change.
Make the review traceable
First, compare the result with a source you trust. Do not rely on how polished the preview looks. Check a small sample in detail before you review the rest.
Next, note any difference and its cause. For example, a wrong date may explain an unexpected total or an omitted record. After you fix it, run the same check again. Finally, keep a note of the checks you completed with the result.
Details to check in this product
- Reporter: confirm the source and keep a clear reference.
- Page URL: check the value against your practice case.
- Steps to reproduce: review the result before you save or share it.
- Expected result: confirm the source and keep a clear reference.
- Actual result: check the value against your practice case.
- Severity: review the result before you save or share it.
- Status: confirm the source and keep a clear reference.
A useful reference
Use an isolated environment when following the runnable application setup. Read the Python documentation on virtual environments for more detail.