Archives
Thank you, Thank you, Thank you!!!!
Submitted by Antony Marcano on Fri, 01/02/2008 - 12:23. this.siteThis is a special thank you to everyone who has contributed to the testingReflections community... Thanks to all those visitors and thanks to all the content providers (who I hear receive plenty of good traffic in referrals from TR ;-)
January 2008 saw the largest number of unique visitors and page impressions for TR so far...
Unique visitors: 32,382 (19 robots) Number of visits: 88,995* Pages: 264,866* *excluding robots
This has inspired me to spend more time working on TR (as some of you now affectionately call it)... this is going to take time and money... almost all my own at the moment...
If you would like to contribute, feel free to donate (see link in right column)... or if you are a corporation and want to expose your brand to all these TR users, get in touch via admin/at\testingReflections/dot\com.
Once again, many thanks...
-Antony
phpBugTracker 1.0.4 released
Submitted by Opensourcetesting.org - latest news on Fri, 01/02/2008 - 13:53.RTH 1.6.3 released
Submitted by Opensourcetesting.org - latest news on Fri, 01/02/2008 - 13:56.End of NUnitAsp Development
Submitted by Opensourcetesting.org - latest news on Fri, 01/02/2008 - 14:02.Concordion 1.1.0 (similar to the Fit acceptance testing framework)
Submitted by webmaster@testdriven.com (News) on Fri, 01/02/2008 - 15:48.Concordion is an alternative to the Fit Framework, for writing acceptance tests.
What users are saying: "a lot more intuitive than Fit", "we've rewritten all our existing Fit tests in Concordion", "impressive", "one to keep your eye on"
Exploratory Testing: Finding the Music of Software Investigation
Submitted by webmaster@testdriven.com (Links) on Fri, 01/02/2008 - 15:49.No More Iterations
Submitted by iclemartin on Fri, 01/02/2008 - 21:55.We've committed to iteration-less pull based software development starting on Monday for one of my teams. A number of factors led up to this decision, not to mention the vast amount of discussion I had with my project managers.
The factors:
- Story size was difficult to estimate and kept crossing iteration boundaries.
- The programmers really didn't see the value of estimating stuff they weren't familiar with and in our planning poker session gave out lots of ? and 100 cards.
- I am looking for a good departmental metric for the rest of the company to see how development is doing and Velocity is always too abstract.
- We were spending to much time researching the time it would take to fix a bug that we weren't going to work on for several weeks.
- There was invisible work being performed.
- We had a tool (Rally) that wasn't really being used as intended.
- The scheduling process seemed overly complicated.
- We didn't have a great way to express the result of adding "one more thing" to the release.
- We are just about to get a true single backlog per product line.
What we are ending up with:
