Node Object Tests
3/25/00 Created
12/21/00 Last modified
Tests specific to this object. Should be done in addition to general field tests.
The type of field is listed in parentheses.
TESTS PER FIELD
- Node Name (DNS name)
- Assign domain name as node name
- Changing alias to name (CNAME to A type)
- Alias (DNS name)
- MX (DNS Name)
- Create mx for non-existent node
- Create mx for existing node
- how do mx privileges work if have or don't have group access to node
- MX Preference (integer)
- Max value?
- Department (single select)
- Group (multiple select box)
- Location (single select)
- Room (string)
- Expiration Date (date)
- Full Search works ok on this?
- Make/Model (single select)
- If create new one, comes back selected
- OS (single select + additional)
- If create new one, comes back selected
- Administrator (people)
- Comes back with good ones checked, multiple ones listed, bad ones in input box
- User (people)
- Comes back with good ones checked, multiple ones listed, bad ones in input box
- Custom Label/Value (string)
- Overlong entry should return error
- The two labels in a given node must be different
- Template Default AS (single select)- Template Node only
- Interface check box (check box)
- Interface name (DNS checkbox)
- Hardware address (hardware)
- Roaming (checkbox)
- Only sticks if hardware address entered
- DHCP (checkbox)
- Only sticks if hardware address entered
- IP address (select and address input)
- IP address name (DNS name)
- Active (checkbox)
- DHCP Options (string)
- What happens if use same option with diff value?
- enter invalid option
- enter invalid value
- max # of options allowed?
- Comments (string)
- IPC Addresses (address)
- IPC Address names (DNS names)
- Count (integer)
Verify People
- Test with existing entries
- Test with empty entries
Verify DNS names
- Test with existing entries
- Test with empty entries
Verify IP Addresses
See IP Address Assignment
Node Type Tests
- If nodetype is template, should not be able to add any other types
- If nodetype is IPC, Adv or Router, should not be able to make it a template type node
- If node changed from Adv or IPC to regular node, are associated names and IP addresses
properly deleted from database?
Other Tests
- Types- can all types be template? If Template IPC, show IPC addr?
- Allow nodes with no interfaces
Modify Test - General
- Change fields one at a time- see if allowed
- Change every fields in one modify operation.
- Change case when possible for things that are supposedly case insensitive (names, hw address)
- Change verifiable fields. Verify. Then change back to original thing
- Should get new box for alias/mx if more than 4 existing
- Can one remove any IP (first, last) or interface (first, last)?
- what is behavior when changing node name to alias? Vice versa?
- Behvior when moving hw address, name or IP address from one interface to another
- behavior when moving alias/mx from one node name to another
- modifying nodes with large #s of mx, alias, interfaces or addresses
- user delete node wants to delete associated mxes. Mail server has multiple groups- do mxes
go away?
- swapping IPC addresses
- remove IP address. select Add Another- can put back in original address?
- remove interface. SElect add another- can put back in original interface?
- change node type of existing node. does that affect adding names, addresses?
- try duplicating fields with multiple values (os, administrator, user, custom fields)
- try using non-unique values for unique fields (names, ip, hw address)
- create node with lots of values in fields (groups, comments, os). Modify works ok?
- Do same for all node types
Modify Test- for regular user
- Can regular user remove own group from record if multiple groups?
- Try all above tests
- Can user modify node that is in multiple groups without errors because IP addresses
are in another group's AS?
- Can user remove group that is not own group?
THE END