Class TestCustomFields
java.lang.Object
com.atlassian.jira.functest.framework.BaseJiraFuncTest
com.atlassian.jira.webtests.ztests.customfield.TestCustomFields
-
Field Summary
Fields inherited from class com.atlassian.jira.functest.framework.BaseJiraFuncTest
assertions, backdoor, environmentData, initClass, navigation, tester, testRule
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoid
void
void
void
void
void
void
void
void
void
void
void
void
setUp()
void
tearDown()
void
void
void
void
void
This test makes sure that there is no accidental data loss after a configuration of a custom field has been updated in such way that existing CF values no longer exist in the context - see JRASERVER-62455 for details.void
void
void
void
void
Editing issue types caused a custom field context configuration to lose its association with the issue type because the (mutable) GenericValue was used as a key in the configs map (cache).void
void
void
void
void
void
void
void
void
void
void
void
Methods inherited from class com.atlassian.jira.functest.framework.BaseJiraFuncTest
getAssertions, getBackdoor, getEnvironmentData, getTester
-
Constructor Details
-
TestCustomFields
public TestCustomFields()
-
-
Method Details
-
setUp
public void setUp() -
tearDown
public void tearDown() -
testReturnUrl
public void testReturnUrl() -
testCustomFields
public void testCustomFields() -
testAllCustomFields
public void testAllCustomFields() -
testNumberCustomField
public void testNumberCustomField() -
testUserCustomFieldWithInvalidDefaultValue
public void testUserCustomFieldWithInvalidDefaultValue() -
testFreeTextCustomFieldWithTooLongDefaultValue
public void testFreeTextCustomFieldWithTooLongDefaultValue() -
testMultiUserCustomFieldWithInvalidDefaultValue
public void testMultiUserCustomFieldWithInvalidDefaultValue() -
testAddingACustomFieldAndEditingTheConfiguration
public void testAddingACustomFieldAndEditingTheConfiguration() -
testCustomFieldsOrderingMultiCheckboxes
public void testCustomFieldsOrderingMultiCheckboxes() -
testCustomFieldsOrderingCascadingSelect
public void testCustomFieldsOrderingCascadingSelect() -
customFieldsAddField
public void customFieldsAddField() -
customFieldsDeleteField
public void customFieldsDeleteField() -
customFieldsAddCustomFieldOption
public void customFieldsAddCustomFieldOption() -
customFieldsDelCustomFieldOption
public void customFieldsDelCustomFieldOption() -
customFieldCreateIssueWithCustomFields
public void customFieldCreateIssueWithCustomFields() -
customFieldCreateIssueWithFieldScope
public void customFieldCreateIssueWithFieldScope() -
customFieldsEditIssueWithCustomFields
public void customFieldsEditIssueWithCustomFields() -
customFieldEditIssueWithFieldScope
public void customFieldEditIssueWithFieldScope() -
customFieldsMoveIssueWithCustomFieldsforProject
public void customFieldsMoveIssueWithCustomFieldsforProject() -
customFieldsMoveIssueWithCustomFieldsforIssueType
public void customFieldsMoveIssueWithCustomFieldsforIssueType() -
customFieldCreateSubTaskWithCustomFields
public void customFieldCreateSubTaskWithCustomFields() -
customFieldWithFieldScreenSchemes
public void customFieldWithFieldScreenSchemes() -
testVersionCustomFieldPromptsForValuesInMove
public void testVersionCustomFieldPromptsForValuesInMove() -
testVersionCustomFieldPromptsForValuesInBulkMove
public void testVersionCustomFieldPromptsForValuesInBulkMove() -
testViewIssueMultiUserCFIssueLevelSecurity
public void testViewIssueMultiUserCFIssueLevelSecurity() -
testViewIssueMultiUserCFPermissionScheme
public void testViewIssueMultiUserCFPermissionScheme() -
testEditIssueTypeDoesNotCauseCustomFieldToDisappear
public void testEditIssueTypeDoesNotCauseCustomFieldToDisappear()Editing issue types caused a custom field context configuration to lose its association with the issue type because the (mutable) GenericValue was used as a key in the configs map (cache). Subsequent calls to see if the exact same issue type key returned a field config failed because the key was then in the wrong hash bucket. This resulted in the custom field not being shown on the view issue screen. Test test checks to see if this problem occurs. NOTE that this test can produce false negatives (incorrect test passes) due to the necessity of causing the jdk implementation to use a different bucket for the new issue type. Of course this doesn't happen in the fixed implementation of the production code so there should be no false positives (incorrect failures) -
testEditSelectWithMultipleValuesFixesField
public void testEditSelectWithMultipleValuesFixesField() -
testEditUserCFWithDeletedUsersValuesSelected
public void testEditUserCFWithDeletedUsersValuesSelected() -
testDateTimeCustomFieldShouldRespectUserTimeZone
- Throws:
Exception
-
testDateCustomFieldShouldBeDisplayedInSystemTimeZone
- Throws:
Exception
-
testCustomFieldsMissingFromContext
public void testCustomFieldsMissingFromContext()This test makes sure that there is no accidental data loss after a configuration of a custom field has been updated in such way that existing CF values no longer exist in the context - see JRASERVER-62455 for details. -
testCascadingSelectWithoutChildOption
public void testCascadingSelectWithoutChildOption() -
testMultipleConfigurationItemsWithoutDefaultValueItem
public void testMultipleConfigurationItemsWithoutDefaultValueItem()
-