Software Testing Articles: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
As software development companies grow, it becomes more important to have a formal quality assurance (QA) process. In this article, Veronika Olshevskaya discusses six mistakes that you might do when you set up your QA department and suggests solutions to avoid making them.
Unit testing is a basic software testing activity that should be performed by every software developer. This handout produced by the Computer Science department of Stanford University introduces the ideas of unit testing and provides some examples on how to do it with JUnit in Eclipse.
A recent survey from the Methods & Tools software development magazine shows that the load testing activity is performed only in a minority of software development organizations. The poll asked the question: “Does your organization perform load / performance testing?”
Software testing during the transition to Agile is not easy. This fourth and final part proposes 7 practical tips for a smooth adoption of Agile software testing practices. From better communication to test automation, these tips should help to solve some of the issues that are naturally associated with this transition. Remember that it is up to you, as a team, to implement your kind of Agile and if you love it or hate it.
SharePoint is a web application framework and platform developed by Microsoft. It integrates Intranet, content management and document management features. Efficient software testing of this platform requires some specific knowledge that will be discussed in this article with hints and tips.
It is often said that “it’s always the baker’s children who have no bread”. In this very interesting article, Ed Glas explains how Microsoft manage the load testing efforts for its Visual Studio Online tool based on a Cloud architecture.
Software testing starts when you write the code that will be tested. In these two articles, Shane Tomlinson discusses some anti-patterns that will make your JavaScript frontend code difficult to test. He explains how to detect these anti-patterns in your code and then shows how to refactor your JavaScript to be easier to read, to reuse and to test.