Testers Get a Moment in the Spotlight -- Visual Studio Magazine

Desmond File

Testers Get a Moment in the Spotlight

Microsoft just launched a new Web site aimed directly at software QA and testing professionals. Called Tester Center, the new site aims to bring testers together to share experiences and best practices, get advice and access useful content.

The site is headed up by James Whitaker, an early innovator in the area of model-based testing and currently a Microsoft security architect working in the Trustworthy Computing Initiative at Redmond.

If you're involved with software testing at your organization, the Tester Center might be worth a bookmark. Have you had a chance to check the new site out? Let me know your thoughts at mdesmond@reddevnews.com.

Posted by Michael Desmond on 10/24/2007

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.