Changes between Version 10 and Version 11 of WindowsTesting

Timestamp:

10/17/16 07:00:10 (8 years ago)

Author:

Samuli Seppänen

Comment:

--

WindowsTesting

@@ -8 +8 @@
 = Current test scripts =
 
-* [https://github.com/mattock/openvpn-windows-buildtest openvpn-windows-buildtest] bash scripts
+* [https://github.com/mattock/openvpn-windows-buildtest openvpn-windows-buildtest bash scripts]
  * Builds an installer on every commit to "release/2.3" and "master" branches
+ * Uses [https://github.com/OpenVPN/openvpn-build openvpn-build]
  * Publishes the resulting installers
- * Email select developers on build failure
-* [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell scripts
- * Automated, manually-triggered testing of OpenVPN-GUI, openvpnserv2 and "OpenVPN in cmd.exe"
+ * Emails selected developers on build failure
+* [https://github.com/mattock/openvpn-windows-test openvpn-windows-test Powershell scripts]
+ * Automated, manually-triggered testing of OpenVPN-GUI, openvpnserv2 and "OpenVPN inside cmd.exe"
  * Tests are done with arbitrary OpenVPN servers (whatever in the configuration directory)
 * ''run.bat/run2.bat'' from cron2 (unpublished atm)
@@ -22 +23 @@
 == GUI-based usage (OpenVPN-GUI) ==
 
-All the basic functionality of [https://github.com/OpenVPN/openvpn-gui OpenVPN GUI] should be tested. Connectivity tests have been automated with the [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell script.
+All the basic functionality of [https://github.com/OpenVPN/openvpn-gui OpenVPN GUI] should be tested. Connectivity tests have been automated with the [https://github.com/mattock/openvpn-windows-test openvpn-windows-test].
 
 [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?
@@ -28 +29 @@
 == OpenVPN as a service (openvpnserv2) ==
 
-All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested. Connectivity tests have been automated with the [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell script.
+All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested. Connectivity tests have been automated with the [https://github.com/mattock/openvpn-windows-test openvpn-windows-test].
 
 More advanced tests yet to be automated:
@@ -42 +43 @@
 
 * cron2's run.bat/run2.bat script 
-* [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell script
+* [https://github.com/mattock/openvpn-windows-test openvpn-windows-test]
 
 Other things that should be tested:
@@ -69 +70 @@
 = Management interface =
 
-Ensure that management interface commands work as expected, with particular focus on the commands and sequences that a GUI typically uses. These tests should automated immediately. Questions:
+Ensure that management interface commands work as expected, with particular focus on the commands and sequences that a GUI typically uses. These tests should not be run manually, but rather automated directly. Questions:
 
 * How do we automate the tests?
 * What are the commands and sequences we should test?
 
-Right now there are no tests, not even ones that are run manually.
-
 = Basic connectivity testing =
 
-Extend t_client.sh tests to Windows also.  Right now: barebones run.bat+run2.bat and [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell script.
+Extend t_client.sh tests to Windows also.  Right now: barebones run.bat+run2.bat (see above) and [https://github.com/mattock/openvpn-windows-test openvpn-windows-test].
 
 = Infrastructure needed for the tests =