How to Report a Bug?
Use following simple Bug report template: This is a simple bug report format. It may vary on the bug report tool you are using. If you are writing bug report manually then some fields need to specifically mention like Bug number which should be assigned manually. Reporter: Your name and email address. Product: In which product you found this bug. Version: The product version if any. Component: These are the major sub modules of the product. Platform: Mention the hardware platform where you found this bug. The various platforms like ‘PC’, ‘MAC’, ‘HP’, ‘Sun’ etc. Operating system: Mention all operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, Mac OS. Mention the different OS versions also if applicable like Windows NT, Windows 2000, Windows XP etc. Priority: When bug should be fixed? Priority is generally set from P1 to P5. P1 as “fix the bug with highest priority” and P5 as ” Fix when time permits”. Severity: This describes the impact of the b
• How to write a Test Plan (1) • HR (5) • HR Questions (5) • Important testing Checklist (1) • Important Testing Interview FAQ (1) • Installation Testing (1) • International Organization for Standardization (ISO) (1) • Internationalization (1) • Interview Faq’s (8) • Joins (1) • Leadership Qualities (1) • Load Runner FAQ’S (4) • Load testing (2) • LoadRunner FAQ’s (5) • LoadRunner for Performance testing (1) • Localization (1) • Manual Software Testing (1) • Manual Testing Basics (52) • Monkey testing and Smoke testing (1) • mr (1) • Multilingualization Testing (1) • New features in LoadRunner 9.5 (1) • NUnit (1) • Parameterization In QTP (1) • patch for QTP 10 debugger (1) • Peer Review in Software Testing (1) • Primary keys (1) • Priority and Severity (1) • purpose of black box testing (1) • Purpose Of Test Strategy (1) • QA engineer (1) • QA Process in an organization (1) • QA processes (1) • QTP FAQ’s (14) • QTP Testing Interview FAQ’s (4) • QTP10.0 (4) • Quality Plan (1) • Quick T
