Best way to test a mdb file before production

[rewdee]

I know this is technically not the best forum but I think it has the most knowledgeable programmers so I'm posting in this forum:

Most places that I have worked for you alpha check your work on your desktop. If the work is good, you import the tables, forms, etc. to a beta testing environment that you have worked on. If they passed tests, the tables, forms, etc are imported to a production mdb file.

My current contract has no alpha plan. When they move beta stuff on the test environment to production, they move the whole mdb file (essentially replacing the previous production mdb file). I have only worked for about a year and half but I tried to point out the risks and defficiencies of this process.

I was basically told this is standard practice here. How do most companies test their work? Does anyone have any documents that show what is standard practice that I can refer to?

Thanks,
Rewdee

 

[Francescina]

Every serious software developer knows that it is impossible to create (new) application without a minimum number of errors (bugs or quirks).

Even if you manage to have a 100% bullet proof error trapping procedure including lock errors you can be certain that the performance of your application has not been optimized.

If you then have a customer who wants to work with the just installed new application the probability that you will have a VERY bad time (ranging from headache to letters from your customer's lawyer).

The most recommended procedure:
1.) finish your application until you think that it is error-free and 100% performant
2.) Let the customer test the application, record the errors and correct them.
3.) Let an independant developer (who never saw your app before) test it and write a quote about your work
4.) Integrate the results of 3.)
5.) Let your customer test the application again.

Happy programming!