Changes between Version 1 and Version 2 of Simple Driver HOWTO

Show
Ignore:
Timestamp:
03/06/10 14:15:58 (9 years ago)
Author:
ibaldin (IP: 98.26.55.18)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Simple Driver HOWTO

    v1 v2  
    4242Once you have coded all the tasks, it is time to test them. Testing drivers is a multi-layered process that includes: 
    4343 1. Running unit-tests built into the code. This is '''strongly''' recommended. Please familiarize yourself with JUnit framework. Look at driver tests in other drivers for ideas.  
    44  2. Running simple ant-based tests. Create drivers/network/<Device Driver name>/test.xml ant script to invoke individual tasks. Look at similar scripts in other drivers for ideas. 
     44 2. Running simple ant-based tests. Create drivers/network/<Device Driver name>/test.xml ant script to invoke individual tasks. Look at similar scripts in other drivers for ideas. They can be invoked as simply as 
     45{{{ 
     46$ ant -f test.xml -Dproperty1=property1Value -Dproperty2=property2Value targetName 
     47}}} 
    4548 3. Creating and invoking a handler script to invoke the tasks and pass appropriate parameters to them. This begins the process of integration of the driver with policies and is described in the next section 
    4649