Changes between Version 6 and Version 7 of WindowsTesting


Ignore:
Timestamp:
10/11/16 10:13:43 (8 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WindowsTesting

    v6 v7  
    66* [wiki:OpenVPN24WindowsTests OpenVPN 2.4 Windows tests]
    77
    8 = Windows-specific components =
     8= Usage patterns to test =
    99
    10 == OpenVPN-GUI ==
     10== Usage of OpenVPN-GUI ==
    1111
    12 [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.
     12Right now OpenVPN-GUI testing has not been automated, and all tests are manual:
    1313
    14 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?
     14 * Without Interactive Service, with admin privileges
     15 * With Interactive Service, without admin privileges
     16 * With Interactive Service, with admin privileges
    1517
    16 == Openvpnserv2 ==
     18That 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?
    1719
    18 All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested.
     20== Usage of openvpnserv2 ==
     21
     22All the basic functionality of [https://github.com/OpenVPN/openvpnserv2 openvpnserv2] should be tested. Right now the tests have to be run manually:
    1923
    2024* Ensuring that the service can be enabled / disabled / started / stopped on all platforms
    2125* Restarting a connection that goes down
    22 * Proper behavior with broken configuration files
    23  * What is "proper behavior" needs to be discussed
     26* What happens with broken configuration files? What is the proper behavior?
     27* What happens with conflicting configuration files? What is the proper behavior?
     28
     29== Usage from command-line ==
     30
     31Basic usage from the command-line should be tested. This is covered by cron2's run.bat/run2.bat script. At minimum we should test
     32
     33* Connect and disconnect to a VPN as admin (should work)
     34* Connect to a VPN as unprivileged user (should fail cleanly)
    2435
    2536= Windows-specific command-line tools =
    … …  
    2738== netsh ==
    2839
    29 Ensure that the netsh calls that OpenVPN makes have the desired effect.
     40Ensure that the netsh calls that OpenVPN makes have the desired effect. There are no automated tests for this yet.
    3041
    3142= Windows-specific options =
    … …  
    4960* What are the commands and sequences we should test?
    5061
     62Right now there are no tests, not even ones that are run manually.
     63
    5164= Basic connectivity testing =
    5265
    … …  
    5770* t_client server side
    5871* what about testing "clients on other systems, server on windows"?
     72
     73= Tests based on usage patterns =
     74
     75* Connecting directly from the command-line as admin
     76* Running --server on Windows
     77* Using more than one tap adapter
     78* Run openvpnserv2
     79 * Single config file
     80 * Several config files
     81  * Behavior if subnets overlap or there are other conflicts