Hello,
I have a question, if you work on a big project with different modules do you often work with a test account? So that the customers have no worries while testing the code?
What i mean is if the project is getting bigger and bigger and you are doing updates that you can test if everything works with a test account?
testing account
Moderator: General Moderators
Customers testing the code?So that the customers have no worries while testing the code?
Shouldn't you test it before it goes live to customers?
I tend to use Unit Testing just to make sure any new code won't break anything and also have a various test accounts just to be sure the different levels of access work ok etc.
..
Eh ;/ this probably wouldn't be reccommended but I always save a backup of my page, edit it to what I'd like, then let people try it out. If there's any problems that I can't fix I can restore my back up and try again.
- Maugrim_The_Reaper
- DevNet Master
- Posts: 2704
- Joined: Tue Nov 02, 2004 5:43 am
- Location: Ireland
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
You should always test your own code once, twice, three times... over and over on as many browsers, versions and Operatinbg systems as you can get hold of... then test a bit more...
I think the original questions was whether developers create a testing account for this kind of thing... of course the answer is yes!... test it as if you were a member of the public and simulate every possible eventuality the you'll cover as much as you can... Hope fully
I think the original questions was whether developers create a testing account for this kind of thing... of course the answer is yes!... test it as if you were a member of the public and simulate every possible eventuality the you'll cover as much as you can... Hope fully