[openserverplatform commit] r108 - Created a page like a checklist to remind myself what to check before releasing a new vers...

[codesite...@google.com]

Author: discipleofranok
Date: Thu Apr 16 16:51:31 2009
New Revision: 108

Added:
wiki/Regressions.wiki

Log:
Created a page like a checklist to remind myself what to check before
releasing a new version.

Added: wiki/Regressions.wiki
==============================================================================
--- (empty file)
+++ wiki/Regressions.wiki Thu Apr 16 16:51:31 2009
@@ -0,0 +1,26 @@
+#summary Things to check for before each release
+#labels Phase-QA,Developer
+
+= Introduction =
+With each release bringing new and exciting features, it's important to
ensure that no bugs are introduced. Below are a list of things to test for
before moving on to more exciting features to ensure a nice solid release.
+
+= Tests =
+
+== Compilation ==
+This should be an obvious one, but ensure it can compile with no
warnings/errors from a fresh checkout/tarball release. There may be some
files not being versioned that are required for a flawless build.
+
+== Running ==
+This is a broad umbrella test to ensure that OSP is running how it should.
It should be able to compile and run from a fresh install, after updating
the configuration file(s) and running `./setup-osp.sh` and then
`./start-osp.sh`. To test this, you should be able to `telnet localhost
9876` and run the `stats` command.
+
+=== Clustering ===
+ * Ensure that with minimal effort, other nodes (both on other Erlang VMs
and other machines) can connect and the `stats` commands should show the
remote nodes.
+ * Make sure to test at least one disk-less system, to ensure that there
are no flaws with that.
+ * Be able to start, stop and migrate servlets between hosts and ensure
that the shared state is in fact, shared.
+ * Test the replication server system: after starting the applications,
start the replication server(s), then kill the Erlang VMs running the
applications. If you start them back up, they should have the same state as
before.
+
+=== Example Servlets ===
+Ensure that all the demo servlets work as as they should, both with TCP
and UDP.
+
+=== Admin Console ===
+Double check that all the commands work how they should and don't cause
any errors or crashes.
+