Right now this is just for obscure timeline bugs around selectionRange
Over time we should break out the timeline test into this and other tests like this.
comment test for SPL-8841 - namely some bad behaviour in selectionRanges versus timelineRange management
setTimeout 120000
openAndWait / (open the main interface)
comment Wait for page to load up
waitForDispatchCompleted 120000
comment save a search with ALL_TIME
select timelineValues value=ALL_TIME
type entry index::_internal gregergegerre
click entrySubmit (Click submit button)
comment Wait for query to load
waitForDispatchCompleted 120000
click menuBug
waitForElementPresent splunksMenu 5000
click saveThisSplunk
waitForElementPresent adminPopupLayer 5000
pause 250
type //div[@id='adminPopupLayer']//input[@name='name'] selectionRangeTester
click //div[@id='adminPopupLayer']//input[@type='submit' and @value='Save']
comment We dont care if it errors out for existing already.
pause 2000
waitForDispatchCompleted 30000
comment Now we run a search with a custom relative timerange.
type entry index::_internal startmonthsago::9
click entrySubmit (Click submit button)
comment Wait for query to load
waitForDispatchCompleted 120000
comment With interface in this state, we click the all_time saved search
click menuBug
waitForElementPresent splunksMenu 5000
click savedSplunksMenu
click //label[.='selectionRangeTester']
comment We made the search match 0 events, so dont have to wait very long here.
waitForDispatchCompleted 10000
verifyTextNotPresent Unable to get a properly formatted response from the server