Test Plan » History » Version 8
Version 7 (Luke Murphey, 10/22/2016 05:22 PM) → Version 8/12 (Luke Murphey, 10/22/2016 06:03 PM)
h1. Test Plan
h2. 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+) (6.2+)
** The app uses web.conf to make inputs public which requires 6.2
** Status history uses a single value with a timechart 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
h2. 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
h2. 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
h2. 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+) (6.2+)
** The app uses web.conf to make inputs public which requires 6.2
** Status history uses a single value with a timechart 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
h2. 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
h2. 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