ATDD for team communication
Acceptance Test Driven Development, or ATDD, is a very effective technique for driving and guiding development, that helps enhancing communication between developers and other project stakeholders, document your product, and report on project progress.
Choosing a testing path
Firstly, I should say that I am always writing from perspective of someone who works in multiple industry, but majority is within web application development. I am a real fan of Acceptance Test Driven Development (ATDD), which has many similar variants:
Visual Studio 2010 : Looping tests using CSV input
To do this, you need to adjust the Test Settings, available in the Test menu. If you leave the default settings, and you are using csv input, the test will only run once (i.e. take the first line from csv file). Within dialog, select Web test then “One run per data source row” It is [...]
TB-303 – Legendary, down to exploratory testing
The 303 – gave birth to music culture, that I still follow today – techno (a very maligned and misunderstood form of music, but then I am biased). As with all technology there are rules, but they can be manipulated to discover something new. Something Roland is figure on was a sound that wasn’t even [...]
VS2010 Automated Testing – Extraction Rules and Conditions
To validate values on screen is easy, as Visual Studio provides method of extraction values displayed on screen in a number of ways. I found the most reliable is to extract using relevant field id and/or name, but good markup practices are not always observed. The method demonstrated here is to use the html code [...]
Blame it on Agile
Waterfall vs Agile? Unnecessary. Waterfall’s defined stages allow for thorough planning, especially for logical design, implementation and deployment. Agile methodology is a sound choice for development. Agile management processes are still being devised – it was all very well accusing business of not being Agile, but they hadn’t been provided with any kind of Agile [...]
Agile test automation
How does automated testing fit into Agile? It hasn’t changed that much, but a sensible approach (assuming development process is also sensible), is to do a combined UI and code level test, so you minimise the high-maintenance part (the UI tests). UI tests are always appealing, as easy to generate (with fine tuning, of course) [...]
