[Zope-CVS] CVS: Packages/FunctionalTests - ISSUES.txt:1.4

[Tres Seaver]

Update of /cvs-repository/Packages/FunctionalTests
In directory cvs.zope.org:/tmp/cvs-serv26739

Added Files:
	ISSUES.txt 
Log Message:
 - Lay in last set of updates (not yet finished).


=== Packages/FunctionalTests/ISSUES.txt 1.3 => 1.4 ===
--- /dev/null	Sat Apr  2 18:22:23 2005
+++ Packages/FunctionalTests/ISSUES.txt	Sat Apr  2 18:21:52 2005
@@ -0,0 +1,99 @@
+Issues (as of 2003/03/03)
+
+  Shane, DemoStorage
+
+    - Second buildout, with modified zopectl which pointed to it;
+      FunctionalTests package integrated into the buildout.
+
+    - Manual restart between scenario runs.
+
+    - Separate starter bases contemplated
+
+  Ken, zopectl
+
+    - Needed end-to-end testing for syndication (multiple servers,
+      etc.)
+
+    - Started with an external method as an invokable storage.
+
+    - Started to morph to use 'zopectl debug'.
+
+    - Connections between servers are outside of transaction used
+      by EM.
+
+    - Interest in using 'zope debug' with assertions.
+
+      o Something like Zope3 'ftest' stuff.
+
+  Jim, application mods
+
+    - Working with Andrew
+
+    - Pitfalls notes
+
+    - Test for creating ZRM site
+
+    - Setup needs empty ZODB
+
+    - TCPWatch recorded fine
+
+    - ScenarioGenerator needed some massaging
+
+      o Underscore bug (squished)
+
+      o prefix / extension clash with TCPWatch
+
+      o redirect code wasn't captured ???
+
+    - Runner breakage
+
+    - Debugging failures hard:  the useful information doesn't
+      make it back out to the runner (swallowed by the error log)
+
+    - Setup / teardown / verification via a test tool, which
+      contained methods for examining ZODB objects.
+
+    - Disabled timing (later figured out how to spell it).
+
+    - Cleanup not executed if error (Rob:  DemoStorage might obviate);
+      check the spelling?
+
+  Zac
+
+    - Form fields with hyphens in the name break the runner.
+
+    - Dependency management would be nice (reuse sections of scenarios?)
+
+    - "Commitable" demo storage.
+
+  Andrew
+
+    - Scenario creation by hand would be possible. 
+
+    - Python for setup / teardown / verification nice.
+
+  Gary (Casey, Ken) "zopectl kids"
+
+    - Could integrate with other approaches.
+
+    - Wanted to use 'zopectl run sometest.zft'
+
+    - Layering sets of transactions (resetting back to several
+      "known good" starting points) (without rebuild)
+
+    - 'CheckpointManager' using ZODB Undo;  resets to known transaction
+      ID after (tids on a stack).
+
+      o Use ZEO to configure starting points.
+
+      o Would work well on top of DemoStorage.
+
+    - Starting from empty ZODB important!
+
+  Tres
+
+    - Known bad:
+
+      o Multi-part form lossage
+
+      o PUT, OPTIONS, PROPFIND, etc.