• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Browse and search Google Drive and Gmail attachments (plus Dropbox and Slack files) with a unified tool for working with your cloud files. Try Dokkio (from the makers of PBworks) for free. Now available on the web, Mac, Windows, and as a Chrome extension!

View
 

Blue Collar Labor

Page history last edited by Gerald Chang 11 years, 8 months ago

Blue Collar Labor: FileMaker Testing and Implementation

 

Let's be honest, we all love to talk about new ways to code, but there's little glory in testing and implementing code in FileMaker. This is an open forum to talk about testing and implementation best practices. What has worked for you in the past? Are you including testing and implementation into your estimate or is that something you do for 'free'?  
 
Host: Gerald Chang, Eight²

Comments (1)

Charlie Bailey said

at 5:24 pm on Nov 18, 2009

We think of testing in 4 phases: (1) developer testing, (2) in house testing, (3) beta testing, and (4) customer testing. In the (distant) past, we pretty much relied on 1 and 4 exclusively. Over the years we have ramped up our in house testing efforts as our staffing allowed and have recently been shifting our emphasis on customer testing to a true beta program. This latter effort is really a formalization of our old customer testing paradigm. The formalization of the beta program allows customers who are interested in testing and being on the bleeding edge to do so. Other customers who aren't as comfortable with that type of situation aren't put in it. This 4 phase model is appropriate for a vertical market solution, and not so much for a custom project. For custom projects, we rely more heavily on developer testing and customer testing. We find that as long as you're up front with the customer about testing expectations, customer testing can be a really powerful tool.

You don't have permission to comment on this page.