Test Plan¶

General¶

• The app must work with custom root endpoints
• The app has a description
• The app has an icon
• The app is visible
• The app works on all applicable versions of Splunk (6.3+)
  • The app uses web.conf to make inputs public which requires 6.2
  • Status history uses a single value with a time-chart which requires 6.3
• The print and edit controls are not displayed on the batch editor
• The app works with IE, Safari, FireFox, and Chrome

Batch editor¶

• The editor will not attempt to create an input with a stanza name that already exists
  • This includes inputs made within the current list of inputs to make (those that didn't exist before the user press the button to make the inputs)
• non-FQDN and IP address based URLs are accepted
  • The protocol will be added automatically if excluded
• non-HTTPS sites are not tested on a Cloud instance but are tested on Enterprise

Input¶

• Memory use is stable (growth is not unbounded)
• Input logs the number of threads when threads are added or removed
• URL declared by an IP address that does not exist is handled correctly on both Windows and *nix (connection exception is handled correctly)
• Thread limit is used correctly
• non-HTTPS sites are not tested on a Cloud instance but are tested on Enterprise

Password handling (both the setup and input editor)¶

• Existing password stored in a conf file is loaded
• Existing password stored in a conf file is cleared upon save and updated to secure storage
• Clearing the password causes the secure password to be removed
  • No error should be thrown if no secure credential entry currently exists
• The existing password entry should be updated if the password is changed or a new credential entry should be created if necessary

Input editor¶

• HTTPS sites are not allowed if on Cloud but allowed on Enterprise