debugging an application for deployment, advice?

I'm about to deploy my first VB application to a customer... I need some advice.

I am attempting to do extensive beta-testing before I deploy the application and would like to know how I should perform this from others who have done it.

First, I placed in each function/subroutine:

function doSomething
  on error goto doSomethingError

  'whatever I put in the function
  exit function
doSomethingError:
  Msgbox "Error found at doSomething " & err.Description
end function

is this the best way to catch errors during the testing phase and during the release?

Also I will have a few other individuals testing the application on different computers since I know that being the developer I probably am used to running it a particular way and they can find things I won't think of. What else can I do to make sure the deployment is successful? Is there anything else in VB I should implement that will be very good to have before or during deployment? Please let me know. I have completed a java application before that worked great on release but I'm still kind of new with VB stuff so in a sense you can consider me a beginner on deployment in VB. ;-) thanks for any advice

guid
LVL 12
guidwayAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
1markmcConnect With a Mentor Commented:
Create an error log and have the testers send this log to you periodically.  Code your application to writing to the error log to include the module name as below:

WriteToLog Err.Number, Me.Name & ".GetTestResults " & Err.Source, Err.Description

0
 
guidwayAuthor Commented:
one more question (I'll raise the points since this is an add-on question). Should I use the native VB errors in the subs/functions or raise my own using Err.Raise ?

just curious which is better... thanks

guid
0
 
guidwayAuthor Commented:
I'll give time for anyone else to comment with ideas and close this tomorrow morning... thanks to any who respond. I appreciate it!

guid
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
rettiseertConnect With a Mentor Commented:
Hi

You can use Erl to get the number of the line where the error was generated (you'll have to put a number to every line where an error can happen)

Function doSomething()
   On Error Goto doSomethingError
   10   a = 1
   20   a = a / 0     'Division by 0, an error is generated here
   30   a = 2
   Exit Function

doSomethingError:
   MsgBox "Error found at doSomething at line" & Str(Erl) & vbCrLf & "Error number:" & Str(Err.Number)

End Function
0
 
MADisonMANConnect With a Mentor Commented:
Additionally you can generate email to specific tech/group at the end depending how critical the error is. And u can also add the followings to the log file:

date/time stamp
user/domain info
machine/os info
module info where Err occurs
some test results
Err.Number and Err.Description
0
 
guidwayAuthor Commented:
thanks everyone, I've integrated almost every idea in the application. :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.