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

  • Tackling real-world unit testing problems

    All the information, books and tools are out there, just pick up NUnit, and you’re good to go, right? Not exactly. Even before deciding to start unit testing, we need to sift through real experience of others; good and bad, horror stories and miracles (“This one test saved me a week of work!”). Then, we take the plunge, and realize: There’s so much to learn!

  • My Experience as a QA in Scrum

    The QA role in Scrum is much more than just writing test cases and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned over the past 2 years while serving as a QA analyst on a Scrum team. She explains how QAs not only perform agile tests but also fill many other roles and responsibilities, earning them a place of importance on the team.

  • Virtual Panel: Code-to-Test Ratios, TDD and BDD

    In the last couple of months several online discussions took place about test first or test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked the opinion of BDD and TDD experts.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

BT