Document Actions
Testing Code in the Staging Site
This note describes the process of testing code.
In what follows, code refers to TAL, Python Scripts, and External Methods. This discussion is relevant to the work of Core Developers and Designers.
A Core Developer has created a new portlet. Code consists of
several Page Templates and External Methods. Further, the
configuration of a few Plone Tools have been changed.
Tests in the development sandbox are encouraging, so he contacts
the Site Administrator about going live with the work.
A Designer has worked up a new skin for a large section of the same
site, and also wishes to go live. The Site Administrator feels there
is enough to warrant a staging effort.
The Core Developer and Designer each prepare a list of the items
that are affected by their recent work. The Site Admin identifies
any common objects in the two lists. The Site Admin arranges
to have the staging site refreshed with a current snapshot
of the production site.
Under the direction of the Site Administrator, a
Core Developer copies and updates objects in the staging
site under /home in the development Zope instance.
This Core Developer maintains a log of every step taken.
The Site Administrator engages another user to test the
staging site. It is the responsibility of the Site
Administrator to ensure that adequate testing is
performed. If testing fails, the staging site is scratched
and the issue is sent back to the sandboxes.
If testing succeeds, the next step is moving to production.