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

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

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

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

  • Test automation and Continuous Delivery

    This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.

  • .NET Static Analysis and Parasoft dotTEST

    Static analysis has a broad set of capabilities to offer the .NET world. It can enforce pattern-based rules, whether they're based on proven standards or custom patterns that help you identify application-specific defects. Nevertheless, some defects cannot be detected by this analysis technique. The flow analysis feature of dotTEST does exactly that.

  • Discover Recording JVM Debuggers

    A debugger is a great tool for examining the internal state of an application, reproducing however a specific issue is a completely different matter. Fully replicating the production environment into a staging area might even be a feat on its own. Meet recording debuggers that remove all the guesswork and extra effort by monitoring the application in production and knowing exactly what happened.

  • Three Tips to Successfully Load Test Microsoft Silverlight Applications

    While Silverlight is an attractive option for developing expanded application, it brings new challenges to organizations. In preparation, companies must adapt their testing approach. Given the way new technologies work when deployed on internet/intranet applications, a careful approach to testing is important.

  • Virtual Panel: State of the Art in JavaScript Unit Testing

    Unit testing is a commonly accepted practice in order to deliver maintainable code. This is especially true for a dynamic language like JavaScript and there are currently several frameworks and libraries for a team to choose from. InfoQ had a Q&A with the creators of some of the leading JavaScript unit testing frameworks about their projects and what they offer to developers.

  • Testing Misconceptions

    In this article Liam O'Connor explains some of the common misconceptions about testing. If you write your tests with these in mind, he hopes that it will help you and your team to decide when it is appropriate to test, and when it isn't.

  • FlexMonkey Deep Dive

    FlexMonkey is an open source tool from Gorilla Logic for testing Flex and AIR applications.  This article provides a brief introduction to FlexMonkey and then walks through debugging issues that can be encountered when testing with it.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 3

    This is the third and final part of the late Jamie Phillip’s exploration into the world of coding kata’s and Behavior Driven Design. This part shows how to incorporate VS 2010 project templates into the testing process.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 2

    This is the second of a three-part series on how Jamie Phillips used a combination of coding katas, behavior driven development, and project templates to improve his development practices. In this part Jamie introduces the reader to behavior driven development and explains how it can improve the effectiveness of unit testing.

BT