Updated to use newer testing API to reduce clutter.

src/zc/buildout/runsetup.txt

@@ -16,10 +16,10 @@ that setuptools is imported means that you can use setuptools-based
 commands, like bdist_egg even with packages that don't use setuptools.
 To illustrate this, we'll create a package in a sample buildout:
 
-    >>> mkdir(sample_buildout, 'hello')
-    >>> write(sample_buildout, 'hello', 'hello.py', 'print "Hello World!"')
-    >>> write(sample_buildout, 'hello', 'README', 'This is hello')
-    >>> write(sample_buildout, 'hello', 'setup.py',
+    >>> mkdir('hello')
+    >>> write('hello', 'hello.py', 'print "Hello World!"')
+    >>> write('hello', 'README', 'This is hello')
+    >>> write('hello', 'setup.py',
     ... """
     ... from distutils.core import setup
     ... setup(name="hello",
@@ -32,15 +32,11 @@ To illustrate this, we'll create a package in a sample buildout:
   
 We can use the buildout command to generate the hello egg:
 
-    >>> cd(sample_buildout)
-    >>> import os
-    >>> print system(os.path.join('bin', 'buildout')
-    ...              +' setup hello -q bdist_egg'),
+    >>> print system(buildout +' setup hello -q bdist_egg'),
     buildout: Running setup script hello/setup.py
     zip_safe flag not set; analyzing archive contents...
 
 The hello directory now has a hello egg in it's dist directory:
 
-    >>> ls(sample_buildout, 'hello', 'dist')
+    >>> ls('hello', 'dist')
     -  hello-1.0-py2.4.egg
-