Test Plan¶

General¶

1. The app must work with custom root endpoints
2. The app has a description
3. The app has an icon
4. The app is visible
5. The app works on all applicable versions of Splunk
6. The print and edit controls are not displayed on the lister and editor
7. The app works with IE, Safari, FireFox, and Chrome

File Lister¶

1. Lookup files appear including both user-based and app-based files and the list is complete (isn't missing files)
2. A warning is shown if the user does not have permission to view the lookup files
3. Both KV store and CSV lookup files are included
4. The list has functional pagination
5. Files can be exported
   1. Files that are in a user context need to be exportable too (including lookups that are in the app directory but are re-assigned to an owner that isn't nobody via meta-data)

File Editor¶

1. Users can create new lookups
   1. The editor warns users if the name or namespace is not provided (when creating a new lookup)
   2. A warning is shown if the lookup file or collection already exists
   3. A warning is shown if no fields are defined for a KV store lookup file
   4. A warning is shown if the KV store field names are not unique
   5. A warning is shown if the KV store fields include a lineage that conflicts with other fields (e.g. cannot have "a" and "a.b")
   6. Importing a lookup file into a new lookup file should fill out the name with the file name if it was not yet completed
   7. Lookup files are saved with the correct name and in the correct app
   8. When a lookup is created, the URL is modified such that it matches a URL that link to editing the lookup
2. Importation functions
   1. Files can be imported by dragging a file onto the editor or on the import dialog (for CSV lookups only)
   2. KV store shouldn't load a file by dragging into the editor (since it isn't supported yet)
   3. User lookups are created in the users directory; these lookups are listed in the list UI for that user

1. Users can edit lookups
   1. The files can be modified in the editor (both KV store and CSV)
   2. The user is provided messaging regarding saving edits (that it is in-progress and/or completed)
   3. KV store with a hierarchy can be edited
   4. KV store that enforces types can be edited (and a warning is shown if an incorrect types)
      1. Incorrect values for fields when a lookup has defined types can be edited
   5. A warning is shown if the user does not have permission to view the lookup files
   6. A warning is shown if the lookup file does not exist
   7. A warning is shown if the lookup file is too large to modify
   8. Users cannot the header
   9. Lookup files that are owned by a user but are actually in the apps directory are saved in the correct location
   10. Pressing "cancel" sends the user back to the list page
   11. The lookup backup list is refreshed when saving (CSV only)
   12. The editor recognizes the field types (if available) for KV lookups and shows that the value is incorrect (e.g. entering "foo" in a field that expects an number is shown as invalid)
   13. Header is fixed so that it always appears at the top of the editor
   14. If a lookup has no rows, then the editor will display at least one empty row

1. Users can view and load backups of files (CSV only)
   1. Backups are automatically made when a lookup is saved
   2. Loading a backup causes it to be loaded into the editor
   3. A message is shown when a lookup is loaded
   4. Backups for user lookups work

1. XSS prevention
   1. An imported a CSV with scripting doesn't get executed
   2. A CSV or KV store lookup with scripting doesn't get executed