Functional testing for VNIC
Crossbow introduces VNIC which is a virtual MAC device. VNIC appears to the rest of the system as if they were regular NICs.
The testing for the VNICS includes functional, stress, performance, memory leak testing. Here I just introduce the functional testing.
The functional testing for VNIC will cover six aspects.
1. VNIC administration: VNICs are managed through the dladm(1M) command line interface. Crossbow extended dladm(1M) to create, delete, and show VNICs. A new test suite is developed to cover all options and handle invalid arguments for these subcommands.
2. Resource management: Crossbow introduces three properties (priority, bandwidth and CPU binding) for data-link to manage resource. User can set/reset link properties via subcommand set-linkprop/reset-linkprop in dladm(1M). Tool netperf and mpstat will be used to make sure these properties really work.
3. Virtual switching: Virtual switches are implicitly created when a VNIC is created on top of NIC. They provide the same semantics expected by physical switches. To test this feature, two VNICs will be created on a same NIC/etherstub and make sure unicast/broadcast/multicast packets can be processed correctly.
4. VNIC's behavior: Test is needed to make sure VNIC behaves as a regular NIC which can be plumbed, snooped on, has its own statistics, etc.
5. Zone testing. VNIC can be assigned to any zone. Test need to make sure user can manage VNIC in global zone and there is no regression in non-global zone.
6. xVM and LDOM Guest OS Testing. Crossbow new features need to be tested within a guest OS to ensure that they work properly.
Functional testing covers how well the system executes the functions it is supposed to execute—including user commands, data manipulation, searches and business processes, user screens, and integrations. You can get more resources from www.macrotesting.com like articles , ebooks, applications, etc,..
Posted by vplmega on July 06, 2009 at 04:07 PM CST #