Search Results

Is your management aware of what you and your fellow testers do on a daily basis? … Can you explain the power of serendipity and exploratory testing to your management or your Speaker to Management? …

For instance, if you're working with CodedUI, Microsoft's Team Foundation Server and Microsoft Test Manager/Lab Manager work together seamlessly once TFS has been configured for lab management (the module …

The short, simple answer: No The slightly more nuanced answer: It can be, but you have to be very careful The real explanation: Like most other candidates for tester performance KPIs, escaped defect …

Bryce, If you go to Alan's blog you'll find a small application there that he deliberately seeded with a couple of errors. That's probably a good starting point for functional black-box testing, alth …

To add to Rsf's excellent answer: You can't "make" management accept anything. You may be able to convince management that migrating your test codebase is a good idea. … If you can demonstrate that a migration stands to improve ROI by enabling any of the following advantages you stand a better chance of management approving the change: The proposed new framework would …

Your management is blaming you for not finding the known issues. … Tell your management about the known issues list - If your managers don't know you've already reported the problem, they don't know whether your team was doing their job properly or not. …

The problem with any form of hard metric in a field like software QA is that - to use the answer I give so often here - it depends. Each hard data point is really only helpful in the context of the de …

To expand on the other answers: Note that something is a corner case - don't be afraid to note that an issue is a corner case and is being documented so that when a customer does encounter it, it's …

From a manual perspective, I'd suggest trying something along these lines: List critical functionality tested and level of confidence List happy path/steel thread functionality tested and level of c …

As a counterpoint to the many answers saying that testers can review the changes in source, I have worked in more than one place where testers have no access to source code. Their only source of infor …

Without looking at the quality of your work, some of the techniques I've used successfully include: Be tactful. If I can, instead of simply creating a bug, I'll ask the developer what should be happ …

In addition to some of the other suggestions, you could consider a few other options: Build/run load tests for new/recent work (given the maturity of your test automation you may already have this u …