Live Test Site vs. Local Site

[pandaa]

In the past, I've used live test sites as well as sites hosted on my computer. What do you think are the advantages and disadvantages of these two ways to set up "test" sites, and which do you prefer?

 

[leelanarasimha]

Having Test site in live is better.

I personally use one beta server for test site and the actual live site will be working on the top of it

 

[pandaa]

Having Test site in live is better.

Why would you say that?

 

[Ash]

I always have live test sites. Helps me as everything is already on the hosting servers and nothing extra needs to be moved or setup

 

[Carson]

For web development, I do it locally. I'll push to a server if I want to show someone what I'm working on. Being able to do work offline is nice, plus it makes collaboration with others easier.

I also don't have to pay a subscription fee for my computer.

 

[Quacker Jack]

In general, depending on the scope of the project and how big of an undertaking it is, and how well you want it worked out, I think it is best to do a Local Host version first for an "Alpha" stage, where you are essentially trying to make it functioning. I would then move to a live test site to commence a "Beta" version, where others can contribute and catch bugs.

 

[leelanarasimha]

Having Test site in live is better.

Why would you say that?

According to me beta site should be there in order to perform TDD(tests).

After all completing the testing we will be moving to the live server from beta site.

When new changes comes first it should be pushed to beta site and after checking when it is free from all bugs. It would be pushed to live site.

This will be the safest method according to me.

 

[Cosmic]

I usually have my stuff on localhost. I haven't used a live test site in a while, except when I have something that I need to demo to a good number of people.

 

[cyimking]

It depends on the situation. I prefer to handle all development testing on my localhost, push it onto a private server (to test for server loads, etc...) then push it live... Also it make it MUCH easier to work with a large team if team members can go onto a private server to view the code to debug it and etc... but if you are working alone then just push it live. No need for a middle man.

 

[Luke]

I prefer a live test site, just because it's easier. I can access it from anywhere on any device. I could be on a university computer and still be able to continue developing.

 

[pandaa]

I can access it from anywhere on any device.

Good point! It would be pretty difficult to test out a mobile site on localhost, or even how a site would look on a different sized monitor. Especially given how many sites are responsive now, I think it's well worth having a live copy of the site after you've done a good portion of the coding.