Month: June 2012

Unit Testing Backbone.js Applications With QUnit And SinonJS

June 11, 2012 0

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.

The Latest in Google Test Tools

June 8, 2012 0

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.

Testing Legacy Servers with Arquillian

June 8, 2012 1

Arquillian is a open source platform sponsored by JBoss that simplifies the testing of Java middleware. It brings your test to the runtime, freeing you from the concern of managing the runtime from your test and letting you focused on writing your integration test logic. This blog post by Nikolas Frankel explains how to to test Java EE components on JBoss 5.1 EAP with Arquilian and TestNG. His conclusion is that Arquillian seems to be a nice in-container testing framework but seems to have to be polished around some corners. The usage of TestNG may be the culprit here.

Design for Testability

June 6, 2012 0

Software testing is a major activity in any software development project and a large part of the budget is spent on it. If we want to effectively spend your money, the ease of software testing should be addressed when you design your system in the early stages of building your applications. In this article, Gil Zilberfeld explains that thee adoption of test first practices like Test-Driven Development (TDD) or Acceptance Test-Driven Development (ATDD) by the majority of agile teams shows how test automation needs are addressed from the initial steps of system concepts. As an additional benefit, it is easier to evolve a testable system because you can add features knowing that existing ones did not break.

.NET BDD with SpecFlow and White

June 5, 2012 0

This article provides a general overview of behaviour-driven development (BDD) in a .NET context. I presents some .NET tools for BDD (SpecFlow) and UI testing (White) and proceeds with a working example giving hands on BDD in .NET. SpecFlow is an open source tool aims to provide a pragmatic and frictionless approach to Acceptance Test Driven Development and Behavior Driven Development for .NET projects. White is an open source framework for automating rich client applications based on Win32, WinForms, WPF, Silverlight and SWT (Java) platforms. It is .NET based and does not require the use of any proprietary scripting languages. Tests automation programs using White can be written with whatever .NET language, IDE and tools.

Evaluating Test Suites

June 5, 2012 0

Test adequacy criteria provide developers with guidance on how to populate software test suites. Current software testing methods do not address many of the fundamental characteristics of distributed systems, such as distribution topology, communication failure, and timing. Furthermore, they do not provide the engineer with a means to evaluate the relative effectiveness of different criteria nor the relative effectiveness of adequate test suites satisfying a given criterion.

« 1 2