By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,870 Members | 2,400 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,870 IT Pros & Developers. It's quick & easy.

Automated test of Access application

P: 5
Hi guys,

Have you created an application that provide Automated test for Access application. What I mean from the Automated test is The Access Form will be open, all text fields will be populated, automate button click event on the form that results to opening the second Access form, etc.

Any idea how to achieve this.

Thank you, any help will be very much appreciated.
May 15 '07 #1
Share this Question
Share on Google+
6 Replies


Rabbit
Expert Mod 10K+
P: 12,366
Hi guys,

Have you created an application that provide Automated test for Access application. What I mean from the Automated test is The Access Form will be open, all text fields will be populated, automate button click event on the form that results to opening the second Access form, etc.

Any idea how to achieve this.

Thank you, any help will be very much appreciated.
I suppose you can use the On Load event. And then code whatever you want to automate. As for the button click, use a different sub and call it for the automation process and the button click.
May 17 '07 #2

JConsulting
Expert 100+
P: 603
Hi guys,

Have you created an application that provide Automated test for Access application. What I mean from the Automated test is The Access Form will be open, all text fields will be populated, automate button click event on the form that results to opening the second Access form, etc.

Any idea how to achieve this.

Thank you, any help will be very much appreciated.
Normally this kind of aumated testing is done using a large scale software package like WinRunner or TestDirector

These packages are geared to provide threshold testing and reporting.
J
May 19 '07 #3

P: 5
Hi Rabbit,

Thanks for your input ...

This is one of the solution, but then I need to put the code on every onLoad event in the form. And To switch between test mode and live mode is very hard thing to do (when you have sequence of form to be tested.)
May 21 '07 #4

P: 5
Normally this kind of aumated testing is done using a large scale software package like WinRunner or TestDirector

These packages are geared to provide threshold testing and reporting.
J
Hi JConsulting,

Ok, I'll look into it ... But if it cost alot then it wont be the solution :P
May 21 '07 #5

Rabbit
Expert Mod 10K+
P: 12,366
Hi Rabbit,

Thanks for your input ...

This is one of the solution, but then I need to put the code on every onLoad event in the form. And To switch between test mode and live mode is very hard thing to do (when you have sequence of form to be tested.)
Switching between modes isn't hard at all. Just code everything in a normal module and have a global variable to switch between test mode and live mode.
May 21 '07 #6

NeoPa
Expert Mod 15k+
P: 31,489
PW,
Probably the best way to switch between Debug & Live mode is to have a 'Conditional Compiler' definition. This way the code is only created for the version that matches your current needs. I've included some sample code (Excel VBA but same concept for Access)
Expand|Select|Wrap|Line Numbers
  1. '#Const conDebug = True     'Only when the project is still in development mode.
  2. ...
  3.             Select Case strType
  4.             Case "Refresh"
  5.                 If strMode = "Process" Then
  6.                     Call .Calculate
  7. #If conDebug Then
  8.                     .ScreenUpdating = True
  9.                     .ScreenUpdating = False
  10. #Else
  11.                     Set shtThis = ActiveSheet
  12.                     Worksheets("Data").Visible = xlSheetVeryHidden
  13.                     .ScreenUpdating = True
  14.                     .ScreenUpdating = False
  15.                     Worksheets("Data").Visible = xlSheetVisible
  16.                     Call shtThis.Select
  17. #End If
  18.                 End If
  19.             Case "Process"
  20. ...
If the {#Const conDebug = True} line is commented out, then the {#If conDebug Then} evaluates to FALSE.
Jun 2 '07 #7

Post your reply

Sign in to post your reply or Sign up for a free account.