[Checkins] SVN: Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/ Update ftests to reflect new package name.

[Uli Fouquet]

Log message for revision 87574:
  Update ftests to reflect new package name.

Changed:
  U   Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/brokenobjs.py
  U   Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/docgrok.py

-=-
Modified: Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/brokenobjs.py
===================================================================
--- Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/brokenobjs.py	2008-06-19 21:56:36 UTC (rev 87573)
+++ Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/brokenobjs.py	2008-06-19 21:59:05 UTC (rev 87574)
@@ -55,7 +55,7 @@
  ...
  ...Broken applications:...
  ...
- ...(broken type: grok.ftests.admin.brokenobjs.PseudoBroken)...
+ ...(broken type: grokadmin.tests.brokenobjs.PseudoBroken)...
  ...This application is broken!...
  ...
 

Modified: Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/docgrok.py
===================================================================
--- Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/docgrok.py	2008-06-19 21:56:36 UTC (rev 87573)
+++ Sandbox/ulif/grokadmin/trunk/src/grokadmin/tests/docgrok.py	2008-06-19 21:59:05 UTC (rev 87574)
@@ -18,7 +18,7 @@
 
 DocGrok offers an extensible class browser for packages, modules,
 classes and similar things. To use it in your own application see
-``docgrok.txt`` in the ``grok.admin`` package.
+``docgrok.txt`` in the ``grokadmin`` package.
 
 Here only the functionality as a class browser for the admin-UI is
 covered.
@@ -85,11 +85,11 @@
 Okay. In the page top we should have links to the various parent
 packages contained in the dotted name of the examined package:
 
-  >>> browser.getLink('grok')
-  <Link text='grok' url='http://localhost/docgrok/grok'>
+  >>> browser.getLink('grokadmin')
+  <Link text='grokadmin' url='http://localhost/docgrok/grokadmin'>
 
-  >>> browser.getLink('ftests')
-  <Link text='.ftests' url='http://localhost/docgrok/grok/ftests'>
+  >>> browser.getLink('tests')
+  <Link text='.tests' url='http://localhost/docgrok/grokadmin/tests'>
 
 and so on.
 
@@ -135,11 +135,11 @@
 done below.
 
 The *DocGrok* classes should be derived from
-grok.admin.docgrok.DocGrok, so that they automatically provide some
+grokadmin.docgrok.DocGrok, so that they automatically provide some
 useful information like the Python path of an object and similar.
 
 The *DocGrokHandlers* should be derived from
-grok.admin.docgrok.DocGrokHandler to be registered automatically on
+grokadmin.docgrok.DocGrokHandler to be registered automatically on
 startup. It must provide a method ``getDoctor(dotted_path,
 obj=None)``, which returns a DocGrok object iff the given dotted_path
 denotes a thing of the appropriate type. In the example below we
@@ -170,7 +170,7 @@
 To check this, we have a look at the docgrok class browser. First we
 have a look at the module, the class is contained in::
 
-  >>> browser.open("http://localhost/docgrok/grok/ftests/admin/docgrok")
+  >>> browser.open("http://localhost/docgrok/grokadmin/tests/docgrok")
 
 In this page, there should be a link available to our Mammoth class,
 as defined below::
@@ -180,7 +180,7 @@
   'Mammoth'
 
   >>> link.url
-  'http://localhost/docgrok/grok/ftests/admin/docgrok/Mammoth'
+  'http://localhost/docgrok/grokadmin/tests/docgrok/Mammoth'
   
 If we click on this link, we normally would get a usual class
 documentation page as generated by the docgrok for classes. But, while
@@ -195,8 +195,8 @@
 
 """
 import grok
-from grok.admin.docgrok import DocGrok, DocGrokHandler
-from grok.admin.view import DocGrokView
+from grokadmin.docgrok import DocGrok, DocGrokHandler
+from grokadmin.view import DocGrokView
 
 class Mammoth(object):
     """A (large) thing, we want to document later on.