You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Verify preset primary field is labeled 'Code' instead of 'Name' on preset definition tab
-- 1. Open Monomer Creation Wizard.
-- 2. Create or edit a preset (e.g., type 'Nucleotide (preset)').
-- 3. Navigate to the tab/section where preset main identifier is entered.
-- 4. Inspect the label of the primary text field at the top of the preset section.
-- Expected result: The primary preset identifier field is labeled 'Code' (not 'Name'); the field position and basic behavior remain as before (no logic change).
Verify preset code is mandatory and triggers 'Mandatory fields must be filled.' when empty on save
-- 1. Open Monomer Creation Wizard and switch to preset creation flow.
-- 2. Leave the 'Code' field completely empty.
-- 3. Fill in all other required fields for saving a preset (e.g., components, any other mandatory properties).
-- 4. Click 'Save' / 'Finish' in the wizard.
-- Expected result: Saving is blocked. An error message appears: 'Mandatory fields must be filled.' The Code field and the preset tab are highlighted in red until a non-empty value is entered.
Verify preset code must be unique amongst other preset codes
-- 1. Create and save a preset with Code value 'PRESET1'.
-- 2. Open the wizard again to create a second preset.
-- 3. Enter Code 'PRESET1' for the new preset.
-- 4. Fill in all other required fields.
-- 5. Attempt to save the second preset.
-- Expected result: Saving the second preset is blocked. Error message appears: 'The preset code must be unique amongst other presets.' The Code field and preset tab are highlighted in red until a different unique code is entered.
Verify allowed characters in preset code (letters, digits, hyphens, underscores, asterisks) are accepted
-- 1. Open the preset creation wizard.
-- 2. In the Code field, enter a value using only allowed characters, e.g. 'AbC-12_', 'abc', 'ABC123', 'CODE-1', 'CODE_2', 'CODE3'.
-- 3. Ensure all other required fields are valid.
-- 4. Attempt to save the preset for several examples of valid codes.
-- Expected result: "Presets with codes containing only uppercase/lowercase letters, numbers, hyphens (-), underscores (_), and asterisks (*) save successfully. No validation error is shown for these codes, and no red highlighting appears.
Verify invalid characters in preset code trigger specific validation error message
-- 1. Open the preset creation wizard.
-- 2. In the Code field, enter a value with at least one invalid character, e.g. 'PRE SET', 'PRESET#1', 'PRESET@1', 'PRESET+1'.
-- 3. Ensure other required fields are valid.
-- 4. Attempt to save the preset.
-- Expected result: Saving is blocked. Error message appears exactly as defined: 'The preset code must consist only of uppercase and lowercase letters, numbers, hyphens (-), underscores (_), and asterisks (*).' The Code field and preset tab are highlighted in red until the invalid characters are removed.
Verify error highlighting on Code field and preset tab is cleared after fixing issues
-- 1. Trigger a validation error for the Code field (e.g. leave it empty or use an invalid character) and attempt to save.
-- 2. Confirm that the Code field and preset tab are highlighted in red.
-- 3. Edit the Code field to a valid, unique value using only allowed characters.
-- 4. Attempt to save again.
-- Expected result: On the first attempt, errors and red highlighting appear. After correcting the Code and saving successfully, the Code field and preset tab no longer have red highlighting. No further validation error for Code is shown.
Verify monomer codes auto-update when preset code changes for auto-generated monomer codes
-- 1. Create a new preset with Code 'ABC'.
-- 2. Allow the wizard to auto-generate monomer codes for components (e.g. Base, Sugar, Phosphate) using the preset code.
-- 3. Confirm the initial monomer codes follow the expected default pattern (e.g. 'ABCB', 'ABCS', 'ABCP' or analogous as defined in previous ticket).
-- 4. Change the preset Code to 'XYZ'.
-- 5. Observe monomer codes for components that were not manually edited.
-- Expected result: For all components whose monomer codes are still in default/auto-generated state, their codes are updated to reflect the new preset Code (e.g. from 'ABCB' to 'XYZB', etc.). The update is applied immediately when the preset Code changes or at the next validation step, as designed.
Verify manually changed monomer code is not auto-updated when preset code changes
-- 1. Create a new preset with Code 'ABC'.
-- 2. Confirm auto-generated monomer codes for all components.
-- 3. Manually change one monomer code (e.g. Base code) to a custom value such as 'BASE_CUSTOM'.
-- 4. Change the preset Code to a new value (e.g. 'XYZ').
-- 5. Inspect all monomer codes in the wizard.
-- Expected result: Monomer codes for components that remain in their default state update to reflect the new preset Code. The manually edited monomer code (e.g. 'BASE_CUSTOM') remains unchanged and is not overwritten by the preset Code change.
Verify multiple sequential changes of preset code keep auto-update logic consistent
-- 1. Create a preset with Code 'AAA' and auto-generated monomer codes.
-- 2. Change Code to 'BBB' and verify non-overridden monomer codes update accordingly.
-- 3. Change Code again to 'CCC'.
-- 4. Inspect monomer codes after each change.
-- Expected result: After each change of the preset Code, all monomer codes that have not been manually changed are updated to use the latest preset Code value. Any monomer codes manually overridden at any step remain unchanged throughout subsequent preset Code changes.
Verify existing presets with valid codes still save successfully after introducing new validation rules
-- 1. Open an existing preset created before this change that has a valid Code according to the new rules.
-- 2. Open it in the wizard without changing the Code.
-- 3. Click 'Save' / 'Finish'.
-- Expected result: Existing presets with already valid codes save successfully without triggering new validation errors. No unexpected errors appear solely due to the introduction of the new preset-Code validation logic.
Verify IDT and AxoLabs aliases for presets follow same uniqueness and validation rules as for monomers
-- 1. Identify or create two presets using IDT/AxoLabs alias fields (if present in the preset wizard).
-- 2. For the first preset, set IDT and/or AxoLabs alias values according to valid monomer rules.
-- 3. Attempt to create a second preset with the same alias values that would violate monomer-level uniqueness.
-- 4. Attempt to save the second preset.
-- Expected result: Behavior of IDT and AxoLabs alias fields for presets matches the existing monomer behavior (same allowed characters and uniqueness rules). If aliases must be unique, saving the second preset is blocked with the same style of error and highlighting used for monomers.
Source task(s):
Defining the preset - presets in the monomer creation wizard #8854
Verify preset primary field is labeled 'Code' instead of 'Name' on preset definition tab
-- 1. Open Monomer Creation Wizard.
-- 2. Create or edit a preset (e.g., type 'Nucleotide (preset)').
-- 3. Navigate to the tab/section where preset main identifier is entered.
-- 4. Inspect the label of the primary text field at the top of the preset section.
-- Expected result: The primary preset identifier field is labeled 'Code' (not 'Name'); the field position and basic behavior remain as before (no logic change).
Verify preset code is mandatory and triggers 'Mandatory fields must be filled.' when empty on save
-- 1. Open Monomer Creation Wizard and switch to preset creation flow.
-- 2. Leave the 'Code' field completely empty.
-- 3. Fill in all other required fields for saving a preset (e.g., components, any other mandatory properties).
-- 4. Click 'Save' / 'Finish' in the wizard.
-- Expected result: Saving is blocked. An error message appears: 'Mandatory fields must be filled.' The Code field and the preset tab are highlighted in red until a non-empty value is entered.
Verify preset code must be unique amongst other preset codes
-- 1. Create and save a preset with Code value 'PRESET1'.
-- 2. Open the wizard again to create a second preset.
-- 3. Enter Code 'PRESET1' for the new preset.
-- 4. Fill in all other required fields.
-- 5. Attempt to save the second preset.
-- Expected result: Saving the second preset is blocked. Error message appears: 'The preset code must be unique amongst other presets.' The Code field and preset tab are highlighted in red until a different unique code is entered.
Verify allowed characters in preset code (letters, digits, hyphens, underscores, asterisks) are accepted
-- 1. Open the preset creation wizard.
-- 2. In the Code field, enter a value using only allowed characters, e.g. 'AbC-12_', 'abc', 'ABC123', 'CODE-1', 'CODE_2', 'CODE3'.
-- 3. Ensure all other required fields are valid.
-- 4. Attempt to save the preset for several examples of valid codes.
-- Expected result: "Presets with codes containing only uppercase/lowercase letters, numbers, hyphens (-), underscores (_), and asterisks (*) save successfully. No validation error is shown for these codes, and no red highlighting appears.
Verify invalid characters in preset code trigger specific validation error message
-- 1. Open the preset creation wizard.
-- 2. In the Code field, enter a value with at least one invalid character, e.g. 'PRE SET', 'PRESET#1', 'PRESET@1', 'PRESET+1'.
-- 3. Ensure other required fields are valid.
-- 4. Attempt to save the preset.
-- Expected result: Saving is blocked. Error message appears exactly as defined: 'The preset code must consist only of uppercase and lowercase letters, numbers, hyphens (
-), underscores (_), and asterisks (*).' The Code field and preset tab are highlighted in red until the invalid characters are removed.Verify error highlighting on Code field and preset tab is cleared after fixing issues
-- 1. Trigger a validation error for the Code field (e.g. leave it empty or use an invalid character) and attempt to save.
-- 2. Confirm that the Code field and preset tab are highlighted in red.
-- 3. Edit the Code field to a valid, unique value using only allowed characters.
-- 4. Attempt to save again.
-- Expected result: On the first attempt, errors and red highlighting appear. After correcting the Code and saving successfully, the Code field and preset tab no longer have red highlighting. No further validation error for Code is shown.
Verify monomer codes auto-update when preset code changes for auto-generated monomer codes
-- 1. Create a new preset with Code 'ABC'.
-- 2. Allow the wizard to auto-generate monomer codes for components (e.g. Base, Sugar, Phosphate) using the preset code.
-- 3. Confirm the initial monomer codes follow the expected default pattern (e.g. 'ABCB', 'ABCS', 'ABCP' or analogous as defined in previous ticket).
-- 4. Change the preset Code to 'XYZ'.
-- 5. Observe monomer codes for components that were not manually edited.
-- Expected result: For all components whose monomer codes are still in default/auto-generated state, their codes are updated to reflect the new preset Code (e.g. from 'ABCB' to 'XYZB', etc.). The update is applied immediately when the preset Code changes or at the next validation step, as designed.
Verify manually changed monomer code is not auto-updated when preset code changes
-- 1. Create a new preset with Code 'ABC'.
-- 2. Confirm auto-generated monomer codes for all components.
-- 3. Manually change one monomer code (e.g. Base code) to a custom value such as 'BASE_CUSTOM'.
-- 4. Change the preset Code to a new value (e.g. 'XYZ').
-- 5. Inspect all monomer codes in the wizard.
-- Expected result: Monomer codes for components that remain in their default state update to reflect the new preset Code. The manually edited monomer code (e.g. 'BASE_CUSTOM') remains unchanged and is not overwritten by the preset Code change.
Verify multiple sequential changes of preset code keep auto-update logic consistent
-- 1. Create a preset with Code 'AAA' and auto-generated monomer codes.
-- 2. Change Code to 'BBB' and verify non-overridden monomer codes update accordingly.
-- 3. Change Code again to 'CCC'.
-- 4. Inspect monomer codes after each change.
-- Expected result: After each change of the preset Code, all monomer codes that have not been manually changed are updated to use the latest preset Code value. Any monomer codes manually overridden at any step remain unchanged throughout subsequent preset Code changes.
Verify existing presets with valid codes still save successfully after introducing new validation rules
-- 1. Open an existing preset created before this change that has a valid Code according to the new rules.
-- 2. Open it in the wizard without changing the Code.
-- 3. Click 'Save' / 'Finish'.
-- Expected result: Existing presets with already valid codes save successfully without triggering new validation errors. No unexpected errors appear solely due to the introduction of the new preset-Code validation logic.
Verify IDT and AxoLabs aliases for presets follow same uniqueness and validation rules as for monomers
-- 1. Identify or create two presets using IDT/AxoLabs alias fields (if present in the preset wizard).
-- 2. For the first preset, set IDT and/or AxoLabs alias values according to valid monomer rules.
-- 3. Attempt to create a second preset with the same alias values that would violate monomer-level uniqueness.
-- 4. Attempt to save the second preset.
-- Expected result: Behavior of IDT and AxoLabs alias fields for presets matches the existing monomer behavior (same allowed characters and uniqueness rules). If aliases must be unique, saving the second preset is blocked with the same style of error and highlighting used for monomers.