We have implemented some basic coding standards, but find that some of the coders are drifting apart (expanding the standard, without communicating). Does anyone have a set of coding standards that are working well for them? What mechanisms/tools do you use to review the source and ensure that the standard is being followed?
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by ctbrooks0: What mechanisms/tools do you use to review the source and ensure that the standard is being followed? <HR></BLOCKQUOTE>
Checklist + peer reviews.
From time to time standard should be upgraded to incorporate new approaches and techniques and remove redundant stuff.
Thanks for your reply. We'll be looking into our ongoing standards update. In the mean time, have you established some standards for "Best" coding techniques in AWL. An internet search of "VB coding standards" turns up quite a few coding standards implemented by different companies - some stressing form, others outlining "gotcha" avoidance.
Some of the results of the search are for software packages that will analyze the source against predefined rules and report exceptions.
I was curious if someone has already put together AWL coding standards to address the "gotchas" and to see what others have laid out as good form. I was also curious if anyone has automated source analysis and standards enforcement.
you can easily adopt a QARun style guide from this sample. Do NOT just hand it to your developers finished. Hold a weekly meeting to develop the guidlines for your group. Their weekly input will ensure realistic guidelines as well as consensus.
We followed documenting helpful tips to get the tool to work with our product. That list turned into a standards document that included where to put comments, wait statements, attach statments, etc. When the automation specialist was complete, they sent it to the business analyst that verified standards were followed and the intended test was met.