tag:blogger.com,1999:blog-6005334108330583722.post8868919999994595688..comments2010-01-13T02:29:16.003-05:00Dawnhttp://www.blogger.com/profile/00149191486108175617noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6005334108330583722.post-56985067093892338012010-01-13T02:29:16.003-05:002010-01-13T02:29:16.003-05:00What I would look out for in the long run is that the rule you now set up with the QA environment matches the production as likely as possible, might become constraining.<br /><br />Let me elaborate what I ran into over the holidays while at work. Our product runs on Java5, since August FitNesse runs on Java6. I exchanged in every code branch java5 through java6 to make it compile again. When I had started up a system I noticed, that I could no longer create customers in the database. When I realized that the only chaneg was Java5 to Java6, I knew there was problem with the implementation. So, I opened up a bug. In the new year I got contacted by two developers from the same team about it. (Note: Bureaucracy is the percentage of what you&#39;re doing that you don&#39;t understand why you&#39;re doing it.) The first developer was highly motivated to investigate the bug and asked to do several things with my system and try to reproduce it. Basically he was pin-pointing the problem. The second developer the next day told me that our product is just &quot;certified&quot; for Java 1.5.0_15 according to document XYZ. Two days later the first developer had fixed the problem in the next release, which is run on Java6 and where the problem still existed. The release of this product is planned for February or March. And I don&#39;t directly test that product.<br /><br />By trying a bit more than the constrainted way, I was able to find a bug in a component, which I was not testing, which might have popped up and caused really big trouble in production for the next release. So, always working after the rules might be a bad thing to do. Hopefully your team is able to transform your new rule over time into a guide and see its limitations.Markus Gärtnerhttp://www.blogger.com/profile/15728306418553053255noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-26975407010456020732010-01-13T00:06:08.922-05:002010-01-13T00:06:08.922-05:00Sounds like a good team. Little changes that can make things better really add up.Johnhttp://www.blogger.com/profile/12298040969043446972noreply@blogger.com