Hi Angela, I don't have any additional comments, looks ok.
Thanks, Sue On 09/14/09 00:47, angela wrote: > Hi Sue, Keith, Eric, and Andre, > > The attachment is the test plan incorporate Andre and I-team comments. > If you haven't any additional issue, this would be the finalized version. > > Thanks for your time reviewing. > Angela > > > ------------------------------------------------------------------------ > > > Text Installer Test Plan > > /There is no ARC ID for this project yet./ > > > Introduction > > > Authors > > Name > > > > Email > > > > Extension / Region > > Angela Li > > > > Angela.Li at Sun.Com <http://nflabs.sfbay.sun.com/NameFinder?-s=SUNID> > > > > x82224 (2) > > *(1)* US/Canada/South America or *(2)* Europe/Middle East/Africa/Asia > > > > Test Sponsor > > The Text Installer will be delivered via the OpenSolaris 1002 release, > not by checking into the Install consolidation. As a result, the C-team > process (including the assignment of a test sponsor) is not being > followed for the OpenSolaris 1002 delivery. A test sponsor will be > requested at such time that the Text Installer is nearing integration > into a consolidation. > > > Test Plan Approvals > > Title > > > > Name > > > > Version > > > > Date > > Development Lead > > > > X.X > > > > YYYY-MM-DD > > Development Manager > > > > X.X > > > > YYYY-MM-DD > > QE management > > > > > > > > > > External Open Source Test Software > > * > > Does this project use any external open source test software? No > > > Revision History > > Date > (yyyy-mm-dd) > > > > Revision > > > > Comments > > > > Approval/Status > > 2009-08-17 > > > > 0.1 > > > > Initial draft for QE team review > > > > submitted to QE team and I-team > > 2009-08-25 > > > > 0.2 > > > > Incorporate I-team comments > > Updated Schedules and Milestones section according to new schedule > version text_installer_082409.pdf > > > > submitted to caiman-discuss > > 2009-09-04 > > > > 0.3 > > > > Incorporate Andre and I-team comments > > Updated Schedules and Milestones section according to new schedule > version text_installer_083109.pdf > > > > submitted to caiman-discuss > > 2009-09-14 > > > > > > > Incorporate Andre and I-team comments > > > > submitted to caiman-discuss > > > > > > > > > > > > > > References > > * > > Pointer to the ON test plan: > > * > > Pointer to the C-team project plan: N/A > > * > > Pointers to other documentation useful in understanding the test > program: > > * > > OpenProj Plan: 08/31/2009: > > https://securewiki.sun.com/download/attachments/24052578/text_installer_083109.pdf?version=1 > > * > > Functional Spec: > > http://www.opensolaris.org/os/project/caiman/TextInstallerProject/text_install_spec_v3.txt > > * > > Project Documentation: > http://www.opensolaris.org/os/project/caiman/TextInstallerProject/ > > * > > UI Spec: > > http://xdesign.sfbay.sun.com/projects/solaris/subprojects/install/design/screensText2.html > > * > > OpenSolaris 1002 Schedule: > http://infoshare.sfbay/twiki/bin/view/Main/OpenSolaris201002Schedule > > * > > > Staffing > > Name > > > > Role > > > > % Commitment > > > > Duration > > Angela Li > > > > Lead > > > > 100% > > > > 6 months > > Jason Zhao > > > > Engineer > > > > 50% > > > > 6 months > > Rokh > > > > Engineer > > > > 50% > > > > 6 months > > > > Glossary > > Term > > > > Definition > > curses > > > > a library of terminal I/O functions that provide the user with a > terminal-independent method of updating character screens with > reasonable optimization. > > nCurses (new curses) > > > > a freely redistributable emulation of the curses library in System V > Release 4, which also provides many useful extentions/enhancements over > SVR4 Curses. > > extended partition > > > > a primary partition (x86) that has been divided up into logical > partitions as a means of creating more partitions than the four that > would otherwise be possible. Only one primary partition can be used as > an extended partition, and it can be created from any of the primary > partitions. > > Transfer Module > > > > Software component on the DVD that copies the OS from the DVD to hard disk. > > > > Test Program Summary > > Interactive Text-based Installer provides interactive text-based install > capability for SPARC and x86. The primary target is server > installations. It also enables OpenSolaris installation in systems > without a graphics card and networking. > > The major components of Text Installer are as the following: > > * > > nCurses UI equivalent to current GUI installer > > * > > Static IP configuration > > * > > VTOC Slice management > > * > > extended partitions > > > For Static IP Configuration, it assumes the use of an existing utility > or method for configuring network information (e.g. SMF profiles). If no > such utility exists, it will have to be developed. > > For extended partition management and slice management and preservation, > it is assumed that the necessary library code will already be available. > The Text Installer's role in these areas is purely that of the UI. > > Language and Keyboard layout are selected prior to starting the Text > Installer (similar to how the LiveCD asks for language and keyboard > prior to starting the gdm desktop environment). There is no longer a > screen to modify the language via the text installer. The selection of > language during boot will be what is used on the installed system (can > be modified by the user later). > > The test program will focus on the Text Installer user interface (UI). > Test assertions will be developed for the functionality of the Text > Installer user interface (UI). Some user cases will be covered, such as > interoperability test. > > The test program include manual test and automated test. The manual test > (including semi-automated test) covers Text Installer display test, > interoperability test and installation where there is older release. The > automated test covers function test on Text Installer UI, including > actions on screens, error handling for user input. Test execution > includes two test cycles before integration. > > QE team will develop an automated test suite (textui), and the Text > Installer automatic test suite will be delivered at the same time when > the project integrate. > > QE team will have two test cycles based on stable bits delivered by > developers. > > The Text Installer automatic test suite will be under TET-CTI test > environment whenever possible, although there are expected to be a few > tests that do not lend themselves to automation that will be executed > manually. > > The automatic test suite will use EXPECT to capture the content of Text > Installer UI screen. > > Testing will not focus the stress test, performance test and conformance > test. > > > Operational Factors > > > Assumptions > > _*Assumption #1:*_ For automated test requirement, all the Text > Installer's output, especially strings in the screens and pop-up > windows, could be captured by EXPECT, EXPECT could do input to the Text > Installer. > > _*Assumption #2:*_ The fully internationalization support testing will > not be covered by the test program. > > _*Assumption #3:*_ The two test cycle will be based on stable testable bit. > > > Dependencies > > _*Dependency #1:*_ The testable bits will be provided as early as > possible for QE develop automated test suite. > > > Risks > > _*Risk #1:*_ > > *Description:* Any difference between the Text Installer's design > and implementation may lead the automated test suite change. > *Likelihood of Occurrence: *High > *Mitigation and Contingency Plan:* Tests will be developed most > independent with the Text Installer's implementation. > > _*Risk #2:*_ > > *Description:* QE team are working on a large number of install > projects at the same time, other install projects' schedule changing > will impact our part-time QE staff. > *Likelihood of Occurrence: *High > *Mitigation and Contingency Plan:* Communicate and re-schedule. > > _*Risk #3:*_ > > *Description:* The Text Installer depends on extended partition > management and slice management and preservation. > *Likelihood of Occurrence:* Medium > *Mitigation and Contingency Plan:* Re-schedule. > > > > Test Development Information > > > Test Development > > Test Name > > > > Automated or Manual > > > > Test Type > > > > Project > Component > > > > Description > > testui (Quit) > > > > automated > > > > functional > > > > Text installer UI Quit > > > > Verity the Text Installer Quit option > > testui (Help) > > > > automated > > > > functional > > > > Text installer UI Help > > > > Verity the Text Installer Help option > > testui (Partition) > > > > automated > > > > functional > > > > Text installer UI Partition > > > > Verity the Text Installer Partition Management, including Extended > Partition on X86 > > testui (Slice) > > > > automated > > > > functional > > > > Text installer UI Slice > > > > Verity the Text Installer Slice Management and Preservation > > testui (Network) > > > > automated > > > > functional > > > > Text installer UI Network > > > > Verity the Text Installer Network hostname and interface configuration > > testui (TZ) > > > > automated > > > > functional > > > > Text installer UI Time Zone > > > > Verity the Text Installer Time Zone configuration > > testui (Date_Time) > > > > automated > > > > functional > > > > Text installer UI Date and Time > > > > Verity the Text Installer Date and Time configuration > > testui (User) > > > > automated > > > > functional > > > > Text installer UI User > > > > Verity the Text Installer User configuration > > testui (Screen) > > > > automated > > > > functional > > > > Text installer UI Screen Navigation > > > > Verity the Text Installer Screen Navigation, including Go Back with > correct setting remembered > > testui (Install) > > > > automated and semi-automated > > > > functional > > > > Text installer Installation > > > > Verity the Text Installer ability to perform an actual installation > > Display > > > > manual > > > > functional > > > > Text installer UI Screen Display > > > > Verity the Text Installer Screen Display, also go through the small menu > of choice briefly > > > > Areas of Testing > > > Functional Testing > > Verify all options in the Text Installer UI. > > The Text Installer will have the following screens: > > * > > Intro/Navigation > > * > > Disk Selection > > * > > Fdisk Partition List (x86 only) > > * > > Fdisk Partition Management (x86 only) > > * > > VTOC Slice Management > > * > > Network > > * > > Manual Network Configuration > > * > > Time Zone (region) > > * > > Time Zone (locations) > > * > > Time Zone Selection > > * > > Date/Time Setting > > * > > Root password and User Account > > * > > Summary and Pre-Installation Review > > * > > Installation Progress > > * > > Installation Results > > * > > Help screens > > > Each action on each screen will be covered, including Continue, Back, > Help, and any specific action on specific screens. > > Valid user input and invalid user input will be carried out to test > error handling. > > Post installation verification will be covered, including partition and > slice, system settings or IP configuration, TZ, user. > > > Regression Testing > > The Text Installer is a brand new project, so no regression testing. > > > Conformance Testing > > The Text Installer does not have to conform to any standards so no > conformance testing is planned. > > > Stress/Robustness Testing > > No stress and robustness testing. The installer runs on an OS image with > only one user account enabled. > > > Performance Testing > > The Text Installer will provide comparable install-time performance > to the GUI installer (for x86), relative to the size of the image. > No performance testing, but the overall installation time will be > collected to say whether it meets the Text Installer's function > specification. > > > Memory Leak Testing > > Memory leak testing isn't applicable to the installer, as it runs in a > one-user microroot environment that will typically be rebooted as soon > as the installation is complete. > > 512MB memory installation test will be covered to make sure the low > memory limitation requirement. > > > Required Solaris Feature Testing > > The installer runs on a Solaris microroot using a DVD/USB/CD as the boot > media and a small ramdisk as the only writable space, so the normal > required feature testing does not apply during the install process. When > booted an installation on disk, some required feature testing can be done: > > * > > Zones Testing: N/A > > * > > ZFS Testing: Once installed, the system will be running on a ZFS > root. The functionality of the zpool command with regards to the > root file system will be verified indirectly. > > * > > Trusted Extensions Testing: N/A > > * > > xVM Guest OS Testing: Only HVM will be tested, as PV > (para-virtualized) has the same installation process with HVM. > > * > > LDOM Guest OS Testing: Will attempt to install Solaris under LDOM. > > * > > virtual box: Will attempt to install Solaris under virtual box. > Currently the latest VB version is 3.0.4. > > > Interoperability Testing > > Installs on systems with pre-existing installations of other OS types > (Windows, Linux) will be performed to verify that Solaris can be > installed alongside other OS's. > > > Documentation Testing > > QE team will review and provide feedback on user level documentation > shipped with product, including README, release notes, and help. > > > Internationalization Testing > > Only basic verification that the specified locale and language support > are installed will be performed. > > > Additional Testing (e.g. BCP, EA Programs) > > Low-memory testing: Install will be performed on a system with the > minimum (512MB) supported memory configuration. > > Minimum disk size testing: Install will be performed on a system with > the minimum disk size (3GB). > > > Testing Not Covered > > Any testing beyond verifying the installer UI itself, such as Extended > Partition, Partition Management, Slice Management, Static IP Management. > > The Transfer Module for transfer of contents from the DVD to hard disk, > and basic verification of the installed OS is beyond the scope of this > test plan. Targeted testing of bundled Solaris components or > applications (X, Firefox, etc.) are left to other groups as coordinated > by the overall OpenSolaris 1002 test lead. > > The internationalization test is out of test scope. > > Text Installer test will be executed using install media DVD and USB stick. > > The small menu of choice is not the focus of our test, we will go > through it briefly in the display manual case. > > > Test Execution > > > Hardware Test Configurations > > The following HW platforms will be tested in various combinations: > > * > > sun4u , sun4v, i386, amd64 > > * > > low memory configurations (in addition to normal memory > configurations) > > * > > VM tech: xVM, Virtual Box, LDOM > > As the Text Installer is platform-independent, we will not exhaust all > the combinations. > > > Software Test Configurations > > Mostly N/A, as the install image containing Text Installer controls the > version of Solaris and all applications/utilities that will be > installed. Testing of software beyond the installer itself and > verification of basic OS functionality is beyond the scope of Solaris > QE's qualification. > > > Extrapolation Strategy (if applicable) > > As the Text Installer is platform-independent, we will not exhaust test > on all hardware combinations. > > > Pre-Integration PIT Run > > * > > Is a pre-integration PIT run required? (REQUIRED, RECOMMENDED, > NONE)? NONE - the Text Installer bits will be integrating into > Slim_source, not into Solaris consolidations. > > * > > If a pre-integration PIT run is required or recommended, should > the run be the OS PIT, Net PIT or both? > > > Test Execution Matrix > > *Table 6.4.1: Machine HW/SW Configurations* > > # > > > > Model > > > > Type > > > > Host Name > > > > Arch > > > > Memory > > > > Kernel > > > > Virtualization > > 1 > > > > Dell270 > > > > desktop > > > > raindoctor > > > > i386 > > > > 512M > > > > 32 > > > > N/A > > 2 > > > > PC - Core2 > > > > desktop > > > > rainout > > > > amd64 > > > > 2G > > > > 64 > > > > N/A > > 3 > > > > Sun Ultra 40 M2 > > > > workstation > > > > rainboot > > > > amd64 > > > > 4G > > > > 64 > > > > xVM > > 4 > > > > Sun Ultra 40 > > > > server > > > > rainday > > > > amd64 > > > > 1G > > > > 64 > > > > Virtual Box > > 5 > > > > Sun Blade 150 > > > > server > > > > rainbox > > > > sun4u > > > > 512M > > > > 64 > > > > N/A > > 6 > > > > Sun T2000 > > > > server > > > > redmoon > > > > sun4v > > > > 8G > > > > 64 > > > > N/A > > 7 > > > > Sun T2000 > > > > server > > > > earthcolor > > > > sun4v > > > > 3G > > > > 64 > > > > LDOM > > > > *Table 6.4.2: Test Suite Execution* > > # > > > > Test Suite Execution > > 1 > > > > textui > > 2 > > > > > > > Schedules and Milestones > > Milestone > > > > Original Date > (yyyy-mm-dd) > > > > Actual Date > (yyyy-mm-dd) > > Test Plan First Draft > > > > 2009-08-21 > > > > 2009-08-17 > > Text Installer Design Completed > > > > 2009-08-31 > > > > > Test Plan I-team Approval > > > > 2009-09-18 > > > > > Test Plan QE Management Approval > > > > 2009-09-18 > > > > > Test Assertions Completed and Approved by I-team > > > > 2009-09-25 > > > > > Text Installer Code Complete > > > > 2009-10-23 > > > > > Automated Test Suite Code Completed > > > > 2009-10-30 > > > > > Text Installer Code Review Complete > > > > 2009-11-11 > > > > > Automated Test Suite Test Completed > > > > 2009-11-16 > > > > > First Test Cycle before Integration > > > > 2009-11-16 > > > > > Second Test Cycle before Integration > > > > 2009-11-30 > > > > > Automated Test Suite Code Review Completed > > > > 2009-11-30 > > > > > Automated Test Suite Integration into STC > > > > 2009-12-04 > > > > > Text Installer Integrated > > > > 2009-12-04 > > > > > Integration into ON PIT > > > > TBD > > > > > > > Post-Integration Testing Information > > > Test Suite Integration Requirements > > Test/Test Suite Name > > > > Source Integration Location > > > > Target Integration Date > > > > Comments > > textui > > > > STC > > > > 2009-12-04 > > > > > > > > > > > > > > > > > Test Suite Execution Integration Requirements > > Test/Test Suite Name > > > > Execution Group > > > > Comments > > textui > > > > PIT > > > > > > > > > > > > > > Other Post-Integration Requirements > > N/A > > > Solaris Update Release (if applicable) > > Not applicable. > > >
