In today’s hyper-competitive, digital age, organizations worldwide need to be able to push code to production and launch new website features and content faster than ever without compromising quality. To address this need, continuous testing has become a critical part of the application development and delivery process.
With the multiplication of versions, platforms (desktop, mobile, tablets) and operating systems, testing an application that is supposed to run in a browser is not easy. In this article, Alexander Rayskiy proposes an approach to select the set of browsers that will be used during the software testing activities.
The performance of your application affects your business more than you might think. Top engineering organizations think of performance not as a nice-to-have, but as a crucial feature of their product. Those organizations understand that performance has a direct impact on user experience and, ultimately, their bottom line. Unfortunately, most engineering teams do not regularly test the performance and scalability of their infrastructure.
The Exploratory Testing Chrome Extension is a free and open source extension for the Chrome browser that is designed to make exploratory testing of web sites easier. This extension will allow you to take notes during your exploratory testing sessions with a nice set of additional features.
QualiTest has recently produced a report and an infographic about the typology and sources of the most common bugs found in web sites. The company has used for this the bug summaries from hundreds of web site testing projects performed recently.
Web application testing is a rapidly evolving topic, so year by year it is reasonable to enumerate the possible options and re-evaluate the web testing strategy you have chosen for your .NET project.