1 | | Right now this page is empty. It will get content soon. |
| 1 | |
| 2 | = Introduction = |
| 3 | |
| 4 | This page outlines the tests we do or should run on Windows. |
| 5 | |
| 6 | = Windows-specific components = |
| 7 | |
| 8 | == OpenVPN-GUI == |
| 9 | |
| 10 | [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) help verify correct operation of OpenVPN-GUI. |
| 11 | |
| 12 | 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? |
| 13 | |
| 14 | == Openvpnserv2 == |
| 15 | |
| 16 | All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested. |
| 17 | |
| 18 | * Ensuring that the service can be enabled / disabled / started / stopped on all platforms |
| 19 | * Restarting a connection that goes down |
| 20 | * Proper behavior with broken configuration files |
| 21 | * What is "proper behavior" needs to be discussed |
| 22 | |
| 23 | = Windows-specific command-line tools = |
| 24 | |
| 25 | == netsh == |
| 26 | |
| 27 | Ensure that the netsh calls that OpenVPN makes have the desired effect. |
| 28 | |
| 29 | = Windows-specific options = |
| 30 | |
| 31 | Ensure that various Windows-specific options behave as excepted |
| 32 | |
| 33 | == ip-win32 == |
| 34 | |
| 35 | TODO |
| 36 | |
| 37 | = Management interface = |
| 38 | |
| 39 | Ensure that management interface commands work as expected, with particular focus on the commands and sequences that a GUI typically uses. |
| 40 | |
| 41 | = Basic connectivity testing = |
| 42 | |
| 43 | Extend t_client.sh tests to Windows also. |
| 44 | |
| 45 | = Infrastructure needed for the tests = |
| 46 | |
| 47 | TODO |