Defect Driven Testing: Your Ticket Out the Door at Five O'Clock

are you not doing TDD yet? start with DDT...

Defect Driven Testing: Your Ticket Out the Door at Five O'Clock:

Test automation is not a controversial topic in most circles. Even developers who don't write automated tests agree it's a great idea. They just don't have time to work on it very often.
....
DDT is a fairly simple concept. When you find a bug, add a test.

Why take this approach?

First, no one can dispute the need for the test. If an issue was found, then it had been missed earlier. Perhaps the developer missed it and QA spotted it. Maybe it slipped past everyone and it was reported by your customer. Whenever it's reported, it needs to be fixed in a way that will prevent it from reappearing.
....
DDT is a gradual approach.
....
Over time you'll find that DDT creates an extremely effective test suite that targets the most problematic parts of your code base. Run your defect driven tests inside of a continuous integration system and you'll find your code running more cleanly every day.

tapestry 5 custom validation error message

in our system/ configuration, in order to customize T5 validation messages using the T5 validation message language key conventions, i had to use the following language keys:

• "required" as language key for a required field
  - f.ex. when i use t:validate="required" in a .tml file
  
• "number-format-exception" for a number field, and integer-format-exception for an integer field
  - when an input field attached to an integer property gets a letter, f.ex. 

using "%s" in the language expression will give access to the name of the field, f.ex. having an error message like "%s must be completed".

what did NOT work for us, even if it worked for others (ref information below), was any prefix with field or form name, or a postfix of -message...


Apache Tapestry - Form Input and Validation:

Customizing Validation Messages

Each validator (such as "required" or "minlength") has a default message used (on the client side and the server side) when the constraint is violated; that is, when the user input is not valid.

The message can be customized by adding an entry to the page's message catalog (or the containing component's message catalog). As with any localized property, this can also go into the application's message catalog.

The first key checked is formId-fieldId-validatorName-message.

• formId: the local component id of the Form component
• fieldId: the local component id of the field (TextField, etc.)
• validatorName: the name of the validator, i.e., "required" or "minlength"

If there is not message for that key, a second check is made, for fieldId-validatorName-message.

If that does not match a message, then the built-in default validation message is used.

http://tapestry.1045711.n5.nabble.com/T5-Overriding-integer-validation-message-td2436931.html#a2436931:

(from the answers)

You should add a prefix consisting of the field id (and optionally the form 
id). (Igor)

To generalize messages overrides for all form, you can contribute to ValidationMessagesSource service in your AppModule class with your own
property file. (Christophe)

Trial and error have yielded: [field id]-integer-message  (xfile80303)

Blogged with the Flock Browser

Dennis Stevens: We are Doing QA All Wrong

A few interesting things from an article by Dennis Stevens, very loosely quoted...

• We Don’t Understand Quality Assurance
• We Don’t Understand the Cost of Rework
• Rework from failed QA tests are extremely expensive to flow. Sending work back into development interrupts work in process. This has a dramatic effect on cycle time across the system – which results in increased cost of every item in the system.
• the cost of setting up testing environments is much lower
• Quality Assurance needs to be part of the development team and process. We need to change our thinking around this. So we need to integrate Quality Assurance very early in the process.
• We have the Wrong Expectations
• We Expect Perfection - Not Improved Value
• We Expect Local Optimization - Not Flow
• Enable value, flow, and ongoing improvement

Dennis Stevens » Blog Archive » We are Doing QA All Wrong 

From the comments:

• One thing: No one can assure quality. Can I convince you to change the reference to “Quality Assistance?” (Jon Bach)
• I prefer ‘testing’ and ‘tester’ to ‘quality assurance’ and ‘QA engineer’ or whatever. But these are nits. The message of Dennis’s post is the point – focus on value, improvement, delivering a better product. (Lisa Crispin)
• I introduce myself to teams as the “public health nurse” for their project, and then subtly place ‘quality assistance’ in my email signature. (Adam Geras) 
• testing is a complex, organic, cognitive activity, rather than a rote, bureaucratic, clerical one. (Michael Bolton)  

Blogged with the Flock Browser

TDD w/javascript using jsTestDriver and (f.ex) QUnit

JsTestDriver is seemingly yet another unit testing framework, and it stems from Google. I say seemingly, because the JsTestDriver guys has made some delicious improvements over the normal work flow which sets it apart from other unit testing frameworks for JavaScript so much it's not even funny to compare.

Having said that, JsTestDriver is (as the name implies) really more of a test runner. It ships a default assertion framework, however it doesn't offer all kinds of JavaScript specific assertions. Instead, JsTestDriver makes it fairly accomplish-able to use your current assertion framework of choice with JsTestDriver by providing a bridge. Last time I checked, both QUnit and YUI Test had functional bridges.

Test driven JavaScript done right / JavaScript - cjohansen.no

There's also an eclipse plugin.

 ff
Blogged with the Flock Browser

Using Eclipse Java Compiler Errors/Warnings – Improving your code quality » Eclipse Papercuts

I highly recommend the usage of restrictive settings here to improve your code quality.

Using Eclipse Java Compiler Errors/Warnings – Improving your code quality » Eclipse Papercuts

Blogged with the Flock Browser

Spring Batch

Many applications within the enterprise domain require bulk processing to perform business operations in mission critical environments. These business operations include automated, complex processing of large volumes of information that is most efficiently processed without user interaction. These operations typically include time based events (e.g. month-end calculations, notices or correspondence), periodic application of complex business rules processed repetitively across very large data sets (e.g. insurance benefit determination or rate adjustments), or the integration of information that is received from internal and external systems that typically requires formatting, validation and processing in a transactional manner into the system of record. Batch processing is used to process billions of transactions every day for enterprises.

Spring Batch is a lightweight, comprehensive batch framework designed to enable the development of robust batch applications vital for the daily operations of enterprise systems. Spring Batch builds upon the productivity, POJO-based development approach, and general ease of use capabilities people have come to know from the Spring Framework, while making it easy for developers to access and leverage more advance enterprise services when necessary.

Spring Batch

Blogged with the Flock Browser