Categories
- Agile Testing
- Automated Software Testing
- Data Verification Testing
- Financial Software Testing
- Game Testing
- Healthcare
- Healthcare Software Testing
- Insurance Software Testing
- LoadRunner
- Localization Testing
- Mobile Performance Testing
- Mobile Testing
- Performance Testing
- QTP Test Automation
- quality metrics
- Regression Testing
- Retail Software Testing
- Security Testing
- Software Test Automation
- Software Testing Metrics
- Test Automation
- Test Case Design
- Test Management
- Test Management and Planning
- Test Process Improvement
- Test Strategy
- Test Tools
- Usability Testing
- User Experience
- Web Application Testing
-
Recent Posts
Recent Comments
- Kranti on Data Verification Testing
- shivakumar on Using XPath Axes to Locate Elements in Selenium Webdriver
- Rendezvous Software Performance Testing with Loadrunner | XBOSoft Software Quality Blog on Testing Retail Software – Ecommerce Testing Considerations
- Kristin on Coded UI Test Automation – CUITe Plug-In
- Santosh on Software Testing Trends – Software Industry Trends
Tags
agile agile project management agile testing android testing Automation Automation Testing Coded UI content target data verification Defect defect analysis defect metrics define software quality financial software testing L10N learnability localization testing mobile mobile application testing mobile performance testing mobile qa pharmacy software testing QA qtp scripting QTP VBS automation quality in use requirements scrum scrum testing Silktest software quality software quality measurement software quality metrics Software testing software testing metrics testing testing metrics test process improvement test strategy url redirection test url test usability user experience Visual Studio Web Application TestingLogin
RSS
Tag Archives: Defect report
Defect Writing Best Practice Guidelines
Defect reporting is one of the most important QA activities in software testing. Sure, we devise test strategies and plans, and test cases, but defects are the main ‘product’ that we produce that people can see as the result of our work. But what constitutes a ‘good’ defect? What are these elements’ definitions? I’ve been working in QA for 7 years now, so I thought I’d share some of our best practices:
Summary/Subject/Title
A short sentence to describe the issue: What is the issue? Where does it happen? Don’t put too many words here since many Defect Tracking Systems (DTS) usually have a text length limitation.
Example: Error occurs after clicking “Load” button in home page. More



