Test Cases for ACCESS database

[ThisIsntMyRealName]

I've been asked to generate some test cases for some formal testing of an access project. Does anyone have any good examples of something like that?

Thanks for your time,

 

[HiTechCoach]

What you are asking for is generally very application specific.

It would help if you would post a sample of your database.

If your database split?

 

[ThisIsntMyRealName]

What I really need is like 10 or 20 examples, just so that I can write my own test cases for my own databases because ive never done formal testing like that before.

 

[xenou]

I don't think there's any general examples available. Test data would imitate the live data you would use in your database. If your database is for recipes, test data would include recipes. If your database was books, test data would include authors, publishers, and book titles ... and so on. If you are testing input, you may need to input the data through your database forms (to test that they work as expected). If you are testing output (reports, analysis) then your test data can be loaded directly to the tables. I don't think test data has to be extremely large per se - just covering the ranges of possible inputs (hit the minimums, maximums, try different kinds of "bad" data such as numbers in bad formats, dates that don't exist, negative quantities, leaving fields blank ... etc.) In other words, try to break the database - input orders without PO's, ship orders without addresses, and so on.

 

[ThisIsntMyRealName]

Guys, what I mean perhaps is functional testing steps, for example:

A user clicks button A, and the application displays the current date: pass/fail.

Something of this nature.

 

[xenou]

I'm lost. It's a trivial task to display the current date with a message. Whatever your testing involves I suspect the nitty gritty will go beyond that. For instance, determining whether the test has passed or failed ...

For example, if a form is supposed to create a new record, I check to see if the new record is created. You can do this any way you like - usually I just view the table to see if the record is there. If you require output to a message box you can query the table to see if the new record was added, then display the result of the query, or show the count of records returned, and so on.

Your question is very general so it's hard to be more specific.

 

[Norie]

This doesn't quite sound like 'formal' testing, to me anyway.

That would probably involve writing test scripts to check every possible scenario, analysing the results etc

You try, as xenou suggests, to break the database in whatever way you can think of and then some more.

Start with obvious stuff and then work down (up?) to more obscure things that could happen but are unlikely to happen.

 

[HiTechCoach]

I don't think test data has to be extremely large per se -

Unless you are load testing then you need large amounts of data

 

[HiTechCoach]

What I really need is like 10 or 20 examples, just so that I can write my own test cases for my own databases because ive never done formal testing like that before.

Sounds agile. Are yoy wanting to do Unit testing?

This may help: VBAUnit

also: Unit testing for VBA in 2 minutes

 

[xenou]

Unless you are load testing then you need large amounts of data

Care to say why?