Home
Testing
Bug ReportingPerspectives from a Test Manager
Author: stickyminds.com Published: 10th Nov 2005 Visited: 538 times
This article highlights four keys to getting better organized: 1. A common set of ground rules on the test progress, defect reporting, and verification; 2. The ability to convey how your team’s testing is going--on a frequent basis; 3. Knowing what needs to be tested--and being able to stand behind the reasons why; 4. Maintaining good communication with the development leaders to help move the product through the development phases--being proactive rather than reactive.Read Article Sponsored Links
Related Articles
• JMeter - Adding HTTP Header Manager Adding Header Manager Another very useful default element is the Header Manager Configuration element This element can either be added to the Test Plan and configured manually as an afterthought or we can simply use the recorded Browser derived headers element as included in the recor ...
• JMeter - Running the Test Running the Test Once the assertions are properly completed we are expecting that running our Test Plan would pass all the assertions Passed assertions will not show any error in Assertion Results Listener installed within the same scope As for all Listeners results as captured by the Listeners can ...
• SOA Web Services - Developing the Test Client Developing the Test Client We will now develop a C console application for consuming the previously created web services Use the project wizard in VS NET to create a console applica ...
• Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test The things we want to test are Initial settings The text field is empty The text field is a sensible size The Ok button is disabled The Cancel button is enabled The dialog is a sensible ...
• Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure Having seen the broad outline of the test class and the UI methods needed we can look closely at the implementation of the test start with the UI Wrapper class and the init and cleanup met ...
• Swing Extreme Testing - The wasCancelled() Test The wasCancelled Test The first of our API tests is to check the wasCancelled method We will basically do three investigations The first test will call wasCancelled before the dialog has been cancelled The second test will cancel the dialog and then call the method In the third test we will enter a ...
• Swing Extreme Testing - The Data Validation Test The Data Validation Test The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid A name can be invalid if it contains an illegal character or if it has already been ...