Changeset 96564 in vbox for trunk/src/VBox/ValidationKit/docs/AutomaticTestingRevamp.txt

Timestamp:

Sep 1, 2022 9:06:13 AM (3 years ago)

Author:

vboxsync

svn:sync-xref-src-repo-rev:

153434

Message:

Validation Kit/docs: Corrected typos.

File:

• trunk/src/VBox/ValidationKit/docs/AutomaticTestingRevamp.txt (modified) (16 diffs)

trunk/src/VBox/ValidationKit/docs/AutomaticTestingRevamp.txt

@@ -242 +242 @@
 other words, cygwin will not be used on Windows!
 
-The testbox will provide the unixy utilties that ships with kBuild and possibly
+The testbox will provide the unixy utilities that ships with kBuild and possibly
 some additional ones from tools/*.*/bin in the VirtualBox tree (wget, unzip,
-zip, and so on).  The test drivers will avoid invoking any of these utilites
+zip, and so on).  The test drivers will avoid invoking any of these utilities
 directly and instead rely on generic utility methods in the test driver
 framework.  That way we can more easily reimplement the functionality of the
-core utilites and drop the dependency on them.  It also allows us to quickly
+core utilities and drop the dependency on them.  It also allows us to quickly
 work around platform specific oddities and bugs.
 
@@ -257 +257 @@
 run under the testbox script, they can be executed in the VirtualBox development
 environment.  This is important for bug analysis and for simplifying local
-testing by the developers before commiting changes.  It also means the test
+testing by the developers before committing changes.  It also means the test
 drivers can be developed locally in the VirtualBox development environment.
 
@@ -335 +335 @@
 
   - Two level testing - L1 quick smoke tests and L2 longer tests performed on
-    builds passing L1.  (Klaus (IIRC) ment this could be realized using
+    builds passing L1.  (Klaus (IIRC) meant this could be realized using
     test dependency.)
   - Black listing builds (by revision or similar) known to be bad.
@@ -344 +344 @@
   - Useful to be able to partition testboxes (run specific builds on some
     boxes, let an engineer have a few boxes for a while).
-  - Interation with ILOM/...: reset systems.
-  - Be able to suspend testing on selected testboxes when doing maintance
+  - Interaction with ILOM/...: reset systems.
+  - Be able to suspend testing on selected testboxes when doing maintenance
     (where automatically resuming testing on reboot is undesired) or similar
     activity.
-  - Abort testing on seleced testboxes.
+  - Abort testing on selected testboxes.
   - Scheduling of tests requiring more than one testbox.
   - Scheduling of tests that cannot be executing concurrently on several
@@ -357 +357 @@
   - Configure tests with variable configuration to get better coverage. Two modes:
       - TM generates the permutations based on one or more sets of test script arguments.
-      - Each configuration permuation is specified manually.
+      - Each configuration permutation is specified manually.
   - Test specification needs to be flexible (select tests, disable test, test
     scheduling (run certain tests nightly), ... ).
@@ -367 +367 @@
     primary log associated with it.
   - Test sets stores further result as a recursive collection of:
-      - hierachical subtest name (slash sep)
+      - hierarchical subtest name (slash sep)
       - test parameters / config
       - bool fail/succ
@@ -448 +448 @@
 for a testcase.  It will schedule on a testcase level, using the combined
 priority of the testcase in the test group and the test group with the testbox
-partition, trying to spread the test case argument varation out accordingly
+partition, trying to spread the test case argument variation out accordingly
 over the whole scheduilng queue.  Which argument variation to start with, is
 not undefined (random would be best).
@@ -486 +486 @@
 the end (exclusive).
 
-Tuple-versioning has a shortcomming wrt to keys, both primary and foreign.
+Tuple-versioning has a shortcoming wrt to keys, both primary and foreign.
 The primary key of a table employing tuple-versioning is really
 'id' + 'valid_period', where the latter is expressed using two fields
@@ -494 +494 @@
 
 Foreign key references to a table using tuple-versioning is running into
-trouble because of the time axsis and that to our knowledge foreign keys
+trouble because of the time axis and that to our knowledge foreign keys
 must reference exactly one row in the other table.  When time is involved
 what we wish to tell the database is that at any given time, there actually
@@ -634 +634 @@
 
 3. If the testbox was marked as disabled, respond with an IDLE command to the
-   testbox [done]. (Note! Must do this after TestBoxStatuses maintainance from
+   testbox [done]. (Note! Must do this after TestBoxStatuses maintenance from
    point 2, or abandoned tests won't be cleaned up after a testbox is disabled.)
 
@@ -740 +740 @@
 
 Also, we need some way of dealing with 'abort' and 'reboot' commands being
-issued while waiting.  The easy way out is pretent it's a time out.
+issued while waiting.  The easy way out is pretend it's a time out.
 
 When changing the status to 'gang-timeout' we have to be careful.  First of all,
@@ -789 +789 @@
 This is a subfunction of scenario #1 and #2.  The actions taken are the same in
 both situations.  The precondition for taking this path is that the row in the
-testboxstatus table is refering to a testset (i.e. testset_id is not NULL).
+testboxstatus table is referring to a testset (i.e. testset_id is not NULL).
 
 
@@ -795 +795 @@
 
 1. If the testset is incomplete, we need to completed:
-        a) Add a message to the root TestResults row, creating one if necesary,
+        a) Add a message to the root TestResults row, creating one if necessary,
            that explains that the test was abandoned.  This is done
            by inserting/finding the string into/in TestResultStrTab and adding
@@ -939 +939 @@
 ------------
 
-The goal for this milestone is configuration and converting current testscases,
+The goal for this milestone is configuration and converting current testcases,
 the result will be the a minimal test deployment (4-5 new testboxes).
 
@@ -983 +983 @@
 
 Once deployed, a golden rule will be that all new features shall have test
-coverage.  Preferrably, implemented by someone else and prior to the feature
+coverage.  Preferably, implemented by someone else and prior to the feature
 implementation.
 
@@ -1060 +1060 @@
 :Status: $Id$
 :Copyright: Copyright (C) 2010-2020 Oracle Corporation.
-