Download to read offline
PP_Eric_Gandt
- 1.
- 2. PERFORMANCE TESTING • Performancetesting of multiple enterprise applications, used to build and manage Web Sites • On-premises • Cloud • Used by many Fortune 500 • Including the four of the top ten • Scales to over 400 million hits per day • Scales from single instance to twenty plus server clusters • Responsible for Performance of the last eight releases • Managed a team of between two and four
- 3. PERFORMANCE TESTING • Responsibilities •Scenarios • Work with Clients and Project Management to design scenarios • Code Scenarios • Execute Scenarios • Monitor metrics • Document results • Created an Estimator for Oracle WebCenter Sites Products • Analyze results for statistical significance • Oversee Engineers executing Scenarios • Prove test cases and scenarios to the Performance Engineers • Prove tools used in monitoring and reporting results. • Assist the Engineering in improving the quality and reliability.
- 4. PERFORMANCE TESTING • LoadTools • Micro Focus Load Runner (Previously HP) • Neotys Neoload • Apache Jmeter • Oracle Application Testing Suite (OATs) • RadView WebLOAD • The Grinder
- 5. PERFORMANCE TESTING • Monitoring •Java • Oracle’s Mission Control • Yourkit Java Profiler • Ej-technologies Jprofiler • Memory Analyzer (MAT) • Thread Dump Analyzer • JVisualVM • Jconsole • Database (Oracle) • Oracle AWR reports • Oracle Database Enterprise Management Console
- 6. PERFORMANCE TESTING • Monitoring,continued • Operating System • Neotys Load Monitors • HP SiteScope • Custom monitoring based on RRDtool (Round Robin Database) and Perl scripts, through Jmeter • Sar/kSar • Iostat, ps, netstat, free, uptime, … • Application Servers • Oracle Weblogic • Oracle Enterprise Management Console • JMX • Jmeter • Jconsole
- 7. PERFORMANCE TESTING • Typeof tests execute: • Data Loading: Generation of sample data • Load Testing: Execute a given number of users for a fixed period of time • Normally executed as a baseline between version and releases • Often used to verify refactored code • Scalability Testing: Determine the maximum load possible within a pre- defined limit • Examples: • Load Average of 3.5 on all servers • Transactions responding in under 2.5 seconds • Stress testing: Locating the breaking point of an application • Utilized to locate the component least capable of handling the stress • Often executed to test a new component or refactored code • Endurance testing: Testing for extended periods • Used to locate issues such as stuck threads or memory growth
- 8. QUALITY ASSURANCE • Functionaltesting • On-premises • Cloud • Worked closely with developers prior to handoff to Functional QA • Primarily responsible for non-UI components • Cache testing • A/B testing backend • Rest • SOAP • Java APIs • Network communications
- 9. QUALITY ASSURANCE • Functional •Created test plans • TestTrack • TestLink • BugDB • Executed and recorded results test plans • TestLink • Mentored junior members
- 10. QUALITY ASSURANCE • Automatedtesting • Designed • Created the test plan outlines • Implemented • Implemented the test plan using multiple tools • Apache Jmeter • JUnit • Reporting • Monitored and created custom reports based on execution. More details can be found under Dev-Ops
- 11. DEV-OPS • Managed DevelopmentLab of 100 Servers, continued • Lab • Built the lab from scratch • Managed operations, and automation of daily tasks • Purchased Hardware • Managed Networking • Handled Cooling and Power distribution • Managed Automation of products, On-premises and Cloud • Installation • Configuration • Sanity Tests
- 12. DEV-OPS • Automated andmanaged the installation, configuration of Oracle products • WebCenter Sites (On Premises) • Jenkins • Shell Scripts • Maven • SVN • Oracle Sites Cloud and Oracle’s CaaS offering (Cloud) • Jenkins • Apache Jmeter • Shell Scripts • GIT
- 13. DEV-OPS • Managed DevelopmentLab of 100 Servers • Linux • VMware ESX • Oracle VM • Oracle Virtualbox • Docker • Solaris • Zones • IBM AIX • LPARs • HP-UX
- 14. DEV-OPS • On-premises • ApplicationServers • Oracle Weblogic • Apache Tomcat • IBM WebSphere • JBoss • Database • Oracle Database • IBM DB2 • MS SQL Server • HSQLDB
- 15. DEV-OPS • On-premises • Messaging •Apache MQ • Kafka • Big Data • Hadoop • Oracle Endeca Studio • Oracle NoSQL • Identity • Oracle Access Manager • Oracle Internet Directory • OpenDS • OpenLDAP
- 16. DEV-OPS • Cloud Platforms •Oracle IaaS • Oracle WebCenter Products • Oracle JCS • Oracle WebCenter Products • Amazon AWS • Fatwire Products • Oracle WebCenter Sites 12c Virtual Machine • Oracle Virtual Machine • Oracle VirtualBox • Reproduced Client environments for Engineering
- 17. DEVELOPMENT • Wrote theOracle WebCenter Sites JumpstartKit • Runs on Unix, Windows, OS X • Written in: • Java • Bash (Unix/OS X) • Batch (Windows) • Based upon • Tomcat • Hsqldb • Provides support for • Oracle WebCenter Sites • Oracle WebCenter Visitors Services • Oracle WebCenter Community-Gadgets
- 18. DEVELOPMENT • Languages • Java •JumpstartKit • API Performance • API Functional tests • Data Creation • Java J2EE • Performance testing WebApp • Perl • Automation • Performance • Batch • WebCenter Sites Installation • Jumpstart Kit • Monitoring
- 19. DEVELOPMENT • Languages, continued •Python • Automation, WebLogic • Bash • Automation • Performance Monitoring • Jumpstart Kit • WebCenter Sites Installation • SQL • Monitoring • WebCenter Sites • PHP • Personal WebSites • C/C++ • Salmon Spawning monitoring software • Various other software
- 20. DOCUMENTATION • Publicly Accessible •WebCenter Sites Installation and configuration guides • WebCeter Sites JCS Installation and configuration guide • WebCeter Sites IaaS Install and configuration guide • WebCenter Sites Visitors Service Configuration guide • WebCenter Sites Administration (Sections) • Exalogic White Paper