testing, regression testing, and activating events in VBA

[belovedcej]

Okay - I have several questions.

I've been learning about testing and regression testing in Java. I totally see the value of it, but I work in Access at work and have not been able to come up with any way to test beyond just using the program to see if it works. After a while, there is a LOT to test. My boss keeps suggesting a start doing regression testing, but I don't know how I would accomplish this in any kind of automated way, like I can with Java.

How do you all work with this issue? Do you program modules that function as your test suites and run them? Or do you just plunk through testing by hand?

Also, related but not. . . .
Soemone suggested that in their programming languages it is possible to activate an event in the code. For instance, if I have a close button on the screen, some other activity could trigger a module that would "click" the close button. But I haven't figured out how to do that in VBA.

Any thoughts?

Thanks for any suggestions/experiences you can share.

 

[Darrylles]

Hi beloved,

It seems to me that you work in a LARGE organisation - it can afford to send you on JAVA 'regression testing' courses.

I would generally associate 'regression testing' with large software houses where software development is the main activity within a company.

If you don't have any idea about VBA - within Access (or any other MS product), then you are not in a software house, nor should you be trying to apply regression testing to MS Access development.

I think that your manager has got the 'wrong end of the stick' perhaps - concerning regression testing, and has thus sent you on a course that is useless to you.
It seems that you have no need to be aware of it.

Are the software development projects within your company massive? If so, why are you using MS Access?

As to your final question: when a button is clicked, if VBA is used (ONLY VBA should be used in MS Access - NOT macros), it calls a defined function.
This function can be 'activated' or 'called' via any other user 'activity' in the application simply by stating:
[tt]
call function_name
[/tt]
I think that you need to ask your boss why he thinks 'regression testing' is important, because unless your company produces massive applications which are contantly changing, with many software developers - it will not be cost-effective.

What does your company do? What is your job?

ATB

Darrylle











Never argue with an idiot, he'll bring you down to his level - then beat you with experience.

 

[belovedcej]

Thanks for the tip - knowing how to call a function will be beneficial, I believe.

I'm in an interesting situation - I work for state government. (That should explain a lot, I think. )

I am not a programmer - but I work in IT and my director has allowed me to function as a junior programmer on some small projects. (Officially, I am clerical support, but there wasn't enough to do. . . ) The programmers do create some very large applications - but I write programs for little offices that have no automation at all. The programmers use VB.Net and SQL Server 2000. I use SQL Server 2000 back end and Access front end.

I am going to school for a degree in computer science and the state is paying for some of it (there is a cap on the amount) because the policy is that a course must "apply to your job or one to which you reasonably aspire." Since that's up for interpretation, I am very lucky to have an IT director who believes I reasonably aspire to be a programmer.

BTW - I don't use macros except the AutoExec macro when the program first opens. Modules, in my opinion, allow for much more flexibility.

As for why my boss wants testing. . . Well, he came from a very large private company and hasn't quite adapted to public policies yet. We are a different world. He wants things done "right" - not that I blame him. But although he has some familiarity with programming, he is NOT a coder and will be the first to admit it.

I have spoken to the other programmers, too, about their testing techniques. They say with the style of programming we do the best that can be done is to have someone "plunk" away at the keyboard and find the bugs. But one of my project managers (again, not a coder) told me that there is software that can be purchased which will do screen testing for you, even in .Net, so you can retest after changes.

Unfortunately, I am stuck "between" my mentors and my bosses and I don't have enough knowledge to have an answer all the time. I am good with Access and fair wtih VBA, but that's as far as it goes. I have a LOT to learn.

Right now I am just milking this experience for all it's worth, because it's is very valuable and i don't have to pay for it.