Downloaded 20 times
![Executing Appium Tests from Jenkins #Start appium server appium_log=appium.log appium_cmd="node <REPLACE_WITH_APPIUM_PATH>/appium/lib/server/main.js" echo "[INFO] Appium command: $appium_cmd" $appium_cmd &> $appium_log& appium_pid=$! #check if appium was successfully started sleep 1 appium_pid_start=`ps -p $appium_pid | grep node | awk '{ print $1 }'` if [ -z $appium_pid_start ] ; then echo "[ERROR] Appium failed to start! Port $appiumport may be already in use. " exit 1 fi echo "[INFO] Appium started with pid: $appium_pid . Logging to: ${appium_log}" # be sure to kill appium on script stop trap "kill $appium_pid" SIGINT SIGTERM EXIT A B C](https://image.slidesharecdn.com/ci-deploy-test-beginningtoend2014-141024110541-conversion-gate02/75/Continuous-Integration-Deploy-Test-From-Beginning-To-End-2014-18-2048.jpg)
Uploaded byClever Moe
Continuous Integration, Deploy, Test From Beginning To End 2014
Frank Cohen provides insights on continuous integration and deployment strategies for developers and testers, emphasizing the importance of aligning agile methodologies with robust testing practices using tools like Jenkins. The document discusses various testing methodologies, including performance and functional testing, and outlines steps for creating successful continuous integration plans. It concludes by inviting readers to reach out for assistance in implementing these strategies and highlights the benefits of effective testing in reducing business risk.
Continuous Integration, Deploy, Test From Beginning To End 2014
- 1. Continuous Integration, Deployment,Test From Beginning To End October 22, 2014 www.appvance.com Frank Cohen, CTO/Founder at Appvance, teaches developers and testers how to become more closely aligned with easily deployable and configurable tools such as Jenkins CI and performance testing platforms. Learn how to: * Merge Agile SDLC and Performance Testing * Speed-up test operations by configuring Jenkins for automatic build, deploy, and tests * Instantly identify functional and performance issues using Jenkins as a performance dashboard * Use effective choices in Jenkins deployment – in the cloud, hosted, or in your datacenter ! fcohen@appvance.com
- 2. Continuous Integration, Deployment,Test From Beginning To End October 22, 2014 Frank Cohen, fcohen@appvance.com, (408) 364-5508
- 3. What We WillTalk About •Agile Methodology Expects Build, Deploy, Test Automation •A Continuous Integration Strategy •Ajax and Mobile Testing Methodology •Repurposing for Functional and Performance Testing •Becoming A CI Architect
- 5. Agile Methodology ina Process 7-day Sprint Highest Priority Backlog of Changes, Improvements • App does not run on iOS • Rendering problems • UX fails at 45 users • Overnight reports needed Funding and Feedback Sprint Review Acceptance ✓ Unit Tests Pass ✓ Functional Tests Pass ✓ Usability Tests Pass ✓ Perf Under Load Pass ✓ Stress Tests Completed ✓ Production Monitor In Place Daily Work Release
- 6.
- 7. Why Do ContinuousIntegration? •It’s free and easy •Your Test Suites Take Longer Than “Overnight” To Run •High Risk App Launch •Software build/deploy/test plan of record (How do I?) •Easy to go from functional to performance testing •Keeps you productive, while long projects build/deploy/test
- 8. Why Avoid ContinuousIntegration •You Work In A Small Shop •Stakeholders Unable To Participate •No One To Manage Projects on Jenkins •One-shot project (build, launch, forget) •Deploy/Test Requires Human Intervention •Low Risk App Launches
- 9. Continuous DevOps •ContinuousIntegration • Dashboard To Testing •Continuous Deploy • Automatic app deployment •Continuous Testing • Regression on Commit • Repurpose for Load Tests Test CI Runtime Repository Tickets Monitor
- 10. How Do IGet Jenkins? •Run on Cloudbees (Fully Managed) •Run on AWS, IBM Softlayer (Self Managed) •Download and Run Internally (Self Managed) •Then, Plug-in Test As A Service Platform
- 12. What Is TheMeasurement of Success •Functional Testing Defines End User Experience Success • Browser Compatibility, UX Latency, Configuration/Integration Problems •Performance Testing Identifies Business Risk To Launch • How Many People Are We Ready To Serve At Any Given Time •Stress Testing Identifies The Experience As The App Fails • International Bank App Showing Other User Details Testing Measures Business Risk Sprint Review Acceptance ✓ Unit Tests Pass ✓ Functional Tests Pass ✓ Usability Tests Pass ✓ Perf Under Load Pass ✓ Stress Tests Completed ✓ Production Monitor In Place
- 13. A Testing Strategyfor You •Working With Today’s Apps, Pages, Tools • Serverless Architecture means pages that have state, workflow, communication • Real time analytics and immediate fix - at the same time • Extending tools to support new technology •Beginning To End Testing •Scaling Up Your Team’s Efforts • Higher Productivity • Test Management •Cost Effectiveness and Immediate Support
- 14. How Do IGet App Testing? •Ajax App Testing • Sahi, Selenium, WebDriver • Unit Testing more difficult, easier to maintain • JMeter does not work in Ajax •Mobile App Testing • Appium for iOS, Android • Unit Testing of REST and SOAP services using soapUI, HAR, JMeter • Others, very limited support and no repurposing to performance tests
- 15. Continuous DevOps InPractice Data Center Switches Testing svn, GIT TestNode 4 TestNode 5 APC Controller Oracle 1 Test Scenario 1 DPL, Logging
- 16. Scale Up ToMultiple Teams Data Center Switches Testing svn, GIT TestNode 4 TestNode 5 APC Controller Oracle 1 Test Scenario 1 DPL, Logging TestNode 2 TestNode 3 APC Controller 2 Test Scenario 2 TestNode 1 Router Team Testing
- 17. Connect To ContinuousIntegration, Deployment Data Center Switches Testing svn, GIT TestNode 4 TestNode 5 APC Controller Oracle 1 Test Scenario 1 DPL, Logging TestNode 2 TestNode 3 APC Controller 2 Test Scenario 2 TestNode 1
- 18. Executing Appium Testsfrom Jenkins #Start appium server appium_log=appium.log appium_cmd="node <REPLACE_WITH_APPIUM_PATH>/appium/lib/server/main.js" echo "[INFO] Appium command: $appium_cmd" $appium_cmd &> $appium_log& appium_pid=$! #check if appium was successfully started sleep 1 appium_pid_start=`ps -p $appium_pid | grep node | awk '{ print $1 }'` if [ -z $appium_pid_start ] ; then echo "[ERROR] Appium failed to start! Port $appiumport may be already in use. " exit 1 fi echo "[INFO] Appium started with pid: $appium_pid . Logging to: ${appium_log}" # be sure to kill appium on script stop trap "kill $appium_pid" SIGINT SIGTERM EXIT A B C
- 22. Why Treat Functional/PerformanceTests Differently? •Repurposing Benefits • Single Test Scripts for All Testing • Pivot Back and Forth Rapidly • Natural for Continuous Integration and Automation •Performance Test • Run at Low, Medium, High Virtual User Levels • Scalability Index Report Answers Risk Questions
- 23.
- 24. Correlation To BackEnd Load
- 25.
- 26. Strategy for MobileTest Runtime •Run Test in Emulators (Mac and Android) 85% •Run Test in Real Devices 10% •Run Test with Real People 5% We’re going to run the test between 1-2 pm, get as many real people on it then
- 27. Become A CIArchitect •Draw A Line From Business Risk To Your Integration Plan
- 28. How To GetStarted •Attend Scrum Meetings, Ask A Few Questions •Ask The Business Manager for an App About Risks •Ask the Developers Where The Test Coverage Is Thin •Choose An Appropriate Test Script Authoring Tool •Write or Record A Test •Commit The Test to svn, CVS, other repository •Plug-in To CI and Maintain
- 29. Contents of aCI Plan •Identify the Parts • Beginning-To-End of User Experience, including Data • Units of App Function •Success/Fail Criteria • 50,000 User Transactions per 10 Minutes with less than 1% Errors • Functional Test on IE 8, Firefox 16, iOS 5 •User Archetypes and Workflow •Performance Under Load and Stress
- 30. Need A CITest Plan Template? Ask sales@appvance.com, it’s free
- 31. What We CoveredToday •Agile Methodology Expects Build, Deploy, Test Automation •A Continuous Integration Strategy •Ajax and Mobile Testing Methodology •Repurposing for Functional and Performance Testing •Becoming A CI Architect
- 32. Are You Ready? •When You Build Modern Apps And Wonder “How Risky Is That App Launch Going To Be?” •Call Us At (855) 254-1164 Or Email Us Sales@Appvance.Com And We Will Show You