|
Defect/problem documentation A defect tracking/problem reporting system should provide:
Why are there Bugs in Software?
(Continued from previous question...)
Defect/problem documentation
A defect tracking/problem reporting system should provide:
- Standardized
- Inputs
- Expected Results
- Actual Results
- Anomalies
- Date
- Time
- Procedure Step
- Environment
- Attempts To Repeat
- Testers
- Observers
- Non-Standardized
- Defect ID
- Priority
- Severity
- Test Cycle
- Test Procedure
- Test Case
- Occurrences
- Test Requirement
- Person Reporting
- Defect Status
- Defect Action
- Defect Description
- Defect Symptom
- Found In Build
- Software Module
- Module Description
- Related modules
- Person Assigned
- Date Assigned
- Estimated Time to Fix
- Resolution
- Resolution Description
- Fix Load Date
- Fix Load Number
- Repaired in Build
- Date Closed
- Contact Person
- Attachments
- Rework Cycles
- Owner
- Work Around
- Person Investigating
- Emergence/Scheduled
- Programming Time
- Process or Product
- Customized defect/problem reporting data fields
- ACD capability
- Predefined queries/reports
- ustom query/reporting
- Free text searching
- Cut and paste
- On-screen report display
- Printed reports
- Support all Network types
- Provide Record Locking
- Provide data recovery
- Support for dial-in access
- An interface to the E-mail system
- Manual notification
- Automatic notification of team members
- Password protection of team members
- Limited access to functions based on user type
(Continued on next question...)
Other Interview Questions
| 