SpecFlow is an acceptance test driven development and behavior driven development for .NET. One of them the biggest challenge in using SpecFlow is to improve the efficiency of the automated testing process. Typical questions are about organizing feature files, keeping the specification language consistent, refactoring feature files, automation code maintainability, better feedback from failing tests, test execution time or handling stability issues.
This article shows how concepts and axioms can be expressed in standard C++ 2011, and explore Axiom-based testing is a technique for testing generic code in a generic way, based on algebraic specification. This article explores how you can specify graph transformation-based rules for a classical problem of transforming from UML sequence diagrams to state machines. The specification of the transformation rules is based on the concrete syntax of sequence diagrams and state machines. It introduces tailored transformation support for sequence diagrams and a novel graphical operator to match and transform combined fragments.
Program understanding is a major obstacle during program maintenance. In an object-oriented language, understanding an operation requires understanding its type and its effect on the object network. The effect is particularly important for scripting languages where there is neither class structure that restricts the shape of an object nor any other kind of access control. We have designed and implemented JSConTest. JSContest is a tool that enhances JavaScript with simple, type-like contracts and provides a framework for monitoring and guided random testing of programs against these contracts at the same time.
Learn how Telerik Test Studio’s performance testing and just-released load testing features can help you detect bottlenecks in your system’s performance and answer business-critical questions about your ability to handle large amounts of traffic. This webinar focuses on Test Studio’s Performance and Load Testing features. It presents how these features can help you respond to questions from management like “Will our site be able to support traffic after this new product’s launch?” and “Are our customers happy when they are using our site during normal and high traffic times?”
Visual Studio allows you to create automated tests of the user interface (UI) known as coded UI tests. These tests provide functional testing of the UI and validation of UI controls. This article provides test automation guidance that helps you leverage the coded UI features of Visual Studio 2010 to foster a continuous, consistent and standard automation approach. Such an approach allows you to build, deploy and test, taking advantage of Visual Studio Lab Management features, which let automation testers reap the benefits of integrating with the build process for automatic build deployment, executing on VMs and reporting test automation results as part of Microsoft Test Manager (MTM). The article provides also a list of Do’s and Don’ts of UI automation. UI automation can be a tricky business. To help you get the best results, follow the advice, guidance and best practices for writing coded UI tests in the following Do and Don’t lists.
This article explores how to use QUnit And SinonJS to perform unit testing on Backbone.js applications. QUnit is a powerful, easy-to-use, JavaScript test suite. It’s used by the jQuery project to test its code and plugins but is capable of testing any generic JavaScript code (and even capable of testing JavaScript code on the server-side). SinonJS is a standalone test spies, stubs and mocks for JavaScript. It has no dependencies and works with any unit testing framework like QUnit.
Software testing is labor intensive, requires expensive switches in context, involves so much grunt work that it stifles creativity and slows down productivity, and, finally, it often ignores product and customer risks. Come and learn about the latest Google has to offer in open source test tools that help manual testers by eliminating much of the grunt work, keeping them focused on testing, and helping them prioritize their efforts based on risk. Chief among these are BITE, Quality Bots, Test Analytics, and Script Cover, the first two of which are the focus of this talk.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates