Page 1 of 1

testing account

Posted: Thu Feb 17, 2005 4:13 am
by wizzard81
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?

Posted: Thu Feb 17, 2005 4:27 am
by markl999
So that the customers have no worries while testing the code?
Customers testing the code? :o
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.

..

Posted: Thu Feb 17, 2005 9:35 am
by s.dot
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.

Posted: Thu Feb 17, 2005 9:38 am
by Maugrim_The_Reaper
You should test your own code prior to anyone else... Putting untested code online for public consumption is just adding unnecessary risk...

Posted: Thu Feb 17, 2005 10:02 am
by Chris Corbyn
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 :-)