InfoQ Homepage Testing Content on InfoQ

Articles

RSS Feed

Newer Older

Writing Automated Acceptance Tests with Spec Flow

Acceptance or functional testing is a type of testing where a system is tested to see if the required specifications are met. These tests are a type of black-box testing where the internal implementation is irrelevant. Mustafa Saeed Haji Ali demonstrates how to automate these tests using SpecFlow.

Mustafa Saeed Haji Ali
on Jul 06, 2012
Testing SQL Server Code with TST

Automated Testing (unit/integration) is an integral part of any agile development process. However a project with significant logic housed in database code creates severe constraints to writing unit level tests, especially if it is large, complex and depend on data. We will explore the TST framework and a few ideas for writing and maintaining good tests for database code.

Roopesh Shenoy
on Jun 18, 2012
First Steps in Unit Testing

Unit testing goes hand in hand with other agile practices, so starting to write tests is a stepping-stone for organizations wanting to go agile. The road is long, but is worth taking. In this article, Gil Zilberfeld cover tips on what to expect, and steps to take when starting out in order to make unit testing a part of development life.

Gil Zilberfeld
on Jun 05, 2012
Writing a Comprehensive Unit Test

A common theme amongst people professing “best practices” for unit tests is that you should only write a single assertion for each test. People who make these proclamations rarely show any unit test and those that do only show one. Yet this pattern may require a dozen other unit tests to ensure quality for even a trivial operation. This article uses examples to question that recommendation.

Jonathan Allen
on May 24, 2012
Dan Allen on Arquillian Testing Framework

Arquillian is an integration and functional testing platform that can be used for Java middleware testing. It helps bring the tests to the runtime environment, freeing developers from managing runtime from within the test. InfoQ caught up with Dan Allen to talk about the framework features and its future roadmap.

Srini Penchikala
on May 14, 2012
Book Review: Experiences of Test Automation

“Experiences of Test Automation” is a compilation of experiences in the field that is hard to read from end to end but serves well as a reference for experienced readers by providing examples of approaches, obstacles and solutions in a variety of domains and technologies as well as insightful overviews from the authors.

Manuel Pais
on Apr 27, 2012
The Developer-Tester Divide

The evolution of the software industry has created two separate roles: The developer and the tester. Traditional software development put these two at odds. Now, agile practices are bringing them together again in order to meet the original business goal: working software.

Gil Zilberfeld
on Apr 25, 2012
Verification and Validation for Trustworthy Software Systems

In this IEEE article, authors discuss a continuous verification and validation of complex and safety-critical software systems using techniques like statechart assertions, runtime execution monitoring, and scenario-based testing.

Man-Tak Shing James Bret Michael Doron Drusinsky Thomas W. Otani
on Mar 05, 2012
Design for Testability – The True Story

Testing is a major activity in any development lifecycle - a large part of a project budget is spent on it. If we want to effectively use it, the ease of testing should be addressed from the early stages of building the system.

Gil Zilberfeld
on Jan 12, 2012
Feature Injection: three steps to success

Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.

Chris Matts Gojko Adzic
on Dec 14, 2011
Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

Jon Arild Tørresdal
on Nov 10, 2011
Interview and Book Review: Specification by Example

Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.

Shane Hastie
on Oct 24, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles