#bugreporting

In software testing, a bug report is more than “something doesn’t work.” It’s the bridge between QA testers and developers. A clear, structured bug report saves hours of debugging, while a vague one leads to delays, confusion, and endless back-and-forth.

For QA professionals, writing effective bug reports is as important as running the tests, because it improves developer efficiency, speeds up fixes, and ensures high-quality product delivery.

Even if most new applications are built with the web in mind, there are still .NET applications out there. And they will continue to be, although many limits of web applications fell in the last years, like WebGL.

For web applications, it's easy to provide a way to get feedback from your users directly.

Until now, having a similar experience for desktop .NET applications was not possible.

Check out this new SDK which allows developers to get In-Application bug reports directly on the touch of a button:

No longer "it does not work" bug reports via email without the context. What I really like is that you'll get a full screenshot of the application and it's even possible to add meta data like the used Windows version, .NET framework or exact build number of your software.

Don't let your users choose what they tell you.

And I really wasted my time to explain Snagit to my end users, ending up with a stamp sized screenshot which does not explain anything at all, like:

"Make the number larger". But where?