Changeset 61474 in vbox for trunk/src/VBox/ValidationKit/docs

Timestamp:

Jun 5, 2016 9:02:01 PM (9 years ago)

Author:

vboxsync

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

107801

Message:

testmanager: Preparting TestSets for TestBoxes belonging to more than one scheduling group by storing the idSchedGroup in TestSets as well (this has a slight speed up effect on grouping results by scheduling group too of course). The idSchedGroup column in TestBoxes will be changed into a M:N table later some time. Also corrected a typo regarding orphaned tests.

Location:

trunk/src/VBox/ValidationKit/docs

Files:

• AutomaticTestingRevamp.html (modified) (4 diffs)
• AutomaticTestingRevamp.txt (modified) (4 diffs)

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

@@ -946 +946 @@
 <li><p class="first">If the testbox was marked as disabled, respond with an IDLE command to the
 testbox [done]. (Note! Must do this after TestBoxStatuses maintainance from
-point 2, or abandond tests won't be cleaned up after a testbox is disabled.)</p>
+point 2, or abandoned tests won't be cleaned up after a testbox is disabled.)</p>
 </li>
 <li><p class="first">Consider testcases in the scheduling queue, pick the first one which the
@@ -1099 +1099 @@
 <p>TODO</p>
 </div>
-<div class="section" id="cleaning-up-abandond-testcase">
-<h2>#9 - Cleaning Up Abandond Testcase</h2>
+<div class="section" id="cleaning-up-abandoned-testcase">
+<h2>#9 - Cleaning Up Abandoned Testcase</h2>
 <p>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
@@ -1110 +1110 @@
 <dd><ol class="first last loweralpha simple">
 <li>Add a message to the root TestResults row, creating one if necesary,
-that explains that the test was abandond.  This is done
+that explains that the test was abandoned.  This is done
 by inserting/finding the string into/in TestResultStrTab and adding
 a row to TestResultMsgs with idStrMsg set to that string id and
@@ -1129 +1129 @@
 <h2>#10 - Cleaning Up a Disabled/Dead TestBox</h2>
 <p>The UI needs to be able to clean up the remains of a testbox which for some
-reason is out of action.  Normal cleaning up of abandond testcases requires
+reason is out of action.  Normal cleaning up of abandoned testcases requires
 that the testbox signs on or asks for work, but if the testbox is dead or
 in some way indisposed, it won't be doing any of that.  So, the testbox

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

@@ -635 +635 @@
 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
-   point 2, or abandond tests won't be cleaned up after a testbox is disabled.)
+   point 2, or abandoned tests won't be cleaned up after a testbox is disabled.)
 
 4. Consider testcases in the scheduling queue, pick the first one which the
@@ -784 +784 @@
 
 
-#9 - Cleaning Up Abandond Testcase
-----------------------------------
+#9 - Cleaning Up Abandoned Testcase
+-----------------------------------
 
 This is a subfunction of scenario #1 and #2.  The actions taken are the same in
@@ -796 +796 @@
 1. If the testset is incomplete, we need to completed:
         a) Add a message to the root TestResults row, creating one if necesary,
-           that explains that the test was abandond.  This is done
+           that explains that the test was abandoned.  This is done
            by inserting/finding the string into/in TestResultStrTab and adding
            a row to TestResultMsgs with idStrMsg set to that string id and
@@ -813 +813 @@
 
 The UI needs to be able to clean up the remains of a testbox which for some
-reason is out of action.  Normal cleaning up of abandond testcases requires
+reason is out of action.  Normal cleaning up of abandoned testcases requires
 that the testbox signs on or asks for work, but if the testbox is dead or
 in some way indisposed, it won't be doing any of that.  So, the testbox