# misc tests - oddities that have caused problems in the past

# CASE 1: submit a corrupted object class
#
# submit object 
#
#SUCCESS
#
# RESULT 1: No objects will be recognised or processed


# CASE 2: We try to create as-set object AS123:AS-TEST
#         A dummy object was created for this object when AS123 was created
#         which referenced AS123:AS-TEST in the member-of: attribute.
#
# create as-set object 
#
#FAILURE
#
# RESULT 2: The creation will fail because of error 32


# CASE 3: We try to create route-set object AS100:RS-CUSTOMERS
#         A dummy object was created for this object when 1.2.3.0/24 was created
#         which referenced AS100:RS-CUSTOMERS in the member-of: attribute.
#
# create route-set object 
#
#FAILURE
#
# RESULT 3: The creation will fail because of error 32


# CASE 4: We try to create rtr-set object rtrs-test
#         A dummy object was created for this object when kst1-core.swip.net was created
#         which referenced rtr-test in the member-of: attribute.
#
# create rtr-set object 
#
#FAILURE
#
# RESULT 4: The creation will fail because of error 32


# CASE 5: Create an assignment inetnum object six times
#         with less specific allocation with mnt-lower
#         and correct password for mnt-lower of parent
#         and mnt-by of object
#
# create inetnum object 
#
#SUCCESS
#
# RESULT 5: The creation will succeed


# CASE 6: Create two inetnum objects, the first one having an & in the 
#         descr: attribute.
#
# create inetnum objects 
#
#SUCCESS
#
# RESULT 6: The creations will succeed


