Starting Out on Testing? We Have The Best Story on the Planet.

项目
03/06/2015

Team Collaboration is Key to Quality.

If you have a silo approach in your organization that "we'll implement all the features then throw these deliverables over the fence to Testers and then get on with the next set of features, this is a recipe for much more time and effort 10x for your organization". The number of outstanding bugs will grow and the backlog will become a challenge. It becomes an ongoing increasing debt. Customer and End-User frustration is inevitable and worst case you actually start the process of net effect losing customers.

At Microsoft, we embrace the notion that it's easier to fix a bug further upstream than it is downstream. We prefer to eliminate bugs as you write code, and if those bugs creep out, we like to empower our testers to find those bugs quickly and provide rich diagnostics such as IntelliTrace, VM snapshots, Video, System Information and other such information with minimum effort, so that the Developer is able to immediately act upon fixing the bug and closing it - successfully reproducing that bug and being taken immediately to the line code or data or environment that caused it. The Tester must be able to find bugs ongoing, quickly, communicate this - in seconds and move and find as many as possible before your customer does.

That's why, we believe Developers and Testers, and yet also Project Managers, Operations and other team members must be a part of an ongoing continuous quality cycle. To that end, there is no solution quite as integrated and out of the box (not an army on consultants from the vendor), that provide the solution for modern application development with quality baked in from the onset.