[ Home || Printable Version ]         NetSoft Network Monitor Suite: System Test Plan * 1. Introduction * Objectives * Scope * Level 1 – Requirements * Level 2 – Requirements * Level 3 – Requirements * 2. System Test Environment * 3. System Test Personnel * 4. System Test Schedule * 5. Load Testing * 6. System Test Description * Level 1 – System Test Descriptions * Level 2 – System Test Descriptions * Level 3 – System Test Descriptions * 7. Traceability * 8. System Test Reporting * 9. Constraints * 10. Sign Off * Appendix-A * Appendix-B *           NetSoft Network Monitor Suite: System Test Plan   1. Introduction Objectives The NetSoft System Tests are compiled of a wide variety of rigorous system tests to verify the functionality and reliability of the NetSoft software package. Tests will be implemented in such away as to sufficiently test all boundary and null cases. Tests will be traceable to all documents to ensure that the NetSoft software meets all expected requirements in a consistent manner. Scope System tests will include all customer requirements, such as: Level 1 – Requirements Monitor Traffic on LAN Capture Packets on LAN Display Details on Individual Frames Monitor Performance on LAN Trigger Alarm Function Common Protocols are Supported Program has Low Overhead Centralized Program with Intuitive Interface Generate Graphical Display of the Network Generate and Send Packets over LAN Network Address Mapping Database Containing Performance Measurements System is Configurable Help Menu Level 2 – Requirements Smart Installation Program Packet Filtering Tool Tips Level 3 – Requirements Smart Uninstall Program Generate HTML Page Containing Network Statistics Dos Interface Provided Other Common Protocols are Supported Detect Network Card Problems A series of load tests will be conducted to check for problems under heavy network traffic. 2. System Test Environment NetSoft system tests will be conducted on a Ethernet LAN running at 10 MBPS or 100 MBPS in the NetSoft Inc. laboratory located at 2300 Ryan Rd Courtenay, BC,V9N 8N6, as well as an ISP cable connection at Todd Ballard’s test lab located at 13 - 951 17th St Courtenay, BC V9N 7P8. The tests will be performed on various hardware platforms, including Windows 9x/2000/NT operating systems. In order to simulate a typical customer environment, all software platforms will have either Norton AntiVirus or McAfee AntiVirus installed. Hardware specifications for test PC’s in the NetSoft Inc. laboratory are listed below. Computer Hardware Specifications Computer # 23 · Windows 2000 · McAfee AntiVirus · 166 MHz Pentium microprocessor · 64 MB Ram · 1.6 GB hard drive · NE 2000 NIC · 800 x 600 d.p.i resolution · GVC SVGA monitor CS 6 · Windows NT 4.0 · 133 MHz Pentium microprocessor · 16 MB Ram · 2.1 GB hard drive · Novell NE 2000 NIC · TTX SVGA colour monitor Computer # 20 · Windows 98 · 350 MHz microprocessor · 64 MB Ram · 2.1 GB hard drive · RealTek network card RTL8029 · 1024 x 768 d.p.i resolution · Seanix SVGA colour monitor Hardware specifications for test PC in Todd Ballard’s laboratory is listed below: Computer Hardware Specifications Computer # TB1 · Windows NT 4.0 · 200 mhz microprocessor · 64 MB SDRAM · 6.4 GB Hard drive · RealTek network card RTL8029 · 800 x 600 x 32768 colours · Acer AcerView 33D SVGA monitor 3. System Test Personnel The testing staff will consist of in-house team members as well as system administrators to ensure proper detection of any anomalies or problem areas. Administrators will install the software, using the software install documentation. Once installed the administrators will test all common features of the software using the help files. Using rigorous system tests described later in this document, the in-house team members will observe and document any problems and user feedback encountered during this test phase. In-house testing staff: Allen Warner – Programmer/Analyst Don Murphy – Network Specialist Todd Ballard – Programmer Lionel Dube - WebSite Administrator 4. System Test Schedule System testing is scheduled to commence on March 7, 2000 and run through April 4, 2000. However, system testing is dependant upon the system integration testing, therefore system testing will not commence until the successful completion of the system integration tests. Furthermore, if part of the system is incomplete system testing cannot begin. 5. Load Testing Load tests are intended to verify the systems ability to withstand abnormal and extreme conditions. Various sub-systems will be invoked simultaneously and any errors or anomalies will be recorded in an error log sheet. All load test and stress tests will be supervised by our network specialist Don Murphy. 6. System Test Description All diagnostic tests will be conducted using controlled network/packet data as well as real time data. All system tests performed on requirements specifications will be referenced by number, as defined in the Requirements Specifications document. System tests will also be referenced by number to the Architectural Design document –see Appendix A for details. To help determine factors such as packet loss, correct network variables, throughput and accurate calculations, all variables will be checked against values obtained from another monitoring tool running in parallel with NetSoft’s system. Resource usage will be monitored to determine program overhead. ST– refers to System Test   Level 1 – System Test Descriptions 1-1.0.0 Monitor Traffic on LAN ST–1 Get adapter names, select adapter, open adapter, count packets, close adapter Action: User invokes Monitoring Sub-system through System Interface Controller, and selects adapter from the user interface. Test pass condition: Monitoring Sub-system is activated, count of all packets are returned. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.2, 2, 4, 6 - see Appendix A 1-1.1.1 Capture Packets on LAN ST–2 Capture packets and fill buffer Action: User invokes Monitoring Sub-system through System Interface Controller, and opens adapter Test pass condition: Monitoring Sub-system is activated, all packets on network are captured and put in the buffer. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.2, 2, 4, 6 - see Appendix A 1-1.1.2 Display Details on Individual Frames ST-3 Retrieve individual frames, display frames Action: Through user interface, user invokes the Snap Shot Sub-System, nested within the Monitoring Sub-System. Test pass condition: Complete detailed data including total size, physical addresses and payload contents in the frame is displayed in the frame display window in list format. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 2, 4, 6 - see Appendix A 1-1.1.3 Monitor Performance on LAN ST-4 Retrieve system variables, compare and display results Action: User invokes Monitoring Sub-system through System Interface Controller and starts packet capture. Test pass condition: Monitoring sub-system is activated, network variables are calculated and correctly displayed to the GUI in the form of a line graph. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.3, 1.2, 2, 3.1, 4, 6 - see Appendix A 1-1.1.3.1 Trigger and Alarm Functions ST-5 Retrieve system variables, alarm trigger and calculate statistics Action: Through the user interface, the user sets the alarms triggers in the Configuration Sub-System. Test pass condition: Alarm conditions must match system configuration settings. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.1.3, 1.2, 2, 4, 6 - see Appendix A 1-1.2.0 Common Protocols are Supported ST-6 Run system on network using the TCP/IP Protocol Action: All system features will be tested using the TCP/IP protocol, as outlined in previous tests. Test pass condition: All system features and or functions respond appropriately. Stress test pass condition: Test is performed 100 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.1.3, 1.2, 2, 4, 6 - see Appendix A 1-2.0.0 Program has Low Overhead ST-7 Run system on network, run a variety of other programs as well Action: System resource use will be monitored while other programs are sharing resources and downloading is in progress. Test pass condition: CPU resources are at a minimal level. Stress test pass condition: Test is performed 100 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.1.3, 2, 6 - see Appendix A 1-2.0.1 Centralized Program with Intuitive Interface ST-8 Menu items , option buttons, option boxes and popup windows Action: User selects option button/box or menu item from GUI interface. Test pass condition: Selected features and or functions respond appropriately and all buttons and menu items have unique icons. User interface utilizes natural mapping of all controls. All windows, popup menus and option boxes resize correctly and have a consistent look and feel. Error messages are readable, logical and displayed in a visible area. Reference to Sub-System and/or Module: 2 - see Appendix A 1-2.4.0 Generate Graphical Display of the Network ST-9 Display network statistics in an understandable line graph format Action: Click on the Start Capture button and view the network performance on the graph. Test pass condition: The graph correctly reflects the present network throughput. The graph is clear and understandable. Reference to Sub-System and/or Module: 1.1.1, 1.1.3, 1.2, 2, 2.4 - see Appendix A 1-2.7.0 Generate and send Packets over LAN ST-10 Make ping system call, analyze and display system call results Action: User selects appropriate menu function to invoke ping system call. Ping will send series of packets to address for testing purposes. Test pass condition: Ping system call is invoked, transmission is analyzed and results are displayed to the GUI. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.2, 1.2, 2.7, 6 - see Appendix A 1-2.8.0 Network Address Mapping ST-11 Make system call for address resolution Action: User selects appropriate menu function to acquire IP address or manually enters IP address. Function will make system call using numeric/string IP address. Test pass condition: Correct IP format is mapped from user input and displayed to GUI. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.3, 2, 2.8, 6 - see Appendix A 1-3.0.0 Database Containing Performance Measurements ST-12 Gather information on network, generate reports, return results Action: User invokes Monitoring and Log Sub-system by clicking the Log Reports button Test pass condition: Accurate and timely reports on network traffic are printed or displayed to the GUI. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 1.1.1, 1.1.3, 1.2, 2, 3.1, 3.2, 6 - see Appendix A 1-4.0.0 System is Configurable ST-13 Change default system settings to user preference settings Action: User invokes Configuration Dialog Box Test pass condition: User input is successfully checked for incorrect input. User settings are saved and can be recalled at any time. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: 4 - see Appendix A 1-5.0.0 Help Menu ST–14 Functional help system – integrated approach Action: User presses F1 key then clicks file menu item, or user selects Help from the menu bar, or user clicks the Help button on the toolbar. Test pass condition: Appropriate help menu is displayed each time. Stress test pass condition: Test is performed 200 times without failing. Reference to Sub-System and/or Module: 5 - see Appendix A Level 2 – System Test Descriptions 2-0.0.0 Smart Installation Program ST–15 Install package Action: User selects the Setup.exe file and specifies target directory to invoke installation of software. If user does not select directory the default directory is checked for correct installation files. System registry will also be checked for appropriate settings. Test pass condition: All program files, folder items and icons are installed into correct directories, changes to registry are correct, installation is successful and software functions correctly. Stress test pass condition: Test is performed 100 times without failing. Reference to Sub-System and/or Module: Not Implemented 2-0.0.1 Packet Filtering ST–16 Set Address filtering Action: User will set filter in the Configuration Sub-System by entering network address. The interface controller will signal hardware and monitoring sub-system will filter output using promiscuous, directed, multicast and broadcast mode respectively. Test pass condition: Only selected addresses/packets are displayed to the GUI. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: Not Implemented 2-2.0.2 Tool tips ST–17 Tool tips Action: User will place mouse over all appropriate button and menu items. Test pass condition: Tool tip message will be displayed for each button or menu item. Stress test pass condition: Test is performed 500 times without failing. Reference to Sub-System and/or Module: 2. Level 3 – System Test Descriptions 3-0.0.2 Smart Uninstall Program ST–18 Install package Action: User double-clicks Uninstall.exe and the program uninstalls itself Test pass condition: All program files, folder items, icons and registry settings are removed Stress test pass condition: Test is performed 100 times without failing. Reference to Sub-System and/or Module: Not Implemented   3-0.0.3 Generate HTML Page Containing Network Statistics ST–19 Generate HTML Report Action: User invokes Monitoring and Log sub-system. User queries database logs through user interface. Results will be checked using either Internet Explorer or Netscape file browsers. Test pass condition: Reports on network traffic are displayed in HTML format. Stress test pass condition: Test is performed 500 times without failing. Reference to Sub-System and/or Module: Not Implemented 3-0.0.4 Dos Interface Provided ST–20 Command Line interface Action: All diagnostic, data retrieval and configuration functions will be invoked. Test pass condition: Program responds correctly as to previous test results. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: Not Implemented 3-0.0.5 Other Common Protocols are Supported ST–21 Other common protocols such as NetWare, or NetBEUI Action: All system features will be tested using protocols other than TCP/IP. Test pass condition: All systems and functions respond accordingly. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: Not Implemented 3-0.0.6 Detect Network Card Problems ST–22 Test a workstation NIC for transmission problems Action: All diagnostic, data retrieval and configuration functions will be invoked. Test pass condition: Program correctly detects an NIC problem. Stress test pass condition: Test is performed 1000 times without failing. Reference to Sub-System and/or Module: Not Implemented 7. Traceability All tests performed will be referenced through a system test number ST-1 through ST-20. Each test is directly correlated to its original specification requirements. In many cases several requirements will be included in a single test. 8. System Test Reporting System test reporting will consist of complete and accurate test logs. These test logs will be maintained consistently with a test log completed for each test performed. The reports will consist of two forms: NetSoft Test Logs Maintained online in HTML format Kept current Share results and up-to-date information amongst all system testers and project leaders Incident Report Used to record any unusual incidents Reviewed by our Network Specialist and signed by the project leader. See Appendix-B for example forms 9. Constraints The constraints which may affect the system testing plan are as follows, Successful completion of the integration test plan Delivery date deadline 10. Sign Off The NetSoft system tests ensure that the NetSoft Monitoring Suite will meet all expected customer requirements. Upon successful completion of the system test plan and all detected error conditions have been dealt with accordingly, the System Test Team will sign off their phase of the project.     Appendix-A Sub-systems referenced from the Architectural Design document: 1. Monitoring Sub-system 1.1 Diagnostic Sub-system 1.1.1 Real Time Module 1.1.2 Snap-Shot Module 1.1.3 Calculations Module 1.2 Packet Sub-system 2. System Interface Controller Sub-system 3. Database Log Sub-system 3.1 Database Handler Sub-system 3.2 Report Generator Sub-system 4. Configuration Sub-system 5. Help Sub-system 6. Hardware Sub-system     Appendix-B Example NetSoft Test Log form: NetSoft.Inc Test Log Date Personnel Test Code Time Start Time End Test PC # Errors Example NetSoft Incident Report form: NetSoft System Test Incident Report Test Name: Test Code: Test Date: Test Personnel: Error Description: Comments: Dependant Modules: Programmer Notified: Project Manager Notified: [ Home ]