WCF Service Testing with Sockets
The socket-based approach is flexible and very useful for security and performance testing of WCF services. This article shows you how to test a WCF service using a network socket based approach.
The socket-based approach is flexible and very useful for security and performance testing of WCF services. This article shows you how to test a WCF service using a network socket based approach.
In his blog post ‘”Exploratory Testing” is a pleonasm ‘, Aaron Hodder explains that there is no “exploratory testing” and “other testing”. All testing is exploratory. If it’s not exploratory, it’s not testing.
When the testability level of a project is not monitored, it can end up becoming a burden for the team. These testability problems usually add up in small steps, making them hard to detect if we do not make the effort to look for them.
Broad assertion cuts out too large a chunk of output and side effects for bit-to-bit comparison, which makes it harmful due to the resulting brittleness. The assertion fails if any small detail changes, regardless of whether that change is relevant to the interests of this particular test. In this article, based on chapter 4 of Unit Testing in Java, author Lasse Koskela explains how to refactor the tests that suffer from broad assertion.
This blog post presents some results of an exploration of software testing tools to discover various types of potential user interface issues even for complex applications.
In this blog post, Alberto Savoia discusses the CRAP (Change Risk Anti-Patterns) code metric. The CRAP metric combines cyclomatic complexity and code coverage by automated tests to help identify code that might be particularly difficult to understand, test or maintain.
This article provides 3 tips to create readable unit tests.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates