1 / 27

Automatic Software Testing Tool for Computer Networks

Automatic Software Testing Tool for Computer Networks. ADD Presentation. Dudi Patimer Adi Shachar Yaniv Cohen. www.cs.bgu.ac.il/~adishach. Table of Contents. Introduction System Requirements System Architecture Main Classes User Interface Open Questions Task List.

evan
Download Presentation

Automatic Software Testing Tool for Computer Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automatic Software Testing Tool for Computer Networks ADD Presentation Dudi Patimer Adi Shachar Yaniv Cohen www.cs.bgu.ac.il/~adishach

  2. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  3. Previously… Access Layers' flagship product, Portnox, is a natural extension of existing security policies and methodologies, allowing network administrators to configure access parameters for physical network ports, and proceed to monitor, control, and manage LAN entities, including devices, switches, ports, access slots, and more. Portnox represents a new approach to LAN protection, providing complete online control of end-point access to the corporate network. Portnox allows networks administrators to determine which devices are allowed LAN access.

  4. The Problem Domain When Access Layers QA's testers execute tests on their software they need to change the settings of an end-stations and to perform different actions, for example: turning on/off the computer, changing the IP address, enable/disable Ethernet card, changes in the network settings of the end-station, login/logoff with users, etc. Nowadays, in order to execute the actions and the setting changes, they should execute all the necessary actions manually in the end-stations.

  5. Solution Our project allows performing all the above actions automatically from a central station with simple GUI, and in addition to view the status of the end-stations at any step. Furthermore, our tool will be able to add and execute new scripts that were written by the testers on the end-stations, manage the scheduling of these actions, meaning to execute actions in chosen order, and to schedule the execution order of the end-stations. Moreover, the tool will enable the testers to perform tests that they could not perform before, such as simultaneously executing actions on group of end-stations or by a given schedule.

  6. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  7. Reminder • Action – There are 4 types of actions in our system: • Command Line (with parameters). • VB Script. • Delay Action. • Test Action – a script that compares the expected results with the product database. • TSC (Test Scenario) – Composed of the following components: • Basic Action (built in actions). • Action. • * Must contain Test action at the end. • TP (Test Plan) – Composed of TSC’s.

  8. System Requirements • Establish Connection & Getting General Information • Assemble/Modify/Delete a TSC and TP • Create/Modify/Delete Additional Actions • Execute TP, TSC or Single Action on remote end-stations • Generate Reports & Logs

  9. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  10. High-level System Architecture End-Stations Database TP’sTSC’sActionsParameters Action\Information\Results Server Main directory\ +Reports\ +Scripts\ ATS GUI

  11. Detailed System Architecture • Stores reports as XML in the local dir. • Loads scripts located under the local dir. • Saves/Loads actions/TSC’s/TP’s from the DB. End-Stations Sends command lines or scripts to the remote end-stations and gets the output. Database Action\Information\Results ActionsTSC’sTP’s DatabasePackage Service ProviderInterface Scripts Reports Test actions PortnoxDatabase ExecutionPackage Executes TP/TSC/Single action and manages the execution process. The main controller of the system that interacts with the user requests. ATS Manager GUI

  12. System Architecture Note: The communication between the ATS and the end-stations will be by using the external utility psexec command provided with pstools for Windows platforms administrators. Our design supports future extensions to other operating systems.

  13. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  14. Main Classes

  15. Main Classes

  16. Main Classes

  17. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  18. User Interface

  19. User Interface

  20. User Interface

  21. User Interface

  22. User Interface

  23. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  24. Open Questions • How to identify end-stations in our system?End-stations can be identified by their IP/MAC address, but our tests include changing IP and MAC address, so after executing such action we need to know the new address and who it belongs to. • How can we perform performance testing without using large amount of end-stations?

  25. Table of Contents • Introduction • System Requirements • System Architecture • Main Classes • User Interface • Open Questions • Task List

  26. Task List

  27. Questions?

More Related