Splunk Apps » Lookup Editor

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
# The print and edit controls are not displayed on the lister and editor
# The app works with IE, Safari, FireFox, and Chrome

h2. File Lister

# Lookup files appear including both user-based and app-based files and the list is complete (isn't missing files)
# A warning is shown if the user does not have permission to view the lookup files
# Both KV store and CSV lookup files are included
# The list has functional pagination
# Files can be exported
## 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)

h2. File Editor

# Users can create new lookups
## The editor warns users if the name or namespace is not provided (when creating a new lookup)
## A warning is shown if the lookup file or collection already exists
## A warning is shown if no fields are defined for a KV store lookup file
## A warning is shown if the KV store field names are not unique
## 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")
## Importing a lookup file into a new lookup file should fill out the name with the file name if it was not yet completed
## Lookup files are saved with the correct name and in the correct app
## When a lookup is created, the URL is modified such that it matches a URL that link to editing the lookup
# Importation functions
## Files can be imported by dragging a file onto the editor or on the import dialog (for CSV lookups only)
## KV store shouldn't load a file by dragging into the editor (since it isn't supported yet)
## User lookups are created in the users directory; these lookups are listed in the list UI for that user

# Users can edit lookups
## The files can be modified in the editor (both KV store and CSV)
## The user is provided messaging regarding saving edits (that it is in-progress and/or completed)
## KV store with a hierarchy can be edited
## KV store that enforces types can be edited (and a warning is shown if an incorrect types)
### Incorrect values for fields when a lookup has defined types can be edited
## A warning is shown if the user does not have permission to view the lookup files
## A warning is shown if the lookup file does not exist
## A warning is shown if the lookup file is too large to modify
## Users cannot the header
## Lookup files that are owned by a user but are actually in the apps directory are saved in the correct location
## Pressing "cancel" sends the user back to the list page
## The lookup backup list is refreshed when saving (CSV only)
## 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)
## Header is fixed so that it always appears at the top of the editor
## If a lookup has no rows, then the editor will display at least one empty row

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

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