儲存庫 vbox 的更動 59549

時間撮記:

2016-2-1 下午03:57:21 (9 年 以前)

作者:

vboxsync

訊息:

Validation Kit: Documentation.

位置:

trunk/src/VBox/ValidationKit

檔案:

• docs/AutomaticTestingRevamp.html (修改) (1 筆差異)
• docs/AutomaticTestingRevamp.txt (修改) (10 筆差異)
• docs/VBoxValidationKitReadMe.html (修改) (1 筆差異)
• docs/VBoxValidationKitReadMe.txt (修改) (1 筆差異)
• testboxscript/win/readme.txt (修改) (1 筆差異)

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

@@ -1347 +1347 @@
 <tr class="field"><th class="field-name">Status:</th><td class="field-body">$Id$</td>
 </tr>
-<tr class="field"><th class="field-name">Copyright:</th><td class="field-body">Copyright (C) 2010-2015 Oracle Corporation.</td>
+<tr class="field"><th class="field-name">Copyright:</th><td class="field-body">Copyright (C) 2010-2016 Oracle Corporation.</td>
 </tr>
 </tbody>

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

@@ -396 +396 @@
 installer).  Queries from unregistered testboxes will be declined as a kind of
 security measure, the incident should be logged in the webserver log if
-possible.   In later dealings with the client the System UUID will be the key 
+possible.   In later dealings with the client the System UUID will be the key
 identifier.  It's permittable for the IP address to change when the testbox
-isn't online, but not while testing (just imagine live migration tests and 
+isn't online, but not while testing (just imagine live migration tests and
 network tests).  Ideally, the testboxes should not change IP address.
 
@@ -579 +579 @@
       redo the sign in.
 
-Note! In scenario #8, the box will not sign on until it has done the reboot and 
+Note! In scenario #8, the box will not sign on until it has done the reboot and
       cleanup reporting!
 
@@ -605 +605 @@
        AND   tsExpire = 'infinity'::timestamp;
 
-   If NOT found return DEAD to the testbox client (it will go back to sign on 
+   If NOT found return DEAD to the testbox client (it will go back to sign on
    mode and retry every 60 seconds or so - see scenario #1).
 
    Note! The WUI will do all necessary clean-ups when deleting a testbox, so
-         contrary to the initial plans, we don't need to do anything more for 
+         contrary to the initial plans, we don't need to do anything more for
          the DEAD status.
 
@@ -858 +858 @@
 
 The implementation of the test manager and adjusting/completing of the testbox
-script and the test drivers are tasks which can be done by more than one 
-person.  Splitting up the TM implementation into smaller tasks should allow 
+script and the test drivers are tasks which can be done by more than one
+person.  Splitting up the TM implementation into smaller tasks should allow
 parallel development of different tasks and get us working code sooner.
 
 
-Milestone #1 
+Milestone #1
 ------------
 
 The goal is to getting the fundamental testmanager engine implemented, debugged
-and working.  With the exception of testboxes, the configuration will be done 
+and working.  With the exception of testboxes, the configuration will be done
 via SQL inserts.
 
@@ -878 +878 @@
       in att/testbox, this shall be moved up into testboxscript/.  The script
       needs to be adjusted according to the specification layed down earlier
-      in this document.  Installers or installation scripts for all relevant 
+      in this document.  Installers or installation scripts for all relevant
       host OSes are required.  Left for part two is result reporting beyond the
-      primary log.  This task must be 100% feature complete, on all host OSes, 
+      primary log.  This task must be 100% feature complete, on all host OSes,
       there is no room for FIXME, XXX or @todo here.
 
@@ -890 +890 @@
     - Implement simple testbox management page.
 
-    - Implement some basic activity and result reports so that we can see 
+    - Implement some basic activity and result reports so that we can see
       what's going on.
 
-    - Create a testmanager / testbox test setup.  This lives in selftest/. 
-      
+    - Create a testmanager / testbox test setup.  This lives in selftest/.
+
       1. Set up something that runs, no fiddly bits. Debug till it works.
       2. Create a setup that tests testgroup dependencies, i.e. real tests
@@ -913 +913 @@
 
     - Implement full result reporting in the testbox script and testbox driver.
-      A testbox script specific reporter needs to be implemented for the 
+      A testbox script specific reporter needs to be implemented for the
       testdriver framework.  The testbox script needs to forward the results to
-      the test manager, or alternatively the testdriver report can talk 
+      the test manager, or alternatively the testdriver report can talk
       directly to the TM.
 
     - Implement the test manager side of the test result reporting.
 
-    - Extend the selftest with some setup that report all kinds of test 
+    - Extend the selftest with some setup that report all kinds of test
       results.
 
-    - Implement script/whatever feeding builds to the test manager from the 
+    - Implement script/whatever feeding builds to the test manager from the
       tinderboxes.
 
     - The toplevel test driver is a VBox thing that must be derived from the
-      base TestDriver class or maybe the VBox one.  It should move from 
+      base TestDriver class or maybe the VBox one.  It should move from
       toptestdriver to testdriver and be renamed to vboxtltd or smth.
 
     - Create a vbox testdriver that boots the t-xppro VM once and that's it.
 
-    - Create a selftest setup which tests booting t-xppro taking builds from 
+    - Create a selftest setup which tests booting t-xppro taking builds from
       the tinderbox.
 
@@ -941 +941 @@
 The goal for this milestone is configuration and converting current testscases,
 the result will be the a minimal test deployment (4-5 new testboxes).
-    
+
 Tasks in somewhat prioritized order:
 
@@ -976 +976 @@
 ------------
 
-After milestone #3 has been reached and issues found by the other team members 
-have been addressed, we will probably go for full deployment.  
+After milestone #3 has been reached and issues found by the other team members
+have been addressed, we will probably go for full deployment.
 
 Beyond this point we will need to improve reporting and analysis.  There may be
-configuration aspects needing reporting as well.  
-
-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 
+configuration aspects needing reporting as well.
+
+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
 implementation.
 
@@ -1059 +1059 @@
 
 :Status: $Id$
-:Copyright: Copyright (C) 2010-2015 Oracle Corporation.
-
+:Copyright: Copyright (C) 2010-2016 Oracle Corporation.
+

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

@@ -436 +436 @@
 <tr class="field"><th class="field-name">Status:</th><td class="field-body">$Id$</td>
 </tr>
-<tr class="field"><th class="field-name">Copyright:</th><td class="field-body">Copyright (C) 2010-2015 Oracle Corporation.</td>
+<tr class="field"><th class="field-name">Copyright:</th><td class="field-body">Copyright (C) 2010-2016 Oracle Corporation.</td>
 </tr>
 </tbody>

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

@@ -111 +111 @@
 
 :Status: $Id$
-:Copyright: Copyright (C) 2010-2015 Oracle Corporation.
+:Copyright: Copyright (C) 2010-2016 Oracle Corporation.
 

trunk/src/VBox/ValidationKit/testboxscript/win/readme.txt

@@ -71 +71 @@
    See also http://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx
 
+7c. Enable verbose driver installation logging (C:\Windows\setupapi.dev.log):
+
+   Create the following value under the key
+   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\
+        LogLevel        [dword] = 0xFF (255)
+
 8. Install firefox or chrome, download the latest testboxscript*.zip from
    the build box.