Changes between Version 7 and Version 8 of WindowsTesting

Timestamp:

10/11/16 10:15:41 (8 years ago)

Author:

Samuli Seppänen

Comment:

--

WindowsTesting

@@ -8 +8 @@
 = Usage patterns to test =
 
-== Usage of OpenVPN-GUI ==
+== GUI-based usage (OpenVPN-GUI) ==
 
 Right now OpenVPN-GUI testing has not been automated, and all tests are manual:
@@ -18 +18 @@
 That said, [https://github.com/OpenVPN/openvpn-gui OpenVPN-GUI] communicates with OpenVPN using the management interface, as do all the more recent GUIs. Thus management interface tests (below) will eventually help verify correct operation of OpenVPN-GUI. All the basic functions of OpenVPN-GUI should be tested, but how would these tests be automated? Would it require an automation API in OpenVPN-GUI itself?
 
-== Usage of openvpnserv2 ==
+== OpenVPN as a service (openvpnserv2) ==
 
 All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested. Right now the tests have to be run manually:
@@ -27 +27 @@
 * What happens with conflicting configuration files? What is the proper behavior?
 
-== Usage from command-line ==
+== Direct use from the command-line ==
 
-Basic usage from the command-line should be tested. This is covered by cron2's run.bat/run2.bat script. At minimum we should test
+Basic usage from the command-line (cmd.exe) should be tested. This is covered by cron2's run.bat/run2.bat script. At minimum we should test these:
 
 * Connect and disconnect to a VPN as admin (should work)
@@ -70 +70 @@
 * t_client server side
 * what about testing "clients on other systems, server on windows"?
-
-= Tests based on usage patterns =
-
-* Connecting directly from the command-line as admin
-* Running --server on Windows
-* Using more than one tap adapter
-* Run openvpnserv2
- * Single config file
- * Several config files
-  * Behavior if subnets overlap or there are other conflicts