How do you test things without clients seeing it?

Discussion of testing theory and practice, including methodologies (such as TDD, BDD, DDD, Agile, XP) and software - anything to do with testing goes here. (Formerly "The Testing Side of Development")

Moderator: General Moderators

User avatar
Jenk
DevNet Master
Posts: 3587
Joined: Mon Sep 19, 2005 6:24 am
Location: London

Re: How do you test things without clients seeing it?

Post by Jenk »

"It's work in progress" solves that one, and it is a lot easier to handle "It's got a bug" than it is "I didn't ask for this. Why have you spent 2 months working on this? It's a complete waste of time!"
josh
DevNet Master
Posts: 4872
Joined: Wed Feb 11, 2004 3:23 pm
Location: Palm beach, Florida

Re: How do you test things without clients seeing it?

Post by josh »

Well a refactoring should not introduce new functionality or bugs, but when a refactoring is only halfway done it certainly could alter the functionality!

I agree though on handling bugs vs explaining wasted time, but I was saying a larger refactoring before putting the new functionality
malcolmboston
DevNet Resident
Posts: 1826
Joined: Tue Nov 18, 2003 1:09 pm
Location: Middlesbrough, UK

Re: How do you test things without clients seeing it?

Post by malcolmboston »

I have been known to do this on the live server of a successful eCommerce store.

I only ever do it if i must interact with the real data but if you do need to do it, just lock it down to your IP

Code: Select all

 
if ($_SERVER['REMOTE_ADDR'] == '65.myip.923.23') {
    // execute my code here
}
 
 
Post Reply