Hi, William,

Yes, what you mentioned works well for us right now.

We are doing following steps for AI client manifest automated test suite:

1. manually boot a client with AI
2. allowing the auto install service to either success or fail
3. login with root
4. Install tet/cti package, test suites
5. run test scripts to execute auto-install -p with various manifest and 
disk configurations


William Schumann ??:
> Jan,
>
> jan damborsky wrote:
>>> I wrote: I added functionality to disktest originally for testing 
>>> the Orchestrator enhancements to maintain slices and partitions, but 
>>> found it unnecessary when AI manifest processing was implemented.  
>>> The test driver code reads a text file and performs operations 
>>> according to commands and parameters.  I have not tried to use it 
>>> since initial development.  For now, I am not going to unit test it, 
>>> since I am not certain that it will be used.
>>
>> I think that QE team is interested in this test driver for testing
>> the orchestrator. If you think this is not the appropriate tool
>> to take advantage of, should we probably offer another way, how
>> those changes might be tested ?
> I've been testing these changes by using an auto-install environment:
> -to get a DHCP address and boot the microroot
> -allowing the autoinstaller to download and mount solaris.zlib and 
> solarismisc.zlib
> -allowing the auto install service to fail
> -logging in as root
> -running auto-install manually specifying manifests with the -p option
>
> Running auto-install manually works for me, but I need to to type a 
> console interrupt after the TI phase if no problems occur.
>
> This would also work for QE, but they are going to want automated 
> techniques.  I think that a small change to the AI-engine to break 
> either before or after TI (chosen by auto-install command line 
> options), so that a script could automatically check status of the 
> test against a particular manifest and disk configuration.
>>
>>>>
>>>> Also, could you please add this test driver to the recently
>>>> introduced SUNWinstall-test package ? It is intended to
>>>> bundle Caiman installer test drivers for purposes of QE team
>>>> and currently contains TD & TI test drivers. Thanks.
>>>>
> OK, but this is out of the scope of this enhancement.  I will file a 
> new bug that addresses the topic of testing AI that will minimally 
> package the test driver and may include the changes I mention above to 
> auto-install for command line automated testing.  As you said in our 
> office discussion, input from the community might improve the 
> resulting test software.
> William
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

-- 
Great Thanks & Best Regards

---
Jeffrey Huang                  SWAN: x51683, Ext: 0086-10-62673683
Solaris QE Group                      Email: jeffrey.huang at sun.com
           China Engineering & Research Institute, Sun Microsystems
         7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090213/a419bd63/attachment.html>

Reply via email to