Add new testing framework along with a few micro-tests.

util/README

Index: util/README
diff --git a/util/README b/util/README
new file mode 100644
index 0000000000000000000000000000000000000000..cb99d67ed69d0a677aed584c1d0ab4a00b6e92f3
--- /dev/null
+++ b/util/README
@@ -0,0 +1,29 @@
+Flashrom Testing
+
+Overall idea:
+- Break tests into small chunks
+- Have a single program that does generic setup and shutdown functions
+- Executes specified tests in a simple loop
+
+Dependencies:
+- uuencode
+- diff
+- A version of flashrom which is installed in $PATH

[Stefan Reinauer, 2010/11/23 19:05:30]

Really? It would be very nice not having to rely on flashrom being installed in
the system path in order to run those tests.
Or is this supposed to be a "known good" version used for recovery at the end?
Please clarify

[dhendrix, 2010/11/24 02:48:14]

It is intended to be the "known good" version used for obtaining a backup copy
at the beginning and recovery at the end. I've elaborated the comment to reflect
that.

+
+Important environment variables:
+FLASHROM: Path to the Flashrom binary to test
+FLASHROM_PARAM: Parameters to pass into flashrom

[Stefan Reinauer, 2010/11/23 19:05:30]

The example below indicates that this would be used to set the programmer to be
used for the testing. Are there limits? Would it make sense to pass -w or -V as
a parameter?

[dhendrix, 2010/11/24 02:48:14]

Good point. Chip operations such as -r and -w are redundant and should
(hopefully) cause flashrom's command parser to fail. -V ought to be fine.

I've added a comment to instruct the user not to specify chip operations.

+
+Important global variables:

[Stefan Reinauer, 2010/11/23 19:05:30]

Why are you differentiating between global and environment variables?

[dhendrix, 2010/11/24 02:48:14]

Good question. That bit about global variables does not need to be in this
document. It's intended to let developers know what variables they may use from
the master script.

That sort of thing should be documented in the master script itself, and the
README should be kept simple for normal users.

+BACKUP: The backup copy of ROM image which is read before executing any tests,

[Stefan Reinauer, 2010/11/23 19:05:30]

Does this have a default, if BACKUP is not set by the user/tester?

[dhendrix, 2010/11/24 02:48:14]

Heh, this is probably why it should be documented in the code :-)

There is no default -- BACKUP is the image which the known good version of
flashrom reads at the beginning, ie:
BACKUP="backup.bin"
${FLASHROM} ${FLASHROM_PARAM} -r ${BACKUP}

+        and restored unconditionally after execution of tests.
+
+Syntax:
+ENV_VARS="blah" ./do_tests.sh <test1> <test2>
+
+Example:
+FLASHROM="../flashrom" FLASHROM_PARAM="-p internal:bus=spi" ./do_tests foo.sh bar.sh
+
+Each unit test might have its own special requirements, such as extra
+environment variables, layout files, etc. Please read the comments at the top
+of each unit test to ensure there are no special dependencies.