Weerasak.com

Flex functional testing with FunFx and Cucumber by Andrea Franz

Cucumber is a great tool I usually use for BDD in my ruby projects, but yesterday I tried it with Flex, and it was very enjoyable. Here a little example on how to test Flex applications with Cucumber.

Mockito.LoginServiceExample by Brett L. Schuchert

What follows is a series of tests to get enough production code written to suggest a better implementation. The first purpose of this tutorial is to demonstrate using Mockito for all types other than the underling LoginService. This is close to a classic mockist approach, though it varies in that I'm emphasizing testing interaction rather than state and deliberately trying to write stable tests that do not depend too much on the underling implementation.

Handling Bugs in an Agile Context by Elisabeth Hendrickson

Many of the traditional teams I worked with (back before I started working with Agile teams) had bug databases that were overflowing with bugs that would never be fixed. Usually these were things that had been reported by people on the team, generally testers, and prioritized as “cosmetic” or “low priority.”

Such collections of low priority issues never added value: we never did anything with all that information. And yet we lugged that data forward from release to release in the mistaken belief that there was value in tracking every single time someone reported some nit picky thing that the business just didn’t care about.

Measuring Web application response time: Meet the client by Srijeeb Roy

Plenty of Web applications rely on JavaScript or some other client-side scripting, yet most developers only measure server-side execution time. Client-side execution time is just as important. In fact, if you're measuring from the end-user perspective, you should also be looking at network time. In this article Srijeeb Roy introduces a lightweight approach to capturing the end user's experience of application response time. He also shows you how to send and log client-side response times on a server for future analysis. Level: Intermediate

JavaScript Test Driven Development with JsUnit and JSMock by Dennis Byrne

This article is a crash course in writing maintainable JavaScript. We'll add features to a running example by iteratively following a simple principle: write a unit test, make it pass. Each test will serve as a quality feedback loop, creating both a safety net and an executable form of documentation for anyone who wants to change the production code. By starting each feature with a simple failing test we ensure that all features are tested. We avoid the cost of rewriting code to test it later. This is particularly valuable given the fact that JavaScript developers have so much rope to hang themselves with – consider how much global mutable state there is between the DOM API and the language itself.

A Better, Faster Way to Stress and Load Test Today’s Web Application by Daniel Baloche

Poor application performance, unexpected deployment issues, and server malfunction can compromise your Web application. But by following the best practices and techniques explained in this article, testers can improve reliability and performance, reduce development costs and most importantly help their companies deliver what they promised in terms of application functionality and performance.

A Web Developer's Responsibility by John Resig

Browser bugs are annoying, frustrating, and make your job incredibly difficult.

Because browser bugs are so frustrating and such a burden on top of normal development it should be the responsibility of every web developer to make sure that the browsers they develop for are able to find and fix their bugs. By taking responsibility for the bugs that you find – and to not assume that "someone else will find it" – will accelerate the rate at which browsers can improve.

Behavior Driven Design for Ruby on Rails with RSpec and Friends by David Chelimsky from Windy City Rails Conf 2008

Automated integration testing with Selenium, Maven and Jetty by Kevin McCormack

Putting all of this together, we’d like to share with you the Maven configurations and Java code that we use to accomplish automated one-step Selenium integration testing for a web application running in Jetty using Maven.

Watir and Selenium by Bret Pettichord

Two excellent open-source tools for testing web applications are under development: Watir and Selenium. I?ve been contributing to both. Why? Wouldn?t it be better to just have one good tool?

Both tools run tests directly in a browser, and both do it in a way that allows the browser to be minimized while the tests are running, which means you don?t have to dedicate a machine to running tests. And both have been used to test significant web applications under development. But there are also many differences which ultimately stem from the different goals they were originally designed to meet.