UI Boundary testing

[sthirugn]

Note: The responsibility of this task if for both @sghai and @kbidarkar. But here I can assign only one person. Please create child tasks and link to this main task as needed.

Auto UI (Owner: Sachin/Kedar) (* - indicates some sort of data population required before any sort of editing is available)

Assure proper positive and negative testing of each field

1. Non-exhaustive examples of Positive:
   1. Proper/expected field data CRUD
   2. UTF-8 data entered in text field.
2. Non-exhaustive examples of Negative
   1. ascii text in a numeric field and vice versa
   2. real values in an integer field?
   3. Very large numbers entered in an integer field
   4. Negative numbers entered in an integer field
   5. etc., etc., etc...

TASK- Boundary testing for Settings submenus (not provisioning-specific per say, could possibly be broken out into its own section.

• [P1] General
• [P1] Auth
• [P1] Provisioning
• [P2] Bootdisk
• [P2] Discovered
• [P2] Puppet
• [P3] Foreman tasks (possibly nothing to do here)

TASK - Boundary testing for Hosts submenus

• [P1] Operating System > (details)
• [P2] Provisioning Templates*
• [P2] Installation Media*
• [P2/3] Hardware Models
• [P2/3] Architectures
• [P3] Partition tables

[P2] [TASK] Boundary testing for Configure submenus

• Environments*
• Puppet Classes*
• Config Groups*
• Smart Variables*

[TASK] Boundary testing for Infrastructure submenus

• [P1] Compute Resources
• [P1] Subnets
• [P1] Domains
• [P2] Capsules*
• [P3] Compute Profiles
• [P3] Realms

[sghai]

A good number of boundary tests are covered in UI automation and working fine. The only pending thing is validation of few parameters under settings sub-menu and for this a separate task is already opened #1250.

Closing this task..