BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Testing Content on InfoQ

  • A Test Strategy for Enterprise Integration Points

    This article introduces a commonly applicable testing strategy for integration points, which improves the coverage, speed, reliability and reproducibility of testing, and thus could be used as a reference for implementing and testing integration-heavy applications.

  • Interview with Sandi Metz on Practical Object-Oriented Design in Ruby

    On occasion of the second edition of her book “Practical Object-Oriented Design in Ruby: An Agile Primer”, InfoQ talked with Sandi about how her book was received, learning from open source code, making sensible use of code analysis tools and other topics.

  • Jepsen: Testing the Partition Tolerance of PostgreSQL, Redis, MongoDB and Riak

    Distributed systems are characterized by exchanging state over high-latency or unreliable links. The system must be robust to both node and network failure if it is to operate reliably--however, not all systems satisfy the safety invariants we'd like. In this article, we'll explore some of the design considerations of distributed databases, and how they respond to network partitions.

  • Refactoring Legacy Applications: A Case Study

    To refactor legacy code, the ideal is to have a suite of unit tests to prevent regressions. However it's not always that easy. This article describes a methodology to safely refactor legacy code.

  • Book Review: ATDD By Example

    “ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero. Despite doing a reasonable job of summarizing and/or pointing to several test-related practices required for any successful agile tester, the book ends up trying and failing to be all things to all readers.

  • Unit Testing Hadoop MapReduce Jobs With MRUnit, Mockito, & PowerMock

    Hadoop MapReduce jobs have a unique code architecture that raises interesting issues for test-driven development. In this article Michael Spicuzza provides a real-world example using MRUnit, Mockito, and PowerMock to solve these problems.

  • Metrics-Driven Development

    In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.

  • Why Testing Matters in Agile Projects

    Agile is changing the way we work together and the work that is done. Many think that the role of testing is dead, but I think it is growing and turning into an even better, rounder, more effective testing. The role of Testing will powerfully help redefine the way things are done and the order in which they are done for best results in agile.

  • Testing in the Cloud: Exploring the Practice

    In this article, authors discuss the effects of cloud-based testing in software delivery process. They talk about cloud-based testing services such as performance testing and web-based application testing. They also share the results from their interviews with different organizations and their use of cloud in testing and suggest a cloud-based testing roadmap.

  • The Day the QA Department Died

    The role of QA is changing. In the waterfall world, QA teams, siloed away from developers, are slow and costly. Unit testing passes the responsibility for software quality to the developers and leads to better code, reducing reliance on a separate QA department. Is unit testing a better way to ensure software quality – the ultimate goal of QA?

  • Interview and Book Review: How Google Tests Software

    "How Google Tests Software" by James Whittaker, Jason Arbon and Jeff Carollo is a book that details exactly what is described on the cover. It is an informative and interesting look beneath the covers of how a large technical organization like Google deals with the complexity of software testing.

  • Continuous Mobile Application Testing

    Given the onslaught of mobile devices and apps into the SDLC, fingers and eyeballs seem to be the only way apps can be tested right now. But manual testing drastically slows down the development process, leaves a huge margin for error, and ultimately lowers the team’s ability to release quality software in a short amount of time. Dan Bartow of SOASTA hopes to offer something better.

BT