Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
The debate about automating or not the software test has always been active in the software development community. This blog post by Ole Laursen discusses the issue of automating software tests with a balanced perspective that presents equally circumstances where automation has benefits or disadvantages.
This blog post provides guidelines for scalability testing. It defines the difference between load, performance and scalability testing. A well-designed workload is the first requirement for any performance testing is a well-designed workload. The post provides hints how to to plan, run and analyze scalability tests.
This blog post presents an interesting vision of how functional software testing works. It discusses the lack of profiency in functional testing and references James Bach SFDPO (Structure, Function, Data, Platform, Operations) heuristic as a guide for providing new functional testing perspectives.
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.
This blog post explains how to separate integration and unit tests with Maven, Sonar, Failsafe and JaCoCo. This is achieved by executing unit tests via Surefire and integration tests via Failsafe. Then you show as much information about them as possible in Sonar. The post provides detailed command lines and Maven configuration files to achieve this goal.
This blog post discusses how to apply a Test-driven Development (TDD) approach to non-functional requirements like performance. He proposes examples on how to test performance with time and memory constraints. He suggests that it is possible to extend this approach to performance, scalability, portability, maintainability and even more abstracts requirements like usability, accessibility.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates