Let's achieve fast feedback loops
API Contract tests and localhost assertion tests will help give Engineers and QAs more confidence in the mobile product
SauceCon 2017: Building a Continuous Delivery Pipeline with Testing in MindSauce Labs
Now more than ever, engineering teams of all sizes are under pressure to deliver quality code more frequently. With the DevOps ecosystem growing larger every day, it might seem overwhelming to fully understand how to create an end-to-end solution that allows developers to continually commit new code with confidence, without having to slow down due to rollbacks. Achieving this true Continuous Deployment pipeline is difficult, but not impossible.
Join Neil Manvar, Solutions Architect from Sauce Labs, as he demonstrates a full CD pipeline containing a Pull Request build which will be used to test changes in isolation before code is merged into the master codebase. Using a JS based code tech stack, with AngularJS for the source code, Karma/Jasmine for unit tests and Protractor for functional (Selenium) tests, he will safely push quality code to production leveraging the following tools:
- Jenkins for CI / orchestration
- Github for Source Code Management
- Docker for creating/deploying container running the application
- Sauce Labs for running tests in various browser/OS combinations
By running through all of the various steps involved in deploying code changes safely and automatically to production, Neil will discuss the ways in which the PR Build creates a real time developer feedback and enforcement mechanism, thus eliminating bottlenecks. He will also discuss the implementation strategies, as well as challenges, along with results and culture changes that come with truly embracing DevOps methodologies.
The document outlines 5 stages of digital quality maturity for organizations:
1) Automate testing, reuse test assets, and scale testing across devices and browsers.
2) Shift testing left into development to provide faster feedback and prioritize important tests.
3) Prioritize test executions based on risk and business impact.
4) Provide continuous testing visibility across development, QA, and production for real-time monitoring.
5) Enable remote debugging and support directly from the cloud.
SauceCon 2017: test.allTheThings(): Digital EditionSauce Labs
TEST.ALLTHETHINGS() – DIGITAL EDITION
Asaf Saar – Director of Product Management, Sauce Labs
Testing responsive web sites is a challenging task when it span across Desktop and Mobile browsers. In this session Neil and Asaf will present the strategy and framework around testing responsive web sites using industry standard automation tools like Selenium and Appium against cloud based desktop browsers, real mobile devices, emulators and simulators.
Learnings from Hybrid App Testing Jijesh MohanvodQA
This document discusses testing a hybrid book reader application built with Phonegap, HTML5, and CSS3 for the iPad. It recommends testing the app on actual devices rather than simulators due to differences in user interactions, screen sizes, and orientations. The document outlines areas to focus testing on, including app performance, memory usage, compliance with App Store guidelines, handling of user gestures and touch events, and network connectivity in various conditions. Automated testing is suggested but noted to have limited support for hybrid apps. Testing across multiple devices using a mobile grid is proposed for report consolidation.
Roland van leusden mobile performance testing rtc 2014 v0.6Romania Testing
The document discusses mobile performance testing for an application migration project involving over 400 apps. It notes the challenges of testing across different mobile devices, platforms, and networks. Key factors that affect mobile app performance are identified as the device hardware, mobile network connections, and other apps using resources. The document recommends testing apps on real devices across various mobile networks and network conditions to adequately test performance.
Testing NodeJS, REST APIs and MongoDB with UFTOri Bendet
Today’s applications are becoming more complex. From multi-layers applications, to micro-services to containers, QA & automation engineers are required to test more with less and without compromising the quality of the app.
Join me and Yossi Neeman as we explain the pros & cons of testing at each of the different layers of the application and also share some best practices around Agile Testing. Everything will be demonstrated on a demo application built with the latest technology stack including NodeJS, REST APIs and MongoDB and tested using UFT 12.52.
This document discusses automated performance testing for desktop applications. It outlines challenges like inconsistent loading times and accessing system resources without third-party tools. It then describes a testing process to address these challenges. The process automatically runs a test sequence 1000 times to collect webpage loading times, CPU/memory usage, and disk I/O. This helps predict real-world performance and identify needed improvements. Results are saved to Excel for analysis. In conclusions, automated performance testing requires initial effort but provides very conclusive results to boost an application's performance.
The document discusses quality assurance and testing in software development. It recommends establishing a quality assurance framework that incorporates source code management, continuous integration, code reviews, and continuous inspection tools like SonarQube. This helps automate the development process, reduce technical debt, and prevent bugs by finding and fixing issues early. Tracking key metrics also allows measuring the costs of quality problems versus prevention activities.
SauceCon 2017: Building a Continuous Delivery Pipeline with Testing in MindSauce Labs
Now more than ever, engineering teams of all sizes are under pressure to deliver quality code more frequently. With the DevOps ecosystem growing larger every day, it might seem overwhelming to fully understand how to create an end-to-end solution that allows developers to continually commit new code with confidence, without having to slow down due to rollbacks. Achieving this true Continuous Deployment pipeline is difficult, but not impossible.
Join Neil Manvar, Solutions Architect from Sauce Labs, as he demonstrates a full CD pipeline containing a Pull Request build which will be used to test changes in isolation before code is merged into the master codebase. Using a JS based code tech stack, with AngularJS for the source code, Karma/Jasmine for unit tests and Protractor for functional (Selenium) tests, he will safely push quality code to production leveraging the following tools:
- Jenkins for CI / orchestration
- Github for Source Code Management
- Docker for creating/deploying container running the application
- Sauce Labs for running tests in various browser/OS combinations
By running through all of the various steps involved in deploying code changes safely and automatically to production, Neil will discuss the ways in which the PR Build creates a real time developer feedback and enforcement mechanism, thus eliminating bottlenecks. He will also discuss the implementation strategies, as well as challenges, along with results and culture changes that come with truly embracing DevOps methodologies.
The document outlines 5 stages of digital quality maturity for organizations:
1) Automate testing, reuse test assets, and scale testing across devices and browsers.
2) Shift testing left into development to provide faster feedback and prioritize important tests.
3) Prioritize test executions based on risk and business impact.
4) Provide continuous testing visibility across development, QA, and production for real-time monitoring.
5) Enable remote debugging and support directly from the cloud.
SauceCon 2017: test.allTheThings(): Digital EditionSauce Labs
TEST.ALLTHETHINGS() – DIGITAL EDITION
Asaf Saar – Director of Product Management, Sauce Labs
Testing responsive web sites is a challenging task when it span across Desktop and Mobile browsers. In this session Neil and Asaf will present the strategy and framework around testing responsive web sites using industry standard automation tools like Selenium and Appium against cloud based desktop browsers, real mobile devices, emulators and simulators.
Learnings from Hybrid App Testing Jijesh MohanvodQA
This document discusses testing a hybrid book reader application built with Phonegap, HTML5, and CSS3 for the iPad. It recommends testing the app on actual devices rather than simulators due to differences in user interactions, screen sizes, and orientations. The document outlines areas to focus testing on, including app performance, memory usage, compliance with App Store guidelines, handling of user gestures and touch events, and network connectivity in various conditions. Automated testing is suggested but noted to have limited support for hybrid apps. Testing across multiple devices using a mobile grid is proposed for report consolidation.
Roland van leusden mobile performance testing rtc 2014 v0.6Romania Testing
The document discusses mobile performance testing for an application migration project involving over 400 apps. It notes the challenges of testing across different mobile devices, platforms, and networks. Key factors that affect mobile app performance are identified as the device hardware, mobile network connections, and other apps using resources. The document recommends testing apps on real devices across various mobile networks and network conditions to adequately test performance.
Testing NodeJS, REST APIs and MongoDB with UFTOri Bendet
Today’s applications are becoming more complex. From multi-layers applications, to micro-services to containers, QA & automation engineers are required to test more with less and without compromising the quality of the app.
Join me and Yossi Neeman as we explain the pros & cons of testing at each of the different layers of the application and also share some best practices around Agile Testing. Everything will be demonstrated on a demo application built with the latest technology stack including NodeJS, REST APIs and MongoDB and tested using UFT 12.52.
This document discusses automated performance testing for desktop applications. It outlines challenges like inconsistent loading times and accessing system resources without third-party tools. It then describes a testing process to address these challenges. The process automatically runs a test sequence 1000 times to collect webpage loading times, CPU/memory usage, and disk I/O. This helps predict real-world performance and identify needed improvements. Results are saved to Excel for analysis. In conclusions, automated performance testing requires initial effort but provides very conclusive results to boost an application's performance.
The document discusses quality assurance and testing in software development. It recommends establishing a quality assurance framework that incorporates source code management, continuous integration, code reviews, and continuous inspection tools like SonarQube. This helps automate the development process, reduce technical debt, and prevent bugs by finding and fixing issues early. Tracking key metrics also allows measuring the costs of quality problems versus prevention activities.
This document discusses continuous delivery and testing in software development. It emphasizes building quality in from the start through continuous integration, maintaining production-like environments, and automating deployments. A testing pipeline is recommended to provide increasing levels of testing from units to systems to catch defects early and provide fast feedback. Key principles for continuous delivery include collaborative teamwork, experimentation, and taking ownership for the larger purpose.
In QA organizations today, a tester must have technical know-how, good communication skills, and attention to detail. We know that a tester’s main responsibility is to test the software that developers develop to ensure that the product meets the quality standards expected of today’s applications. But apart from that, it’s difficult to measure what exactly makes a good tester.
QA managers and their team members are constantly under pressure to test faster and more efficiently, and deliver software with fewer defects. The role and importance of QA in today’s R&D teams is evolving from simply finding defects to protecting the corporate image. As a result, your testers have to be more productive and more efficient, and change their mindset to think about quality over quantity. It’s not just about finding bugs; it’s about continuing to measure and improve, and finding the right bugs to make the end-user experience better.
In this lecture I will share with you some of the key performance indicators (KPIs) that we use to measure our own testing efforts: Percentage of high/critical, escaped defects, Time to test, Defect resolution time, Percentage of rejected defects and what we’ve learned from each of them, and how our team improved its efficiency and productivity as a result.
Continuous testing on emulators using the espresso test automation frameworkSauce Labs
Continuous testing for mobile requires that dev teams have an environment that can easily scale. Although real device testing is a must, using emulators early in the development cycle gives teams a cost-effective and quick alternative for test automation in the cloud. This webinar will explore how to implement the Espresso, a widely used framework for testing mobile apps for the Android OS, on emulators. Espresso provides APIs for writing UI tests to simulate user interactions within a single target app.
Developers have embraced Continuous Integration for years and it has proven their value for accelerating software production for Web environments. However, for mobile developers, it’s been a slow road to adopting many of these same practices. In this webinar, Kevin Rohling (Emberlight, Ship.io) and Kristian Meier (Sauce Labs) will cover best practices in implementing a mobile CI system and demonstrate how you can easily build, test and deploy mobile apps.
Awesome Test Automation Made Simple w/ Dave HaeffnerSauce Labs
Learn how to build simple and powerful automated tests that will work on the browsers you care about, cover visual testing and functional regressions, and be configured to run automatically through the use of a continuous integration (CI) server.
Join Sauce Labs’ Automation Specialist and Selenium project contributor, Leo Laskin, as he discusses the value of open source in testing. He will also share his personal experience in moving from manual to automated testing, the lessons he has learned, and the steps he took to build a powerful, international test coding army.
View the recording at https://saucelabs.com/resources/webinars/automation-best-practices
This document discusses extending continuous integration (CI) practices to mobile projects by integrating real devices into the testing process. It summarizes:
1. Plugging real devices into Jenkins allows for automatically deploying builds and performing automated functional testing on each build cycle.
2. A demonstration shows connecting a mobile testing cloud to a Jenkins build to deploy apps and run tests in parallel on real devices.
3. Using real devices for testing provides real feedback that emulators cannot, and helps shift testing left in the development cycle for continuous quality.
This document discusses how wearables will impact mobile app development workflows. It begins by reviewing wearable adoption trends and use cases, such as smartwatches extending smartphones and sensor-based health/fitness apps. It then provides overviews of the Android Wear and Apple Watch development platforms, including their app models and UI elements. The document notes challenges like new hardware constraints but also opportunities like continuous testing on real devices. It concludes by advising developers to leverage capabilities like handoff between devices and consider navigation patterns from the start of wearable app design.
Testistanbul 2016 - Keynote: "The Story of Appium" by Dan CuellarTurkish Testing Board
When I demo’ed what is now called Appium at the Selenium Conference in 2012 I had no idea what I was doing starting an open source project. I knew little about how open source operated and worked behind the scenes. Thanks to the help of a great community and the advice of some seasoned open source contributors, Appium has quickly become the most popular open source mobile automation framework. Along the way, mistakes were made, lessons were learned, and occasionally we got things right. I’ve put together a collection of stories and lessons that I’d like to share with others to help everyone manage, contribute to, and consume open source software projects more effectively.
SauceCon 2017: Testing @ the Speed of ConcurrencySauce Labs
Learn the why, what and how of testing with concurrency. In this talk, Mike will take attendees on an automation journey of in-house machine testing into cloud-based testing. He will show what worked, what didn’t and discuss things to improve as the machines are increasingly doing the work.
7 Keys for Unattended Test AUtomation webinar deckPerfecto Mobile
The document discusses recommendations for building a solid test automation suite. It outlines some common challenges with test automation such as executing tests across platforms and maintaining test scripts over time. It then discusses strategies for defining appropriate digital test coverage, including determining which devices, OS versions, and platforms to test. The presentation recommends starting with a small set of tests and growing automation over time. It also emphasizes debugging tests across different platforms and environments. The last part of the document demonstrates automated testing using Perfecto's tools and discusses maintaining robust automation.
Baris sarialioglu testing on the move, mobile testingRomania Testing
This document summarizes a presentation on mobile testing. It discusses the growth of mobile devices and apps, challenges in mobile testing like varied platforms and devices, and tools for mobile testing like emulators, automation, and beta testing. It also describes a mobile testing contest held at the conference between developers and testers involving questions about mobile history, bugs, and security.
This document discusses mobile platform testing. It lists the major mobile platforms including iOS, Android, Blackberry, Symbian, and Windows. It describes the different types of mobile applications that can be developed - native, web, and hybrid. It also discusses the different aspects of testing mobile applications including compatibility, usability, interfaces, services, security, performance, and more. The document compares emulator/simulator testing to real device testing and lists the pros and cons of each approach. It recommends using emulators for initial development but performing major testing on real devices before commercial release.
testCloud & Crittercism: How to Continuously Ensure Mobile App QualityApteligent
The document discusses how testCloud and Crittercism can be used together to continuously ensure mobile app quality. testCloud provides on-demand software testing services while Crittercism offers mobile application performance management. The webinar agenda covers an introduction to the two companies, the hidden costs of software testing, how to build better apps faster using their joint solution, and a case study of an app's quality assurance process.
Mobile app testing is a completely different beast when compared with web application testing. The challenge of testing the mobile app across multiple mobile devices, each of which might be of different screen sizes and might be using a different operating system and on top of all; mobility related issues (ex. N/W, internet speed, etc) make mobile app testing tough.
5 Keys to Mobile App Testing Success
1. Do mobile app testing on the cloud
2. Choose a combination of Physical Devices & Emulators for Mobile app testing
3. Develop special mobile-centric test cases
4. Automate your mobile app testing
5. Test the performance of your Mobile App
Automated verification is becoming increasingly important. Getting a product from idea to customer as fast as possible in a Continuous Delivery, or a Deployment pipeline is crucial in more businesses than ever before. But how do we get a product through that pipe line, with high quality? Kristian will talk about how automated verification can get you there.
Deeper Root Cause Analysis to App Performance Bottlenecks with Appvance APM I...Clever Moe
Appvance coined the term "Proactive APM" (Application Performance Management) to demonstrate techniques and tools for business managers, engineers, and testers a way to anticipate the end-user experience while the app is under development. It simulates user load on apps once the app launches. This allows for instant diagnoses when there are production issues, by comparing expected transaction times with potential issues. If you are already using New Relic, you’ll want to add Appvance PerformanceCloud to your app development and testing environment.
Testing for Logic App Solutions | Integration MondayBizTalk360
In this Integration Monday session, Mike discussed the challenges and approaches for some of the common testing scenarios when delivering integration solutions with Microsoft Azure.
Android software development is the process by which new applications are created for devices running the Android operating system. Google states that, "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit, while using other languages is also possible.
Zen Test Labs Mobile Application TestingZen Test Labs
For more info visit: www.zentestlabs.com
www.blog.zentestlabs.com
--Mobile Application Testing
--Mobile Configuration Optimization
--Mobile Test Automation
--Mobile Performance Testing
Find out what testing works for your mobile app.
Agile Software Development means we want to maximise progress while minimising waste. Delays cause waste, for instance wasted time and efforts; ineffective work causes waste; poor quality causes waste; and bugs cause waste and delay progress, etc.
Mobile apps and the mobile app ecosystem help determine what sorts of testing will be more valuable for the project. This workshop introduces various key concepts and factors related to testing mobile apps effectively. You will have the opportunity to practice testing mobile apps during the workshop to help reinforce your learning and discovery.
We will cover both interactive and automated testing of mobile apps, and find ways to reduce the Time To Useful Feedback (TTUF) so the project team can make more progress while reducing project waste. We will also cover various ways to gather more and better information about the qualities of our mobile codebase and of the quality of the apps-in-use.
Bring your mobile apps and mobile devices and be prepared to get involved in testing!
More details: http://confengine.com/agile-pune-2014/proposal/861/agile-mobile-testing
Conference: http://pune.agileindia.org/
This document discusses continuous delivery and testing in software development. It emphasizes building quality in from the start through continuous integration, maintaining production-like environments, and automating deployments. A testing pipeline is recommended to provide increasing levels of testing from units to systems to catch defects early and provide fast feedback. Key principles for continuous delivery include collaborative teamwork, experimentation, and taking ownership for the larger purpose.
In QA organizations today, a tester must have technical know-how, good communication skills, and attention to detail. We know that a tester’s main responsibility is to test the software that developers develop to ensure that the product meets the quality standards expected of today’s applications. But apart from that, it’s difficult to measure what exactly makes a good tester.
QA managers and their team members are constantly under pressure to test faster and more efficiently, and deliver software with fewer defects. The role and importance of QA in today’s R&D teams is evolving from simply finding defects to protecting the corporate image. As a result, your testers have to be more productive and more efficient, and change their mindset to think about quality over quantity. It’s not just about finding bugs; it’s about continuing to measure and improve, and finding the right bugs to make the end-user experience better.
In this lecture I will share with you some of the key performance indicators (KPIs) that we use to measure our own testing efforts: Percentage of high/critical, escaped defects, Time to test, Defect resolution time, Percentage of rejected defects and what we’ve learned from each of them, and how our team improved its efficiency and productivity as a result.
Continuous testing on emulators using the espresso test automation frameworkSauce Labs
Continuous testing for mobile requires that dev teams have an environment that can easily scale. Although real device testing is a must, using emulators early in the development cycle gives teams a cost-effective and quick alternative for test automation in the cloud. This webinar will explore how to implement the Espresso, a widely used framework for testing mobile apps for the Android OS, on emulators. Espresso provides APIs for writing UI tests to simulate user interactions within a single target app.
Developers have embraced Continuous Integration for years and it has proven their value for accelerating software production for Web environments. However, for mobile developers, it’s been a slow road to adopting many of these same practices. In this webinar, Kevin Rohling (Emberlight, Ship.io) and Kristian Meier (Sauce Labs) will cover best practices in implementing a mobile CI system and demonstrate how you can easily build, test and deploy mobile apps.
Awesome Test Automation Made Simple w/ Dave HaeffnerSauce Labs
Learn how to build simple and powerful automated tests that will work on the browsers you care about, cover visual testing and functional regressions, and be configured to run automatically through the use of a continuous integration (CI) server.
Join Sauce Labs’ Automation Specialist and Selenium project contributor, Leo Laskin, as he discusses the value of open source in testing. He will also share his personal experience in moving from manual to automated testing, the lessons he has learned, and the steps he took to build a powerful, international test coding army.
View the recording at https://saucelabs.com/resources/webinars/automation-best-practices
This document discusses extending continuous integration (CI) practices to mobile projects by integrating real devices into the testing process. It summarizes:
1. Plugging real devices into Jenkins allows for automatically deploying builds and performing automated functional testing on each build cycle.
2. A demonstration shows connecting a mobile testing cloud to a Jenkins build to deploy apps and run tests in parallel on real devices.
3. Using real devices for testing provides real feedback that emulators cannot, and helps shift testing left in the development cycle for continuous quality.
This document discusses how wearables will impact mobile app development workflows. It begins by reviewing wearable adoption trends and use cases, such as smartwatches extending smartphones and sensor-based health/fitness apps. It then provides overviews of the Android Wear and Apple Watch development platforms, including their app models and UI elements. The document notes challenges like new hardware constraints but also opportunities like continuous testing on real devices. It concludes by advising developers to leverage capabilities like handoff between devices and consider navigation patterns from the start of wearable app design.
Testistanbul 2016 - Keynote: "The Story of Appium" by Dan CuellarTurkish Testing Board
When I demo’ed what is now called Appium at the Selenium Conference in 2012 I had no idea what I was doing starting an open source project. I knew little about how open source operated and worked behind the scenes. Thanks to the help of a great community and the advice of some seasoned open source contributors, Appium has quickly become the most popular open source mobile automation framework. Along the way, mistakes were made, lessons were learned, and occasionally we got things right. I’ve put together a collection of stories and lessons that I’d like to share with others to help everyone manage, contribute to, and consume open source software projects more effectively.
SauceCon 2017: Testing @ the Speed of ConcurrencySauce Labs
Learn the why, what and how of testing with concurrency. In this talk, Mike will take attendees on an automation journey of in-house machine testing into cloud-based testing. He will show what worked, what didn’t and discuss things to improve as the machines are increasingly doing the work.
7 Keys for Unattended Test AUtomation webinar deckPerfecto Mobile
The document discusses recommendations for building a solid test automation suite. It outlines some common challenges with test automation such as executing tests across platforms and maintaining test scripts over time. It then discusses strategies for defining appropriate digital test coverage, including determining which devices, OS versions, and platforms to test. The presentation recommends starting with a small set of tests and growing automation over time. It also emphasizes debugging tests across different platforms and environments. The last part of the document demonstrates automated testing using Perfecto's tools and discusses maintaining robust automation.
Baris sarialioglu testing on the move, mobile testingRomania Testing
This document summarizes a presentation on mobile testing. It discusses the growth of mobile devices and apps, challenges in mobile testing like varied platforms and devices, and tools for mobile testing like emulators, automation, and beta testing. It also describes a mobile testing contest held at the conference between developers and testers involving questions about mobile history, bugs, and security.
This document discusses mobile platform testing. It lists the major mobile platforms including iOS, Android, Blackberry, Symbian, and Windows. It describes the different types of mobile applications that can be developed - native, web, and hybrid. It also discusses the different aspects of testing mobile applications including compatibility, usability, interfaces, services, security, performance, and more. The document compares emulator/simulator testing to real device testing and lists the pros and cons of each approach. It recommends using emulators for initial development but performing major testing on real devices before commercial release.
testCloud & Crittercism: How to Continuously Ensure Mobile App QualityApteligent
The document discusses how testCloud and Crittercism can be used together to continuously ensure mobile app quality. testCloud provides on-demand software testing services while Crittercism offers mobile application performance management. The webinar agenda covers an introduction to the two companies, the hidden costs of software testing, how to build better apps faster using their joint solution, and a case study of an app's quality assurance process.
Mobile app testing is a completely different beast when compared with web application testing. The challenge of testing the mobile app across multiple mobile devices, each of which might be of different screen sizes and might be using a different operating system and on top of all; mobility related issues (ex. N/W, internet speed, etc) make mobile app testing tough.
5 Keys to Mobile App Testing Success
1. Do mobile app testing on the cloud
2. Choose a combination of Physical Devices & Emulators for Mobile app testing
3. Develop special mobile-centric test cases
4. Automate your mobile app testing
5. Test the performance of your Mobile App
Automated verification is becoming increasingly important. Getting a product from idea to customer as fast as possible in a Continuous Delivery, or a Deployment pipeline is crucial in more businesses than ever before. But how do we get a product through that pipe line, with high quality? Kristian will talk about how automated verification can get you there.
Deeper Root Cause Analysis to App Performance Bottlenecks with Appvance APM I...Clever Moe
Appvance coined the term "Proactive APM" (Application Performance Management) to demonstrate techniques and tools for business managers, engineers, and testers a way to anticipate the end-user experience while the app is under development. It simulates user load on apps once the app launches. This allows for instant diagnoses when there are production issues, by comparing expected transaction times with potential issues. If you are already using New Relic, you’ll want to add Appvance PerformanceCloud to your app development and testing environment.
Testing for Logic App Solutions | Integration MondayBizTalk360
In this Integration Monday session, Mike discussed the challenges and approaches for some of the common testing scenarios when delivering integration solutions with Microsoft Azure.
Android software development is the process by which new applications are created for devices running the Android operating system. Google states that, "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit, while using other languages is also possible.
Zen Test Labs Mobile Application TestingZen Test Labs
For more info visit: www.zentestlabs.com
www.blog.zentestlabs.com
--Mobile Application Testing
--Mobile Configuration Optimization
--Mobile Test Automation
--Mobile Performance Testing
Find out what testing works for your mobile app.
Agile Software Development means we want to maximise progress while minimising waste. Delays cause waste, for instance wasted time and efforts; ineffective work causes waste; poor quality causes waste; and bugs cause waste and delay progress, etc.
Mobile apps and the mobile app ecosystem help determine what sorts of testing will be more valuable for the project. This workshop introduces various key concepts and factors related to testing mobile apps effectively. You will have the opportunity to practice testing mobile apps during the workshop to help reinforce your learning and discovery.
We will cover both interactive and automated testing of mobile apps, and find ways to reduce the Time To Useful Feedback (TTUF) so the project team can make more progress while reducing project waste. We will also cover various ways to gather more and better information about the qualities of our mobile codebase and of the quality of the apps-in-use.
Bring your mobile apps and mobile devices and be prepared to get involved in testing!
More details: http://confengine.com/agile-pune-2014/proposal/861/agile-mobile-testing
Conference: http://pune.agileindia.org/
Best Practices for DevOps in Mobile App TestingBitbar
Watch a live presentation at http://offer.bitbar.com/best-practices-for-devops-in-mobile-app-testing
In essence, the core of DevOps methodology aims to speed up the app development delivery and process by getting devs and operation specialists to collaborate throughout the end-to-end app development and deployment process.
Stay tuned and join our upcoming webinars at http://bitbar.com/testing/webinars/
This document discusses mobile application testing. It begins with an introduction to the author's experience in mobile development and quality assurance. It then covers trends in mobile technology and applications. The main sections discuss approaches to testing mobile applications, including requirement analysis, challenges for different mobile platforms, and focus areas for testing like performance, security and compatibility. Automated and manual testing strategies are also outlined.
Mobile users have high expectations for apps, with nearly 80% deleting apps after first use due to bad design, slow loading, or crashes. Testing mobile apps is challenging due to a variety of devices, platforms, and user expectations. An effective mobile testing strategy uses a combination of emulators, physical devices, cloud/mobile testing tools, and both automated and manual testing methods across the application lifecycle to ensure quality, performance, and reliability.
The document discusses mobile user expectations, mobile testing challenges, and strategies for mobile application testing. It provides the following key points:
1) Nearly 80% of mobile users delete apps after the first use due to bad design, slow loading times, or crashes upon installation.
2) Mobile testing faces challenges due to a variety of devices, platforms, and operating systems. Effective strategies include test automation, coverage of multiple devices and platforms, and continuous monitoring of usage data.
3) A mobile application testing strategy should utilize emulators, physical devices, cloud/mobile testing tools, and automation to reduce manual effort and provide comprehensive testing.
Join Perfecto & CloudBees for a presentation on how to drive mobile app quality feedback in every build, on real devices. Watch a demo featuring the CloudBees Jenkins Workflow showcasing automated testing with Perfecto's Continuous Quality Lab.
This presentation represents the Mobile Application testing fundamentals. This presentation will describe How Mobile testing is different from Web testing. It will give you brief information about different mobile application techniques which needs to be taken care while testing Mobile Applications.
This document provides an overview of how to deliver winning mobile apps through continuous quality. It discusses establishing a mobile QA plan based on continuous quality lab (CQL) principles, including functional and non-functional testing, regression testing, and pillars of a CQL. It also outlines mobile QA best practices such as building a proper test plan, establishing a continuous integration workflow, and implementing a continuous automation regression model. The key is leveraging a hybrid cloud approach using real devices to ensure high quality, velocity, and market responsiveness for mobile apps.
1. Having 3.8 years of testing experience which includes Manual , automation,mobile, API testing.
2. Experience in Mobile Testing include Functional Testing & GUI testing.
3 Hands on experience on Agile methodology.
4. Hands on domain experience Telecom, Mobility, retail, real-estate.
5. Basic domain knowledge of healthcare, banking and finance.
6. Hands on experience on SQL, JIRA, HP QC.
Tina Su discusses how Intuit implemented continuous integration and mobile test automation to speed up their mobile development cycle. They created an Intuit Virtual Device Lab (VDL) that gives developers browser-based access to real mobile devices. This allows automated tests to be run simultaneously across many device configurations. Intuit also developed a shared test library and uses Cucumber and Calabash for behavior-driven testing on Android and iOS. Continuous integration with the VDL and test automation reduced Intuit's iteration cycle from days to minutes, improving release quality and developer productivity.
Speed and quality through Mobile Continuous Integration on Real Devices at Intuit. The presentation share about our key considerations for 3rd-party vs custom built solutions and how we created Virtual Device Lab and test automation framework to enable end-2-end Mobile continuous integration that reduce development iteration cycle from Days to Minutes
Tina Su discusses how Intuit implemented continuous integration and mobile test automation to speed up their mobile development cycle. They created an Intuit Virtual Device Lab (VDL) that gives developers browser-based access to real mobile devices. This allows automated tests to be run simultaneously across many device configurations. Intuit also developed a shared test library and uses Cucumber and Calabash for behavior-driven testing on Android and iOS. Continuous integration with the VDL and test automation reduced Intuit's iteration cycle from days to minutes, improving release quality and developer productivity.
Badoo: Cross platform Mobile Test Automation and Continuos DeliveryCodeFest
The document discusses mobile test automation and continuous delivery at Badoo. It describes how Badoo uses a single test automation code base to run tests across two products, three platforms, and both phones and tablets. The tests achieve 68% functional coverage for Badoo in Android and iOS, 76% coverage for HotOrNot, and 52% coverage for mobile web. The document also provides an overview of cross-platform test automation, common tools like Calabash and Appium, and how continuous delivery integrates continuous integration and continuous test automation.
Use Jenkins For Continuous Load Testing And Mobile Test AutomationClever Moe
The document discusses using Jenkins for continuous load testing and mobile test automation. It describes how Jenkins can be used to automate testing across sprints in an agile methodology. Specifically, it outlines how to leverage Jenkins to run functional tests continuously and repurpose those tests for performance and load testing. This helps ensure applications are thoroughly tested before each release.
Rajakumari Thota has over 9 years of experience in software testing of web, mobile, and desktop applications. She has expertise in test automation using Selenium WebDriver, Appium, JMeter, and other tools. Her experience includes test automation framework development, test case writing, defect tracking, test execution and reporting. She is proficient in testing methodologies like test planning, requirement analysis, test design, test execution and defect management.
The document summarizes trends in mobile and web market testing. It discusses fundamentals of test coverage, reviews the desktop and mobile testing landscapes including popular tools, and highlights the rise of progressive web apps. It also explores how headless browsers can help with testing and provides an example of bridging gaps in test automation coverage. Finally, it outlines new capabilities from Perfecto including their one cloud lab covering multiple digital platforms and technologies.
Встреча "QA: в каких направлениях может найти себя тестировщик?"GoIT
19.12.2014 в креативном пространстве "Часопыс" состоялась очередная встреча от проекта GoIT, посвященная "вечному". Наши любимые преподаватели и менторы доносили следующее:
• Виды QA и специфика работы в каждом из этих направлений;
• Необходимые вспомогательные навыки, которыми должен обладать тестировщик;
• Новинки мира QA.
Наши спикеры:
Николай Ковш - QA Engineer в Ciklum, которому успешно удалось перейти в сферу IT из маркетинга. Расскажет о необходимости тестировщикам уметь программировать.
Алла Пенальба - QA Lead в компании invisibleCRM, работала в компании ПИКСУС, 4 года проживала в Бельгии, где работала Mobile QA Engineer.
Марина Шевченко - Mobile QA Engineer в Ciklum. QA с опытом тестирования веб, десктопных и мобильных приложений. Расскажет о специфике тестирования мобильных приложений.
Александр Майданюк - Head of Quality Assurance Solution в компании Ciklum. Занимал должности QA Lead, Manager, QA Consultant и Trainer. Эксперт и судья QA секции чемпионата UA Web Challenge. Соучредитель Киевского клуба тестировщиков QA Club.
STARWest: Use Jenkins For Continuous Load Testing And Mobile Test AutomationClever Moe
Frank Cohen's session from the STARWest (Software Test Automation) conference, October 2014. Building mobile apps and Ajax apps effectively requires a blended approach to test automation. Frank Cohen, CTO/Founder at Appvance, shows how to leverage the best application performance test methodology with test tools to deliver excellent Ajax, iOS and Android apps. Learn how to: * Effectively choose a mobile testing method for Agile shops * Reduce costs by choosing the best tools (Appium, Jenkins, Appvance PerformanceCloud) * Scale-up your mobile testing to thousands of test suites automatically * The mix-and-match mobile testing methodology for just-in-time performance testing
Similar to Mobile Testing Tips - Let's achieve fast feedback loops (20)
1. The document introduces Swift Localhost, a tool for writing localhost UI tests in Swift. It allows setting up a mock localhost server to handle API requests from the app under test.
2. Common problems with traditional end-to-end tests like brittle tests and slow execution are discussed. Localhost UI tests address these by mocking API responses at a faster, isolated integration level.
3. The key aspects of setting up and asserting localhost requests are explained, including routing requests to the localhost server, configuring mock responses, and validating the expected request paths and cURL commands.
With localhost, you can write XCUITest without the constraint of shared dependencies. This talk will showcase how you can setup a localhost XCUITest using 4 simple steps. In addition you can also assert outgoing requests and analytic events fired from the app
Network Interception - Write Swift codes to inspect network requests (even wi...Kenneth Poon
Using a custom URLProtocol class and code injection technique, we can now inspect all requests in an iOS Apps (even when SSL certificate pinning is active). In the hand on demo, I used this technique to inspect all requests in Tinder and Twitter iOS apps
This keynote was presented in https://engineers.sg/video/intercepting-network-requests-ios-dev-scout--2639
PropertyGuru is Hiring. iOS / Android Engineer (Bangkok, Thailand)Kenneth Poon
PropertyGuru is Hiring. Join the band of mobile engineering rockstars at South East Asia's Leading Property Portal, PropertyGuru. We are looking for iOS / Android Engineers to join us and be part of the awesome team responsible for serving 16 million users every month.
This document discusses using Gherkin with XCUITest for iOS automation testing. It begins with an introduction to XCUITest, including recording tests, interacting with elements, and refactoring code. It then demonstrates building a simple test suite for a weather app. Finally, it shows how to implement Gherkin feature files to specify tests in a human-readable format, including steps to set up tests and make assertions. Gherkin allows for acceptance test driven development and collaboration across teams.
A security flaw called Heartbleed was discovered in the OpenSSL encryption software that is widely used on the internet. The flaw allowed hackers to access passwords, credit card numbers, and other sensitive data without leaving a trace for over 2 years. Users are advised to change passwords on websites that may have been affected and to check if websites have patched the vulnerability.
CNY Distribution of Oranges, Uplifting the spirit [@TPCTMC]Kenneth Poon
The document describes an event called "Uplifting the Spirit" held by a Toastmasters club 3 years ago. The event involved distributing oranges and taking pictures during visits, which touched and motivated local residents. The author learned that Toastmasters clubs can be self-organizing and creative when motivated, and their inspired works can further inspire others outside the club. The event from the Toa Payoh Central community club showed the great work of its Toastmasters members.
A high-Speed Communication System is based on the Design of a Bi-NoC Router, ...DharmaBanothu
The Network on Chip (NoC) has emerged as an effective
solution for intercommunication infrastructure within System on
Chip (SoC) designs, overcoming the limitations of traditional
methods that face significant bottlenecks. However, the complexity
of NoC design presents numerous challenges related to
performance metrics such as scalability, latency, power
consumption, and signal integrity. This project addresses the
issues within the router's memory unit and proposes an enhanced
memory structure. To achieve efficient data transfer, FIFO buffers
are implemented in distributed RAM and virtual channels for
FPGA-based NoC. The project introduces advanced FIFO-based
memory units within the NoC router, assessing their performance
in a Bi-directional NoC (Bi-NoC) configuration. The primary
objective is to reduce the router's workload while enhancing the
FIFO internal structure. To further improve data transfer speed,
a Bi-NoC with a self-configurable intercommunication channel is
suggested. Simulation and synthesis results demonstrate
guaranteed throughput, predictable latency, and equitable
network access, showing significant improvement over previous
designs
Properties of Fluids, Fluid Statics, Pressure MeasurementIndrajeet sahu
Properties of Fluids: Density, viscosity, surface tension, compressibility, and specific gravity define fluid behavior.
Fluid Statics: Studies pressure, hydrostatic pressure, buoyancy, and fluid forces on surfaces.
Pressure at a Point: In a static fluid, the pressure at any point is the same in all directions. This is known as Pascal's principle. The pressure increases with depth due to the weight of the fluid above.
Hydrostatic Pressure: The pressure exerted by a fluid at rest due to the force of gravity. It can be calculated using the formula P=ρghP=ρgh, where PP is the pressure, ρρ is the fluid density, gg is the acceleration due to gravity, and hh is the height of the fluid column above the point in question.
Buoyancy: The upward force exerted by a fluid on a submerged or partially submerged object. This force is equal to the weight of the fluid displaced by the object, as described by Archimedes' principle. Buoyancy explains why objects float or sink in fluids.
Fluid Pressure on Surfaces: The analysis of pressure forces on surfaces submerged in fluids. This includes calculating the total force and the center of pressure, which is the point where the resultant pressure force acts.
Pressure Measurement: Manometers, barometers, pressure gauges, and differential pressure transducers measure fluid pressure.
3rd International Conference on Artificial Intelligence Advances (AIAD 2024)GiselleginaGloria
3rd International Conference on Artificial Intelligence Advances (AIAD 2024) will act as a major forum for the presentation of innovative ideas, approaches, developments, and research projects in the area advanced Artificial Intelligence. It will also serve to facilitate the exchange of information between researchers and industry professionals to discuss the latest issues and advancement in the research area. Core areas of AI and advanced multi-disciplinary and its applications will be covered during the conferences.
Determination of Equivalent Circuit parameters and performance characteristic...pvpriya2
Includes the testing of induction motor to draw the circle diagram of induction motor with step wise procedure and calculation for the same. Also explains the working and application of Induction generator
ELS: 2.4.1 POWER ELECTRONICS Course objectives: This course will enable stude...Kuvempu University
Introduction - Applications of Power Electronics, Power Semiconductor Devices, Control Characteristics of Power Devices, types of Power Electronic Circuits. Power Transistors: Power BJTs: Steady state characteristics. Power MOSFETs: device operation, switching characteristics, IGBTs: device operation, output and transfer characteristics.
Thyristors - Introduction, Principle of Operation of SCR, Static Anode- Cathode Characteristics of SCR, Two transistor model of SCR, Gate Characteristics of SCR, Turn-ON Methods, Turn-OFF Mechanism, Turn-OFF Methods: Natural and Forced Commutation – Class A and Class B types, Gate Trigger Circuit: Resistance Firing Circuit, Resistance capacitance firing circuit.
Accident detection system project report.pdfKamal Acharya
The Rapid growth of technology and infrastructure has made our lives easier. The
advent of technology has also increased the traffic hazards and the road accidents take place
frequently which causes huge loss of life and property because of the poor emergency facilities.
Many lives could have been saved if emergency service could get accident information and
reach in time. Our project will provide an optimum solution to this draw back. A piezo electric
sensor can be used as a crash or rollover detector of the vehicle during and after a crash. With
signals from a piezo electric sensor, a severe accident can be recognized. According to this
project when a vehicle meets with an accident immediately piezo electric sensor will detect the
signal or if a car rolls over. Then with the help of GSM module and GPS module, the location
will be sent to the emergency contact. Then after conforming the location necessary action will
be taken. If the person meets with a small accident or if there is no serious threat to anyone’s
life, then the alert message can be terminated by the driver by a switch provided in order to
avoid wasting the valuable time of the medical rescue team.
Sri Guru Hargobind Ji - Bandi Chor Guru.pdfBalvir Singh
Sri Guru Hargobind Ji (19 June 1595 - 3 March 1644) is revered as the Sixth Nanak.
• On 25 May 1606 Guru Arjan nominated his son Sri Hargobind Ji as his successor. Shortly
afterwards, Guru Arjan was arrested, tortured and killed by order of the Mogul Emperor
Jahangir.
• Guru Hargobind's succession ceremony took place on 24 June 1606. He was barely
eleven years old when he became 6th Guru.
• As ordered by Guru Arjan Dev Ji, he put on two swords, one indicated his spiritual
authority (PIRI) and the other, his temporal authority (MIRI). He thus for the first time
initiated military tradition in the Sikh faith to resist religious persecution, protect
people’s freedom and independence to practice religion by choice. He transformed
Sikhs to be Saints and Soldier.
• He had a long tenure as Guru, lasting 37 years, 9 months and 3 days
Digital Twins Computer Networking Paper Presentation.pptxaryanpankaj78
A Digital Twin in computer networking is a virtual representation of a physical network, used to simulate, analyze, and optimize network performance and reliability. It leverages real-time data to enhance network management, predict issues, and improve decision-making processes.
This study Examines the Effectiveness of Talent Procurement through the Imple...DharmaBanothu
In the world with high technology and fast
forward mindset recruiters are walking/showing interest
towards E-Recruitment. Present most of the HRs of
many companies are choosing E-Recruitment as the best
choice for recruitment. E-Recruitment is being done
through many online platforms like Linkedin, Naukri,
Instagram , Facebook etc. Now with high technology E-
Recruitment has gone through next level by using
Artificial Intelligence too.
Key Words : Talent Management, Talent Acquisition , E-
Recruitment , Artificial Intelligence Introduction
Effectiveness of Talent Acquisition through E-
Recruitment in this topic we will discuss about 4important
and interlinked topics which are
Impartiality as per ISO /IEC 17025:2017 StandardMuhammadJazib15
This document provides basic guidelines for imparitallity requirement of ISO 17025. It defines in detial how it is met and wiudhwdih jdhsjdhwudjwkdbjwkdddddddddddkkkkkkkkkkkkkkkkkkkkkkkwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwioiiiiiiiiiiiii uwwwwwwwwwwwwwwwwhe wiqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq gbbbbbbbbbbbbb owdjjjjjjjjjjjjjjjjjjjj widhi owqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq uwdhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhwqiiiiiiiiiiiiiiiiiiiiiiiiiiiiw0pooooojjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj whhhhhhhhhhh wheeeeeeee wihieiiiiii wihe
e qqqqqqqqqqeuwiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiqw dddddddddd cccccccccccccccv s w c r
cdf cb bicbsad ishd d qwkbdwiur e wetwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww w
dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffw
uuuuhhhhhhhhhhhhhhhhhhhhhhhhe qiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii iqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc ccccccccccccccccccccccccccccccccccc bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbu uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuum
m
m mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm m i
g i dijsd sjdnsjd ndjajsdnnsa adjdnawddddddddddddd uw
Blood finder application project report (1).pdfKamal Acharya
Blood Finder is an emergency time app where a user can search for the blood banks as
well as the registered blood donors around Mumbai. This application also provide an
opportunity for the user of this application to become a registered donor for this user have
to enroll for the donor request from the application itself. If the admin wish to make user
a registered donor, with some of the formalities with the organization it can be done.
Specialization of this application is that the user will not have to register on sign-in for
searching the blood banks and blood donors it can be just done by installing the
application to the mobile.
The purpose of making this application is to save the user’s time for searching blood of
needed blood group during the time of the emergency.
This is an android application developed in Java and XML with the connectivity of
SQLite database. This application will provide most of basic functionality required for an
emergency time application. All the details of Blood banks and Blood donors are stored
in the database i.e. SQLite.
This application allowed the user to get all the information regarding blood banks and
blood donors such as Name, Number, Address, Blood Group, rather than searching it on
the different websites and wasting the precious time. This application is effective and
user friendly.
3. Agenda
• Theme - Focusing On Feedback
• Mobile App Testing Strategies
4. Focusing On Feedback
• Long feedback loops in typical mobile testing
• How mobile bugs generally occur
• API Breakage
• Mobile Client User Interaction Bug
• Mobile Client Logic Bug
6. Mobile App Testing Strategies
Solution - Contract Tests
• Series of cURL network calls that simulate mobile app request behaviour
• Assert that API Schema are according to expected.
• Assertions are based on what the mobile apps are using. Owned by the mobile team
• Create a CI Job that can be triggered against any environment. Eg QA, Production, Sandbox
• Automate process where Mobile Contract Tests are executed after backend code deployment
• Lowest hanging fruit if you have no tests.
7. Mobile App Testing Strategies
How should I
respond?
Solution - Localhost Response Mock Tests
• Given that the API returns a particular response, assert the behaviour of the app
• Mobile Testing decouples itself from external environment.
• Have total control to mock any response
8. Mobile App Testing Strategies
What
request should I
send?
Solution - Localhost Request Tests
• For a given use case, assert all outgoing requests
• Tests may also assert outgoing requests performed by 3rd party SDKs
9. • End-to-end tests are still required but they can be slow and
brittle. Decide on a good mix and prioritisation of end-to-end
and localhost tests
• Encouraged to use a combination of Cross platform and
native specific testing tools. Eg (Appium, XCUITest,
Espresso)
• All Mobile codes and tests should be located at the same
commit point. Use pull requests to drive test case
developments. Ideally, pull requests should contain native
and test codes together
Mobile App Testing Strategies
10. • Engineers and QAs should regularly review each others’
testing strategy. Code and testing complexity should not
differ too much
• Mobile Client Logic Bug
• Please unit test your code. 100% coverage if possible
Mobile App Testing Strategies
11. Extra Links (iOS Related)
https://github.com/depoon/WeatherCucumber
https://medium.com/@kennethpoon/ios-xcuitest-
cucumberish-5ea6121897fa
iOS XCUITest - Cucumberish
BDD iOS UI Test