Changes between Version 8 and Version 9 of WindowsTesting

Timestamp:

10/17/16 06:55:23 (8 years ago)

Author:

Samuli Seppänen

Comment:

--

WindowsTesting

@@ -6 +6 @@
 * [wiki:OpenVPN24WindowsTests OpenVPN 2.4 Windows tests]
 
+= Current test 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
+ * 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"
+ * Tests are done with arbitrary OpenVPN servers (whatever in the configuration directory)
+* run.bat/run2.bat from cron2 (unpublished atm)
+ * Runs openvpn inside cmd.exe against the t_client.sh test servers
+
 = Usage patterns to test =
 
 == GUI-based usage (OpenVPN-GUI) ==
 
-Right now OpenVPN-GUI testing has not been automated, and all tests are manual:
+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.
 
- * Without Interactive Service, with admin privileges
- * With Interactive Service, without admin privileges
- * With Interactive Service, with admin privileges
-
-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?
+[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?
 
 == 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:
+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.
+
+More advanced tests yet to be automated:
 
 * Ensuring that the service can be enabled / disabled / started / stopped on all platforms
@@ -29 +39 @@
 == Direct use from the command-line ==
 
-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:
+Basic usage from the command-line (cmd.exe) should be tested. This is covered by
 
-* Connect and disconnect to a VPN as admin (should work)
-* Connect to a VPN as unprivileged user (should fail cleanly)
+* cron2's run.bat/run2.bat script 
+* [https://github.com/mattock/openvpn-windows-test openvpn-windows-test] Powershell script
+
+Other things that should be tested:
+
+* Connecting to a VPN as unprivileged user should fail cleanly
 
 = Windows-specific command-line tools =
@@ -64 +78 @@
 = Basic connectivity testing =
 
-Extend t_client.sh tests to Windows also.  Right now: barebones run.bat+run2.bat
+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.
 
 = Infrastructure needed for the tests =