Presentation on theme: "Automated Software Testing using Open Source Testing Tools By Elfriede Dustin."— Presentation transcript:
Automated Software Testing using Open Source Testing Tools By Elfriede Dustin
2 Agenda Who is IDT State of Software Testing What is Automated Test and Re-test (ATRT) Approach to ATRT Advantage of open source ATRT and open source – Our IDE and solution ATRT Challenges
3 Who is IDT? IDT specializes in the design, development, and implementation of Automated Software Testing and Re-Test (ATRT) and Quality Assurance (QA) solutions –Deliver turn key automated test suite Automated test strategy and identification of highest payoff areas to apply automation for your project Selection of best automation tools for your project Using your existing test cases or develop test cases for you Test results documented in requirements traceability matrix –Training and pilot project implementation with companies
4 Who is IDT? IDT specializes in the design, development, and implementation of Automated Software Testing and Re-Test (ATRT) and Quality Assurance (QA) solutions –Deliver turn key automated test suite Automated test strategy and identification of highest payoff areas to apply automation for your project Selection of best automation tools for your project Using your existing test cases or develop test cases for you Test results documented in requirements traceability matrix –Training and pilot project implementation with companies We are currently hiring Java Developers Plus we’d like to hire 2 or 3 grad students to work for us part time ( i.e. 20 hours week ) must be US citizen
5 State of Software Testing - Why ATRT? ?
6 State of Software Testing - Why ATRT? Utilize Automated Testing Strategies and Technology to Improve Productivity and Quality Manual Automated Reduction in Test Days IDT Provides Automated Software Testing Solutions Increased Test Coverage Manual vs. Automated Spiral / Release 1 Spiral / Release 2 Spiral / Release 3 Spiral / Release 4 Size & Complexity of SW Baseline Test Days 50% or More of Overall Development Cost is Typically Spent on Testing
7 What is ATRT? Our definition of ATRT is: Application and implementation of software technology throughout the entire Software Testing Life Cycle (STL) and QA lifecycle; with the goal to improve STL efficiencies and effectiveness
8 ATRT Spans the Software Development Life Cycle – Visual Modeling F Modeling and test case generation Development Tools Components Use cases Desig n BuildAssembl e Round-Trip Engineering Test
9 ATRT Spans the Software Development Life Cycle – Requirements FOrganizes, tracks, & controls requirements FRequirements Traceability Matrix (RTM) Development Tools Components Visual Modeling Requirements Management and Process Automation
10 Automated Software Testing ATRT Spans the Software Development Life Cycle – Automated Test Tools Development Tools Components Visual Modeling Execution Management Development Requirements Management and Process Automation FAutomates test cases using vendor-provided, open-source tools or in-house development Automated Testing Tools
11 ATRT Spans the Software Development Life Cycle – Integrated Suite of Tools Additionally: FMiddleware FInfrastructure FDefect Tracking FConfiguration Management FMemory Leak Detectors FPerformance Testing Tools FDocumentation Tools Fothers Development Tools Components Visual Modeling Automated Testing Tools Requirements Management and Process Automation Software Configuration Management Defect Tracking Middleware Infrastructur e
12 Types of Software Test Life-cycle Support Tools Which tools are you familiar with?
13 Types of Automated Test Tools Life-Cycle Phase Type of ToolTool Description Business Analysis Phase Business ModelingRecords definitions of user needs and automates rapid construction of flexible, graphical, client-server applications Configuration Management Baselines important data repositories Defect TrackingManages system life-cycle defects Technical Review Management Facilitates communication, while automating the technical review/inspection process Documentation Generators Automate document generation Requirements Definition Phase Requirements Management Manages and organizes requirements; allows for test procedure design and test progress reporting Requirements Verifiers Verify syntax, semantics, and testability Use Case Generators Create use cases
14 Types of Tools (Cont’d) Programming Phase Memory Leak and Runtime Error Detection Detects runtime errors and memory leaks Source Code TestingVerifies maintainability, portability, complexity, and standards compliance Static and Dynamic Analyzers Depict quality and structure of code Life-Cycle Phase Type of ToolTool Description Analysis and Design Phase Database DesignDevelops second generation enterprise client-server systems Structure Charts, Flowcharts, and Sequence Diagrams Manage processes Test Procedure Generators Generate test procedures from requirements, design, or data and object models Syntax Checkers/ Debuggers Perform syntax checking and have debugging capability; usually available with built-in programming language compiler Metrics ToolsCode (Test) Coverage Analyzers or Code Instrumentors Identify untested code and support dynamic testing Usability MeasurementsProvide usability testing as conducted in usability labs
15 Types of Tools (Cont’d) Life-Cycle Phase Type of ToolTool Description Other Testing Life-Cycle Support Tools Data Extraction ToolExtract Data from various formats into various formats Test Data GeneratorsGenerate test data File Compare UtilitiesFind discrepancies between files that should be identical in content SimulationSimulates application to measure for scalability, among other tasks Test ManagementTests management Network TestingMonitors, measures, tests, and diagnoses performance across the entire network GUI Testing (Capture/Playback) Conducts automated GUI tests; capture/playback tools record user interactions with online systems so they may be replayed automatically Load/Performance TestingConducts load/performance and stress testing Security TestingPerforms security testing and vulnerability scanning at the application or network level; plus debuggers will allow to check for security coding errors (source code checkers)
16 Deployment Approach – Adapted ATLM Collect/Create: Requirements Test Cases Test Procedures Expected Results Interface Specifications System/Component Configuration Description Identify or Develop & Pilot Test Manager Test Scripts Data Comparators Performance Test Tools GUI Record/Playback Storing/Retrieving Results Populate Test Manager with Test Cases and Requirements Develop Test Scripts from Test Procedures Test Results: Pass/Fail by Test Case Pass/Fail Summary Test Time Required
17 Why Open Source ?
18 Why Open Source? Advantage of Open Source: –no licensing issues; i.e. license cost; maintenance; etc. –easily modifiable –adaptable –lightweight –flexibility - not tied to one vendor
19 ATRTs IDE - Eclipse Eclipse – this site lists all the plugins plugins.info/eclipse/plugins.jsp?category=SCM&pager.offset=0&firstItem=1 plugins.info/eclipse/plugins.jsp?category=SCM&pager.offset=0&firstItem=1 Eclipse/TPTP – Open Source - Developed by IBM –Eclipse/Test and Performance Tools Platform (TPTP) offers a common extensible framework for the following functions: Requirements Management Configuration Management - Subversion Testing Tools (http://www.nabble.com/Eclipse-TPTP---Testing- Tools-f2262.html) Profiling: default Java applications, but can be extended to other apps
20 ATRTs IDE - Eclipse Eclipse/Test and Performance Tools Platform (TPTP) offers a common extensible framework for the following functions (cont): Static Analysis: default for C++ and Java, but can be extended to other apps Application monitoring and log analysis Build tool – ant Xml input and output - using an open source Java package which is a Java library that has an API for constructing and outputting XML. Test Manager – STAF/STAX
21 Current Test Tool Implementation – Example and Challenges Vendor-provided (Capture/Playback) Tool: Automated test tools mimic actions of the test engineer. During testing, the engineer uses the keyboard and mouse to perform some type of test or action. Testing tool captures all keystrokes and subsequent results, which are baselined in an automated test script. During test playback, scripts compare latest outputs with previous baseline. Testing tools have built-in, reusable test functions. Most test tools provide for non-intrusive testing; i.e., they interact with the “application-under-test” as if the test tool was not involved.
22 Current Testing Tools – Challenges (cont) In-House Software Development required: Capture/Playback tools generate hard-coded values; test scripts are not reusable, nor do they implement software development best practices right out of the box; scripts need to be modified. Capture/Playback tools don’t necessarily provide all testing features required; code enhancements are often required to meet testing needs. Capture/Playback tools are not necessarily compatible with system engineering environment, and software testing scripts need to be developed in-house. Developed testing scripts are not cross-vendor compatible, even if the same scripting language is used
23 Linux Capture/Playback Tools IDT Findings Replay Xcessoryhttp://www.scl.com/products/ics/motif/testing/replay/ QF-Testhttp://www.qfs.de/en/qftestJUI/index.html Froglogichttp://www.froglogic.com/pg?id=Google&category=squishjava Redstone SoftwareEggplant KD Executorhttp://www.kdab.net/?page=products&sub=kdexecutor Jameleonhttp://sourceforge.net/projects/jameleon/ ShUnit2for shell scripts testing GNU Linux Desktop Projecthttp://ldtp.freedesktop.org/wiki/Home Cantanahttp://www.ipl.com/pdf/p0003.uk.pdf crontabPart of Unix crontab, cruisecontrol, Dogtailhttp://people.redhat.com/zcerza/dogtail/about.html dogtail-tool.html Expecthttp://expect.nist.gov/
24 Automated Test and Re-Test (ATRT) ATRT includes a common framework comprised of re-usable software services –Open Source Software Test Automation Framework (STAF) Provides automated test procedures, test inputs, and test results for SW components –Suitable for use by 3 rd parties not associated with development of the component
25 STAX is an automation system With STAX you can automate and monitor your entire test environment ƒSystem/product setup ƒTestcase distribution ƒTestcase execution ƒTestcase results collection and analysis STAX consists of ƒA programming language designed for automation –Programs written in this language are called jobs ƒAn execution engine (similar to an interpreter for other programming/scripting languages) which manages the execution and runtime behavior of the job ƒA GUI application, called the STAX Monitor, which provides a dynamically updated view of your executing jobs ƒA tool (STAXDoc) that is used to generate documentation for your STAX jobs What is STAX?
26 * Windows 95 * Windows 98 (and 98 SE) * Windows Millenium Edition * Windows NT Version 4.0 * Windows 2000 * Windows XP * Windows Server 2003 (IA32, IA64, AMD64) * Windows Vista (IA32, AMD64) * Linux (Intel32/64, AMD64, PPC32/64) * Linux on zSeries (31-bit, 64-bit) * AIX Version or higher (32-bit, 64-bit) * Solaris (Sparc) 2.6 and higher * Solaris AMD Opteron 64-bit * HP-UX and higher (PA-RISC, IA64 32-bit and 64-bit) * OS/400 V5R2 or higher * z/OS UNIX V1.4 and higher STAF can run on:
27 STAF Internal Services DIAG Provides diagnostics services Internal ("DIAG") DELAY Provides a means to sleep a specified amount of time Internal ("DELAY") ECHO Echos back a supplied message Internal ("ECHO") FILE SYSTEM Allows you to get and copy files across the network Internal ("FS") HANDLE Provides information about existing STAF handles Internal ("HANDLE") HELP Provides Help on STAF error codes Internal ("HELP") MISC Handles miscellaneous commands such as displaying the version of STAF that is currently running Internal ("MISC") PING Provides a simple is-alive message Internal ("PING") PROCESS Allows you to start, stop, and query processes Internal ("PROCESS") QUEUE Provides a network-enabled IPC mechanism for STAF Programs Internal ("QUEUE") SEMAPHORE Provides network-enabled named event and mutex semaphores Internal ("SEM") SERVICE Allows you to list services available on a machine and to examine the Requests that have been submitted on a machineInternal ("SERVICE") SHUTDOWN Provides a means to shutdown STAF and register for shutdown Notifications Internal ("SHUTDOWN") TRACE Provides tracing information for STAF services Internal ("TRACE") TRUST Interfaces with STAF's security Internal ("TRUST") VARIABLEProvides a method for maintaining configuration and runtime data (variables) Internal ("VAR")
28 STAF External Services The executable code for external STAF services resides outside of STAFProc, for example in a Java jar file, a C++ DLL file, or a Rexx script file. CRON Calls into STAF services at a specified time interval External (Java) Allows you to send messages External (Java) EVENT Provides a publish/subscribe notification system External (Java) EVENTMANAGER Allows you to call STAF services when a specified Event occurs External (Java) HTTP Allows you to make HTTP requests which can be grouped together in a session External (Java) LOG Provides a full-featured logging facility External (C++) MONITOR Allows a testcase to publish its current running execution status for others to read External (C++) RESOURCE POOL Allows you to manage exclusive access to pools of elements, e.g. VM UserIDs or Software Licenses External (C++) STAX Provides an XML-based execution engine External (Java) ZIP Provides a means to zip/unzip/list/delete PKZip/WinZip compatible archives External (C++)
29 STAF ƒSTAF provides the infrastructure on which STAX builds. The full power of STAF and its services is exposed for use within STAX jobs. XML ƒThe STAX programming language is based on XML. This provides built-in structure to your jobs, as well as providing a set of existing tools for use in constructing your jobs, such as XML (aware) editors and XSLT. Python ƒThe STAX programming language builds on Python to provide a rich and accessible data model ƒSTAX's Python integration also allows you to access the wealth of existing Python libraries Java ƒThe STAX programming language allows you to access existing Java classes/libraries, providing another source for reuse Technologies used in STAX
31 End-to-End Automation with STAF and STAX Event, EventManager, Cron FS, Process Process, Monitor, Log, Variable, Queue, ResPool Log, Process Process , HTTP STAXJobSTAXJob Automation Completion Results Notification Testcase Cleanup Testcase Output Analysis Testcase Execution System Setup Automation Startup
32 Key ATRT Architecture Requirements Support applications running on multiple computers Support applications developed in different languages Support applications running on different types of OS’s Support applications which have GUI and those which do not (for example Interface testing) Support applications which use different types of network protocols such as TCP/IP, DDS, etc Support integration of multiple commercial testing tools from different vendors ( allowing as new or better products emerge in the market they can be utilized ) Support testing w/o having to install ATRT on the same computers as the application under test and be able to be distributed across computers
33 Display Application Analysis & Display Application Simulation of Application Processing Messages Simulation of Application Processing Messages System Under Test Test Manager RTM Bugzilla ATRT Eggplant R/P VNC Robot R/P STAF/STAX Prototype – Proof of Concept Windows Based Linux Based
34 Able to successfully execute ATRT for 48 hours without operator intervention During the tests: VNCRobot - Approximately 25,000 operator key strokes were replayed STAF/STAX - More than 1,000,000 messages processed and verified by ATRT ATRT Prototyping Effort
35 Additional Requirement Pristine test environment required – automated testing tool cannot be installed on Application- Under-Test PC Eggplant – allows for remote capture/playback via VNCserver and KVM switch VNCRobot
36 Automated Software Testing Software testing paradox What is it?
37 Effective Automated Software Testing Current State: Developing software in order to test software Automate the test support development: automated IDL to code generation; test data generation (using FireEye from NIST); compare utilities; log file analyzers; Our Automated Software Testing Goal: Minimize Human interaction –Possibly get on par with Hardware Automated Testing?
38 Hardware Testing: current state Many automated test generators for manufacturing/ logic devices, circuit testing, etc., available i.e. SEI/ATG, uMaster, etc. Automated testing without human interaction is the norm for hardware testing
39 Hardware vs. Software AT How is hardware testing different? Software Challenge: –Changing requirements –GUI interfaces –Code access/availability –Defects uncovered earlier in the software development lifecycle are cheaper to fix Solution flexibility required – problem dependent
40 Proposed solutions Focus on Reusable Components –Test Data / Expected Results –Interfaces –Middleware Assuming code and models are available: Model based testing; automated test case generators based on models Eclipse – effective ATRT IDE Probes – see Aprobe – Code instrumentation Building self-testable components Using standard language MOF to Text to generate automate test cases GUI Testing tool ideas New tools - other Working with NIST to produce additional tools
41 GUI Testing Jemmy - java library to test UI Perl modules run via VNCServer?
42 Questions ? with any follow-up
43 IDT We are hiring……. Please come see me now if interested or send with any