User:Log Linden/Socks5Viewer/TestPlan

Scope

• This test is to verify that newly added proxy support in the viewer works as expected.
• The user story that prompted the changes is STORM-1112 .
• This test will only be meaningful if performed in a network environment that does not have access to second life.
• The test also requires a working web proxy host and SOCKS 5 proxy host.
• Estimated running time: 2 hours/platform after securing the appropriate test environment

Set-up

Environment

• Viewer: This test requires a build of the viewer that contains the Proxy code. Grab the latest for your platform from the link below:

STORM-1112 Implement SOCKS 5 proxy

Allow the Second Life Viewer to connect through a SOCKS 5 proxy.

Windows | Macintosh | Linux

---

Source: https://bitbucket.org/log_linden/viewer_socks5
Details for these builds (build logs, included changesets)

• Server: The test requires testing of mesh upload and download functionality, so access to a region with mesh support is required. Agni or Aditi are each fine. Region crossing will also be tested, so adjacent regions to test in will also be required.
• A restrictive, firewalled network to connect the testing machine to is required to obtain valid test results.
• A working web proxy host and a working SOCKS 5 host are required to complete the test.
• Instructions to set up a reference Ubuntu Linux server that will act as a firewall and proxy gateway are available.
• While 3rd party testers are welcome to set up a duplicate of our reference gateway server, we are also interested in results you might get in your organization's specific network setup, rather than using our reference setup. Since you might not be allowed to reconfigure your organization's firewall or proxy host, feel free to only test in the proxy configuration your organization supports and report on results you observe.

Other

• Second Life Account that is able to upload mesh assets on the grid being tested.
• At least one notecard, sound, and animation in your avatar's inventory.
• Sandbox, or other area where building is allowed.

Common Procedures

Refer to this section when asked to do one of the following in a test step.

1. Enable proxy connection with HTTP traffic sent through web proxy.
   1. Change these settings before logging into Second Life.
   2. Open the Proxy settings floater. Me->Preferences->Setup->"Adjust Proxy Settings"
   3. Check "Use HTTP Proxy for Web pages" and enter the address and port number.
   4. Check "Use SOCKS 5 Proxy for UDP traffic" and enter the address and port number.
   5. Under other HTTP traffic proxy, select "Use HTTP Proxy".
   6. Click OK.

1. Enable proxy connection with HTTP traffic sent through SOCKS 5 proxy.
   1. Change these settings before logging into Second Life.
   2. Open the Proxy settings floater. Me->Preferences->Setup->"Adjust Proxy Settings"
   3. Check "Use HTTP Proxy for Web pages" and enter the address and port number.
   4. Check "Use SOCKS 5 Proxy for UDP traffic" and enter the address and port number.
   5. Under other HTTP traffic proxy, select "Use SOCKS 5 Proxy".
   6. Click OK.

1. Disable all proxies
   1. Change these settings before logging into Second Life.
   2. Open the Proxy settings floater. Me->Preferences->Setup->"Adjust Proxy Settings"
   3. Uncheck "Use HTTP Proxy for Web pages".
   4. Uncheck "Use SOCKS 5 Proxy for UDP traffic".
   5. Click OK.

1. Clear Viewer Caches
   1. Click the "Clear Cache" button on the advanced tab of the preferences floater.
   2. Confirm that you want to clear the cache.
   3. Restart the Viewer.

Test Steps

Configuration

1. Test case 1 (you can briefly outline the goal of the test case here)
   1. step 1
   2. step 2
   3. Verify against expected behavior

---

Pass/Fail Criteria

1. Passes if
   1. No unexpected behaviors are observed
2. Fails if
   1. Deviation from expected behavior is observed
   2. A bug is detected that was not accounted for by this test plan
   3. Performance degradation is observed when the proxy is disabled.
3. Known Issues
   1. SLVoice does not support proxies, therefore voice is not expected to work when running the viewer behind a strict firewall.

Tear Down

• Disable all proxies in the viewer configuration.