BbWorld 2012 AppDynamics Presentation

•

2 likes•1,390 views

Georgetown University has improved its testing practices for its Blackboard learning management system over time. It moved from insufficient testing of Blackboard 5.0 to implementing comprehensive manual functional testing for Blackboard 6.x and load testing with JMeter. For Blackboard 9.1, load and functional testing became more difficult due to increased client-side technologies. Georgetown now focuses on monitoring production use with application performance management to better understand real user experiences rather than relying solely on testing.

Technology

WHY I DON'T LOAD
TEST…
Peter Farkas
Associate Director, Enterprise Scholarly Systems
Georgetown University

GETTING VISIBILITY
INTO
BLACKBOARD'S
"BLACK BOX" AND
LEARNING TO TEST
IN PRODUCTION

About Georgetown

• Located in Washington, DC
• Founded in 1789
• Comprised of 8 schools
• 3 campuses and several additional locations
• 2,100 full-time and part-time faculty
• 15,000+ undergraduate and post-graduate students

3

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Bb 5.0
• Insufficient QA
• Insufficient Functional Testing
• MAJOR NIGHTMARE

4

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Bb 6.x
• Comprehensive manual functional testing process implemented
• JMeter load testing
• CRITICAL bottlenecks found!

5

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Bb 8.x
• Continued JMeter testing
• Bb ICM engaged for Oracle RAC
• Brought Grinder test framework
• Attempts to license Grinder from Bb were not successful
• Attempts to automate functional testing
• Lots of work, limited reward
• Misunderstanding of some important use cases

6

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Bb 9.1
• Load testing and automated functional testing even harder
• Heavy use of client-side technologies
• Faculty reports of slowness were difficult to verify (but correct!)

7

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Limitations of testing
• Requires significant investment in time and expertise
• It is easy to draw the wrong conclusions
• Based on our (mis)understanding of user behavior
• Valid for conditions at time test is conducted
• End user experience depends on client-side technologies

8

Evolution of testing @ Georgetown

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Due Diligence Testing!
• Closely monitor production use! This is what really matters!
• APM allows us to do this!

9

Blackboard via AppDynamics now… live?

AppDynamics

Next Steps

Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current

• Upgrade to take advantage of End User Experience
Monitoring
• Move to a relative method of categorizing requests
• Some requests are slow and always will be…
• Pass persistent user reference to AppDynamics
• Search for requests from Prof. X.

39

We value your feedback!
Please fill out a session evaluation.

41

The document discusses WebSphere testing at IBM. It provides an overview of IBM's: - Extensive testing resources including over 200 engineers and thousands of systems. - Daily regression testing of over 1.7 million tests. - Transition from waterfall to agile development which reduced cycle times and resources needed for testing. - Use of cloud resources to speed up test deployment and automation. - Focus on creating meaningful regressions through techniques like integration acceptance tests run continuously on each build.

Performance Testing In Software Testing | quality professionals

QualityProfessionals2

Casestudy: Continuously Delivering Fitness with Redgate DLM

Red Gate Software

Presentation at SQL in The city 2016 by Jon Forster and James Smith. Fitness First is the largest privately owned health club group in the world. It consists of more than 360 Fitness First clubs worldwide reaching just over 927,000 members in 16 countries. DevOpsGuys have transformed the way that Fitness First deliver changes to their core club management systems, through Continuous Delivery and DevOps principles, and building quality into the process was a primary concern. In this talk, DevOpsGuys will illustrate how the Redgate DLM toolset has been successfully deployed to transform integration and regression testing of fast flowing changes across 16 countries, increasing visibility and creating a robust process.

Load and performance testing

Qualitest

QualiTest provides load and performance testing services to determine a system's behavior under normal and peak load conditions. Their testing process identifies maximum operating capacity and elements that cause degradation. They ensure applications can handle predicted traffic volumes. QualiTest uses various load testing tools and methodologies to simulate real-world usage and stress test systems. Their testing delivers reports on defects, tool evaluations, and ongoing support for quality improvement.

Getting start with Performance Testing

Yogesh Deshmukh

The document discusses performance testing. It defines performance testing as determining how fast and stable a system is. It outlines why performance testing is important to identify problems early, prevent revenue and credibility loss from poor performance, and ensure systems meet expectations. It also discusses various performance testing terms, metrics, processes, limitations of manual testing, and benefits of automation using tools like LoadRunner and JMeter.

Using Acceptance Tests to Validate Accessibility Requirements in RIA

analuizadias

The document discusses using acceptance tests to validate accessibility requirements in rich internet applications (RIAs). It proposes that acceptance tests can help evaluate accessibility in RIAs as they are developed using a continuous integration approach. Preliminary results found that acceptance tests identified more accessibility issues than traditional validation tools. Advantages include evaluating dynamic content and ARIA requirements, while limitations include high cost of authoring test cases. Next steps involve implementing new test scenarios and further evaluating ARIA compliance.

Implementing a Performance Centre of Excellence

Richard Bishop

An old presentation, but just as relevant today as it was when I presented this at the British Computer Society in 2006. This presentation showed how building a performance test team using a shared knowledge base with shared code libraries and best practice techniques made the performance test team a valuable part of the project team at a large UK bank. Making test results and reports accessible to the entire project team and acting as a intermediary between the development teams and business users made the test team vital to the success of many projects at HBoS.

Bugday bkk-2014 nitisak-auto_perf

Nitisak Mooltreesri

Nitisak Mooltreesri from DST Worldwide Services spoke about automated load testing for continuous delivery. He discussed how load testing is important to find bugs under high user loads. His company performs daily automated performance tests using simulation approaches to test incomplete systems cheaply and reliably. This helps reduce performance issues by providing early feedback and catching problems before deployment.

This document outlines Broadcom's experience enhancing its chip verification flow with Nextop's BugScope assertion synthesis technology. Broadcom was finding bugs late in the verification process using its traditional methodology. BugScope helped address this by automatically generating assertions that find corner case bugs missed previously and improve debug and coverage closure. Using BugScope, Broadcom found bugs in most blocks during property review and noticed improved functional coverage and visibility. While seeing benefits, Broadcom also provides ideas to further improve the tool, such as supporting cross-module properties and a GUI for classification. Overall, Broadcom finds assertion synthesis a natural addition that improves block verification quality and observability in chip testing.

Continuous Delivery without Test Automation @STPCon, San Diego

Maaret Pyhäjärvi

Test Execution

Rajathi-QA

This document provides an overview of test execution, including its purpose, entry and exit criteria, cycles, and methodologies. Test execution involves running test cases against software to find defects and assess quality. Key activities include verifying the test environment, selecting test cases, executing them, and logging any defects found. Test cycles are run as planned, with additional cycles as more defects are uncovered. Retesting and regression testing help ensure defects are closed without impacting previous functionality. Testing ends when criteria like completing test cases, reaching an acceptable defect rate, and schedule constraints are met.

UX Week 2007: CNN.com Relaunch Case Study

Adaptive Path

The document summarizes CNN's relaunch of their website CNN.com in 2007. It describes the multi-step process they took which included discovery research, defining design principles, creating prototypes, gathering user feedback, implementing the new site, and conducting a public beta test. The relaunch process spanned over a year and involved cross-functional teams working to modernize the site and improve the user experience based on new technologies and changing user behaviors.

In Sync Running Apps On Oracle

InSync Conference

This document discusses Oracle's innovations for testing applications on Oracle databases. It introduces Oracle's Application Quality Management Suite which includes tools for testing application changes, infrastructure changes, and secure test data management. It focuses on Real Application Testing which allows testing database tier changes through workload capture and replay. It provides enhancements to SQL Performance Analyzer and discusses how Real Application Testing can be used to test database upgrades and other changes in a cost effective manner.

Vaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Agile Testing Leadership Lessons for the Test & QA Professionals Silicon India Software Testing Conference - SOFTEC - 2 July 2011 Bangalore Presentation from Speaker: Vaidyanathan Ramalingam, Director Engineering (Test), Huawei Technologies R&D, Bangalore Coverage: 1) Waterfall Testing Vs Agile Testing 2) Testing Checklist - 5W & 2H 3) Trade Off Economics in Testing 4) Software Testing Eco System 5) RCA (Root Cause Analysis) Cotact: rvaidya67@hotmail.com Linked-In: Vaidyanathan Ramalingam

Vaidyanathan Ramalingam_Iterative Testing_SOFTEC_2_July2011_Silicon India Con...

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included: 1) Comparing waterfall vs agile testing approaches in areas like test requirements, strategy, team structure and test automation. 2) Outlining a testing checklist using the "5 Ws and 2 Hs" (Why, What, When, Who, Where, How, How Long) to plan testing. 3) Discussing trade-off considerations around testing scope, resources and quality goals. 4) Describing the software testing ecosystem involving various stakeholders. 5) Emphasizing the importance of root cause analysis (RCA) at different

Vaidyanathan Ramalingam Agile Testing Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Rca In Agile Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Software Testing Eco System Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam_Agile QA_SOFTEC_2_July2011_Silicon India Conf_Bangalore

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included: 1) Comparing waterfall vs agile testing approaches. Agile testing focuses on incremental requirements, test strategies, and collaborative teams. 2) Using the "5 Ws and 2 Hs" (why, what, when, where, who, how, how long) as a testing checklist. 3) Discussing tradeoffs around test scope, resources, defects, and timelines that require risk mitigation. 4) Describing a software testing ecosystem with various stakeholders involved in development, management, testing, and more. 5) Emp

Vaidyanathan Ramalingam Agile Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam_Sprint Testing_SOFTEC_2_July2011_Silicon India Conf_B...

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

This document discusses key lessons for leadership in test and QA professions. It covers: 1) Differences between waterfall and agile testing approaches. 2) Using a testing checklist of 5 Ws and 2 Hs. 3) Tradeoffs involved in testing economics and scope. 4) The software testing ecosystem involving various stakeholders. The overall message is on adapting testing strategies to agile environments while maintaining quality.

Vaidyanathan Ramalingam_Testing in Agile_SOFTEC_2_July2011_Silicon India Conf...

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included: 1) Comparing waterfall vs agile testing approaches. Agile testing focuses on incremental requirements, test strategies, and collaborative teams. 2) Using the "5 Ws and 2 Hs" (why, what, when, where, who, how, how long) as a testing checklist. 3) Discussing tradeoffs around test scope, resources, defects, and timelines that require risk mitigation. 4) Describing a software testing ecosystem with various stakeholders involved in development, management, testing, and more. 5) Emp

Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Silicon India Testing Conference 2 July2011 Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Rca In Testing Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

Vaidyanathan Ramalingam Testing Checklist Conference Speech

Skills2Talent (Integrated Talent Management and L&D Software - Hire to ROI)

An Introduction to Performance Testing

SWAAM Tech

The document discusses performance testing, including its goals, importance, types, prerequisites, management approaches, testing cycle, activities, common issues, typical fixes, challenges, and best practices. The key types of performance testing are load, stress, soak/endurance, volume/spike, scalability, and configuration testing. Performance testing aims to assess production readiness, compare platforms/configurations, evaluate against criteria, and discover poor performance. It is important for meeting user expectations and avoiding lost revenue.

Presentation of the OECD Artificial Intelligence Review of Germany

innovationoecd

Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack

shyamraj55

Zilliz

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...

Jeffrey Haguewood

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on integration of Salesforce with Bonterra Impact Management. Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

GenAI Pilot Implementation in the organizations

kumardaparthi1024

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

akankshawande

Skybuffer SAM4U tool for SAP license adoption

Tatiana Kojar

Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool. SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.

Energy Efficient Video Encoding for Cloud and Edge Computing Instances

Alpen-Adria-Universität

Digital Marketing Trends in 2024 | Guide for Staying Ahead

Wask

https://www.wask.co/ebooks/digital-marketing-trends-in-2024 Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.

Recently uploaded (20)

Presentation of the OECD Artificial Intelligence Review of Germany

Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack

Ocean lotus Threat actors project by John Sitima 2024 (1).pptx

Cosa hanno in comune un mattoncino Lego e la backdoor XZ?

HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU

Columbus Data & Analytics Wednesdays - June 2024

Introduction of Cybersecurity with OSS at Code Europe 2024

OpenID AuthZEN Interop Read Out - Authorization

GraphRAG for Life Science to increase LLM accuracy

National Security Agency - NSA mobile device best practices

UI5 Controls simplified - UI5con2024 presentation

Generating privacy-protected synthetic data using Secludy and Milvus

20240609 QFM020 Irresponsible AI Reading List May 2024

Building Production Ready Search Pipelines with Spark and Milvus

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...

GenAI Pilot Implementation in the organizations

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

Skybuffer SAM4U tool for SAP license adoption

Energy Efficient Video Encoding for Cloud and Edge Computing Instances

Digital Marketing Trends in 2024 | Guide for Staying Ahead

BbWorld 2012 AppDynamics Presentation

1. WHY I DON'T LOAD TEST… Peter Farkas Associate Director, Enterprise Scholarly Systems Georgetown University

2. GETTING VISIBILITY INTO BLACKBOARD'S "BLACK BOX" AND LEARNING TO TEST IN PRODUCTION

3. About Georgetown • Located in Washington, DC • Founded in 1789 • Comprised of 8 schools • 3 campuses and several additional locations • 2,100 full-time and part-time faculty • 15,000+ undergraduate and post-graduate students 3

4. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Bb 5.0 • Insufficient QA • Insufficient Functional Testing • MAJOR NIGHTMARE 4

5. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Bb 6.x • Comprehensive manual functional testing process implemented • JMeter load testing • CRITICAL bottlenecks found! 5

6. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Bb 8.x • Continued JMeter testing • Bb ICM engaged for Oracle RAC • Brought Grinder test framework • Attempts to license Grinder from Bb were not successful • Attempts to automate functional testing • Lots of work, limited reward • Misunderstanding of some important use cases 6

7. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Bb 9.1 • Load testing and automated functional testing even harder • Heavy use of client-side technologies • Faculty reports of slowness were difficult to verify (but correct!) 7

8. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Limitations of testing • Requires significant investment in time and expertise • It is easy to draw the wrong conclusions • Based on our (mis)understanding of user behavior • Valid for conditions at time test is conducted • End user experience depends on client-side technologies 8

9. Evolution of testing @ Georgetown Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Due Diligence Testing! • Closely monitor production use! This is what really matters! • APM allows us to do this! 9

10. Demo 10

11. Blackboard via AppDynamics Then…

12.

13.

14. Blackboard via AppDynamics now… live? AppDynamics

15.

16.

17.

18.

19.

20.

21. Slow Assignment Upload Example

22. Slow Assignment Uploads

23.

24.

25.

26.

27.

28.

29.

30.

31. Slow DB Instance

32.

33.

34.

35.

36. Xythos DB Tuning

37.

38.

39. Next Steps Bb 5.0 Bb 6.x Bb 8.x Bb 9.1 Current • Upgrade to take advantage of End User Experience Monitoring • Move to a relative method of categorizing requests • Some requests are slow and always will be… • Pass persistent user reference to AppDynamics • Search for requests from Prof. X. 39

40. Questions?

41. We value your feedback! Please fill out a session evaluation. 41

BbWorld 2012 AppDynamics Presentation

Recommended

Recommended

More Related Content

Similar to BbWorld 2012 AppDynamics Presentation

Similar to BbWorld 2012 AppDynamics Presentation (20)

Recently uploaded

Recently uploaded (20)

BbWorld 2012 AppDynamics Presentation