Unit Testing Web Applications
Unit testing focuses on testing small pieces of code that a developer is writing. This article shows how to get started unit testing JavaScript as well as server-side code.
Unit testing focuses on testing small pieces of code that a developer is writing. This article shows how to get started unit testing JavaScript as well as server-side code.
Testing continues to represent the single largest cost associated with the development of sophisticated, software intensive, military systems. A reduction in overall testing cost will save billions of dollars over the lifecycle of tactical software systems. Such savings can only be achieved if the concept of testing begins very early in the development process, improving synergy throughout the development and testing communities.
This article explores qooxdoo’s built-in facilities for automated UI testing. qooxdoo is a universal JavaScript framework that enables you to create applications for a wide range of platforms. With its object-oriented programming model you build rich, interactive applications (RIAs), native-like apps for mobile devices, light-weight traditional web applications or even applications to run outside the browser.
In this blog post, James Whittaker explains how he decreased the time needed to create test plans by splitting the allowed time to produce them in 10 minutes slices.
This is a brief video on how to use the JUnit open source unit testing framework for Java. By using JUnit, you can assert that methods in your Java code work as designed, without the need to set up the complete application.
As a software testing consultant and musician, I meet a lot of skilled testers who do amazing work. Through experience and a lot of trial and error, they have developed skills they can’t easily explain. Unfortunately, with software testing, there aren’t as many obvious avenues for skill development as there are for musicians. Many software testers don’t realize that there are learnable exploratory testing skills they can develop to help them become even more valuable to software development teams.
This article discusses how to build a portfolio of scenarios for load testing automation. You have rarely only a single scenario to test, so you have to decide which scenarios to include in your test plans. Criticality, frequency, difficulty and verifiability are the four key factors that should be considered to determine the scenarios to automate.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates