Project

General

Profile

Test Plan » History » Version 8

Luke Murphey, 10/28/2015 05:38 PM

1 1 Luke Murphey
h1. Test Plan
2 1 Luke Murphey
3 7 Luke Murphey
h2. General
4 7 Luke Murphey
5 7 Luke Murphey
# The app must work with custom root endpoints
6 7 Luke Murphey
# The app has a description
7 7 Luke Murphey
# The app has an icon
8 7 Luke Murphey
# The app is visible
9 7 Luke Murphey
# The app works on all applicable versions of Splunk
10 7 Luke Murphey
# The print and edit controls are not displayed on the lister and editor
11 8 Luke Murphey
# The app works with IE, Safari, FireFox, and Chrome
12 7 Luke Murphey
13 7 Luke Murphey
h2. File Lister
14 7 Luke Murphey
15 7 Luke Murphey
# Lookup files appear including both user-based and app-based files and the list is complete (isn't missing files)
16 7 Luke Murphey
# A warning is shown if the user does not have permission to view the lookup files
17 7 Luke Murphey
# Both KV store and CSV lookup files are included
18 7 Luke Murphey
# The list has functional pagination
19 7 Luke Murphey
# Files can be exported
20 7 Luke Murphey
## 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)
21 7 Luke Murphey
22 7 Luke Murphey
23 7 Luke Murphey
h2. File Editor
24 8 Luke Murphey
25 7 Luke Murphey
# Users can create new lookups
26 7 Luke Murphey
## The editor warns users if the name or namespace is not provided (when creating a new lookup)
27 7 Luke Murphey
## A warning is shown if the lookup file already exists when creating a new one
28 7 Luke Murphey
## A warning is shown if no fields are defined for a KV store lookup file
29 7 Luke Murphey
## Importing a lookup file into a new lookup file should fill out the name with the file name if it was not yet completed
30 7 Luke Murphey
## Lookup files are saved with the correct name and in the correct app
31 7 Luke Murphey
## When a lookup is created, the URL is modified such that it matches a URL that link to editing the lookup
32 7 Luke Murphey
# Importation functions
33 7 Luke Murphey
## Files can be imported by dragging a file onto the editor or on the import dialog (for CSV lookups only)
34 7 Luke Murphey
## KV store shouldn't load a file by dragging into the editor (since it isn't supported yet)
35 7 Luke Murphey
36 7 Luke Murphey
# Users can edit lookups
37 7 Luke Murphey
## The files can be modified in the editor (both KV store and CSV)
38 7 Luke Murphey
## The user is provided messaging regarding saving edits (that it is in-progress and/or completed)
39 7 Luke Murphey
## KV store with a hierarchy can be edited
40 7 Luke Murphey
## KV store that enforces types can be edited (and a warning is shown if an incorrect types)
41 7 Luke Murphey
### Incorrect values for fields when a lookup has defined types can be edited
42 7 Luke Murphey
## A warning is shown if the user does not have permission to view the lookup files
43 7 Luke Murphey
## A warning is shown if the lookup file does not exist
44 7 Luke Murphey
## A warning is shown if the lookup file is too large to modify
45 7 Luke Murphey
## Users cannot the header
46 7 Luke Murphey
## Lookup files that are owned by a user but are actually in the apps directory are saved in the correct location
47 7 Luke Murphey
## Pressing "cancel" sends the user back to the list page
48 7 Luke Murphey
##  The lookup backup list is refreshed when saving (CSV only)
49 7 Luke Murphey
## 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)
50 7 Luke Murphey
## Header is fixed so that it always appears at the top of the editor
51 7 Luke Murphey
52 7 Luke Murphey
# Users can view and load backups of files (CSV only)
53 7 Luke Murphey
## Backups are automatically made when a lookup is saved
54 7 Luke Murphey
## Loading a backup causes it to be loaded into the editor
55 7 Luke Murphey
## A message is shown when a lookup is loaded