Package com.atlassian.jira.webtests.ztests.navigator.jql
package com.atlassian.jira.webtests.ztests.navigator.jql
-
ClassesClassDescriptionTests written to prove fix for JRASERVER-69435Test switching from the advanced JQL view to the basic editing viewTests the "text" clause in JQL, which searches across all system text fields and custom free text fields that the user can see.Tests specific clauses ability to be used when their system properties have been disabled.Some more tests for column context.Testing for "fitness" in the filter form of singular custom field clauses.Tests the interpretations of different literals (operands) for each custom field clause.Tests the validity of all the operators against all the custom field clauses.Verify the behaviour of custom fields in JQL queries when they have been disabled.Test date fields such as Created.Tests using the EMPTY and NOT EMPTY literals.Test saved filter behaviour with JQL.This is test to verify the function of security levels used together with custom fields group selectors such as "single select" or "multi select".A test that verifies that a SearchRequestView (e.g.Test of the Search Request View for Comments and using JQL.Tests the JQL parser and how it handles reserved words.Test for JQL included JQL system functions.Queries mentioned in our documentation on http://confluence.atlassian.com/display/JIRA/Advanced+SearchingA collection of random, crazy JQL queries that don't fit in anywhere else.Test realated to relative Date formats.Tests if JQL searches do not bring back data when fields have been hidden or custom fields have been moved out of configuration.Testing for "fitness" in the filter form of multiple system field clauses.Testing for "fitness" in the filter form of singular system field clauses.Tests the interpretations of different literals (operands) for each system field clause.Tests the validity of all the operators against all the system field clauses.This test class test for User queries being case insensitive.JQL Func Test to ensure the IssueNavigator's behaviour when currently in Simple Mode and calling the IssueNavigator via URL and the value for a field is invalid and requires to display a validation error message.