“Would you trust a programmer to test your application? It’s like asking a Fox to guard the chicken-house, right?” This is the beginning of this post that deals with the issue of having programmers testing their own code.
Selenium is an open source project with no formal guidance, making problem investigation time-intensive for testers. This article provides best practices for common issues during testing based on Selenium 1.0, which was released in June 2009.
Many of the most common problems people have with implementing BDD or agile acceptance testing come from a misalignment of conceptual models. By changing our view at the specifications/tests we can make most of those issues go away instantly. This post explains the principle of symmetric change: one small change in a business model should require one small change to executable specifications.
This website presents a list of open source and commercial continuous integration tools. http://www.continuousintegrationtools.com/
Testing is a fundamental part of the Agile process. We live and breathe TDD/BDD. Red/Green/Refactor is our daily mantra. We love cucumber and writing executable, customer readable specifications. We even write tests for our JavaScripts.
Javascript becomes much more important to interactive website development then before (ok it has been for a while already) but the notion of testing that logic seems even further fetched then testing the code written in C#, Java. And this is something that is wrong as well.
This blog post is about the fact that testers are probably the biggest generalists on any team and they should try to pair with other development roles to increase their knowledge.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates