Summarized Test Results
-----------------------

ncp: all tests pass

location: all tests pass

nwamadm: all tests pass

auth: all tests fail oweing to the fact that authorizations have changed

enm

- tests 1, 2, 3, 8 - nwam_test_user (that the tests run as) should have 
updated authorizations and profiles to run svcadm(1M) commands for ENMs 
with FMRIs.

nwamcfg interactive

- test 12 - walkprop and list have different help usage message
- test 14 - output lists ncu in lowercase now, not NCU (also other objects)
- test 29 - list/walkprop usage message has changed
- tests 39, 40 - can create NCPs other than "User", fix test expectation
- test 54 - loc is lowercase, not LOC
- test 70 - list/walkprop usage message has changed
- test 71 - enm is lowercase, not ENM

nwamcfg non-interactive

- tests 3, 11, 13, 34, 35, 49, 51, 63 - ncu is lowercase, not NCU
- test 36 - can create NCPs other than "User", fix test expectation

event

- test 41 - does a "nwamadm disable" of a location that was 
conditionally enabled.  not allowed.  can do a "nwamadm disable" of a 
conditional location only it is was manually (nwamadm) enabled.

- tests 51, 53, 55, 57 => when no NCU is active, NoNet is activated.  
The test expects a "ncu foo is-not active" object to be enabled.

- test 58 - must be a "select ncp user" before doing the "nwamcfg 
destroy ncu ..."

- test 59 - the ip-address in condition string is missing, configuration 
cannot be read

- test 63 - ipv6-addr has "/", configuration cannot be read

- tests 46, 47, 65, 66, 67, 68 - these fail at random.  The test should 
wait for network/location or ipfilter:default service to come out of the 
offline*/online* state before checking.


Missing Tests
-------------

New tests need to be added for the recently pushed RFEs.

=> output of list (in both nwamadm and nwamcfg) is sorted alphabetically
=> conditions can be based on NCP also "ncp <foo> is/is-not active"
=> object names are *not* case-sensitive
=> list and walkprop have a "-a" option that lists and walks all 
properties (the usage message also has changed)
=> new authorizations added and scope of existing ones changed
=> Network Autoconf split into two different profiles
=> Multiple NCPs are supported

Reply via email to