Software Testing Articles: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
This article discusses how test automation can help achieving continuous delivery. It suggests to start small with a good investment on a robust automation suite, to give it your best people and to cultivate habits in your team that respect tests. Test automation reduces cycle times and also improves the cost of each deployment.This is achieved by earlier feedback to developer through automated tests improves the quality of builds that the testers work on, provided they pick up green builds. There is also a direct reduction in testing cost, as fewer people are needed to run the tests.
Unit tests are comprised of test methods and classes that verify whether a particular piece of code is working properly. This article introduces test methods in the salesforce.com environment. It details why test methods are a critical part of Force.com application development, test method syntax, best practices, and advanced topics such as test methods for Visualforce controllers and Apex web service callouts.
Selenium is a popular framework for testing the user interface (UI) of a web application. It is an extremely powerful tool for running end-to-end functional tests. You can write tests in several programming languages and Selenium executes them into one or multiple browsers.
James A. Whittaker, the former Test Director for Chrome and Chrome OS, discusses in this article what it means to be a Google tester and how Google testers approach the problems of scale, complexity and mass usage.
The open source JUnit unit testing tool has been a blessing for Java developers. However, many programmers think that it is enough to learn the JUnit API and write a few tests in order to have a well-tested application. This idea is more dangerous than not doing unit tests because it leads to a wrong sense of code quality. Learning JUnit is the easiest part of unit testing your Java code, but writing good tests is the hard part.
This article provides a process to integrate Test-Driven Development in the maintenance of a .NET application. You will first write the tests that will prove your new code gets the same results as the legacy code. Then you isolate new code into separate methods or classes that you can test independently. You break down the requirements into simple valid tests. Finally you check to see that you have not introduced a new bug. While you are doing this, let Visual Studio generate the utility code for you and find a tool to run your tests continuously like AutoTest.NET.
This article discusses the traditional software testing aspects that should be changed before adopting Agile practices. Testing teams face a significant impediment when they have to unlearn the traditional practices.
