Sandbox (software development)

A sandbox is a testing environment that isolates untested code changes and outright experimentation from the production environment or repository, in the context of software development including Web development and revision control. Sandboxing protects "live" servers and their data, vetted source code distributions, and other collections of code, data and/or content, proprietary or public, from changes that could be damaging (regardless of the intent of the author of those changes) to a mission-critical system or which could simply be difficult to revert. Sandboxes replicate at least the minimal functionality needed to accurately test the programs or other code under development (e.g. usage of the same environment variables as, or access to an identical database to that used by, the stable prior implementation intended to be modified; there are many other possibilities, as the specific functionality needs vary widely with the nature of the code and the application[s] for which it is intended).

The concept of the sandbox (sometimes also called a working directory, a test server or development server) is typically built into revision control software such as CVS and Subversion (SVN), in which developers "check out" a copy of the source code tree, or a branch thereof, to examine and work on. Only after the developer has (hopefully) fully tested the code changes in their own sandbox should the changes be checked back into and merged with the repository and thereby made available to other developers or end users of the software.[1]

By further analogy, the term "sandbox" can also be applied in computing and networking to other temporary or indefinite isolation areas, such as security sandboxes and search engine sandboxes (both of which have highly specific meanings), that prevent incoming data from affecting a "live" system (or aspects thereof) unless/until defined requirements or criteria have been met.

In web services

The term sandbox is commonly used for the development of Web services to refer to a mirrored production environment for use by external developers. Typically, a third-party developer will develop and create an application that will use a web service from the sandbox, which is used to allow a third-party team to validate their code before migrating it to the production environment. Microsoft,[2] Google, Amazon.com,[3] PayPal,[4] eBay[5] and Yahoo,[6] among others, provide such services.

In wikis

Wikis also typically employ a shared sandbox model of testing, though it is intended principally for learning and outright experimentation with features rather than for testing of alterations to existing content (the wiki analog of source code). An edit preview mode is usually used instead to test specific changes made to the texts or layout of wiki pages.

See also

References

  1. ↑ Vivek Venugopalan, "Developer Sandbox" chapter 4, CVS Best Practices, The Linux Documentation Project, 2005. (See also Google for numerous other examples from the CVS FAQ, SourceForge, etc.)
  2. ↑ "Microsoft UDDI Business Registry (UBR) node". Archived from the original on 2005-11-07. Retrieved 27 July 2012.
  3. ↑ "Amazon Mechanical Turk Developer Sandbox". amazon.com. Retrieved 27 July 2012.
  4. ↑ "PayPal Sandbox User Guide" (pdf). paypal.com. Retrieved 27 July 2012.
  5. ↑ "eBay Developer's Sandbox". ebay.com. Retrieved 27 July 2012.
  6. ↑ "Enterprise Web Services: Sandbox". yahoo.com. Archived from the original on 2008-01-19. Retrieved 27 July 2012.
This article is issued from Wikipedia - version of the Friday, April 15, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.