The document discusses the current and missing parts of Samsung's open source QA process. It covers their use of compile-time testing, unit testing, and static analysis currently. Areas missing include runtime testing, graphical unit tests, code coverage, and pre-push continuous integration. The presentation proposes steps like making tests mandatory for new APIs, increasing test coverage 5-10% per release, improving graphical testing, and adding pre-push continuous integration through Jenkins and Phabricator hooks. It ends with questions about these proposals and announcements of job opportunities.
Smoke testing involves basic testing to check if a program runs and performs very basic functions like opening a window and buttons responding to clicks. GUI testing focuses on user interface elements like buttons, menus and windows. Functional testing verifies program features and functions according to requirements. Regression testing is done after functional testing to check that changes didn't break existing functionality, and confirmation testing ensures changes were implemented correctly.
This document summarizes a QNAP intern's report on using the Robot Framework for automated regression testing. It discusses how the framework allows tests to be written once and run every time with each new build. Test cases are stored as text files for version control and can be executed from the command line. The intern demonstrated how automated regression testing found issues across multiple builds and shortened the regression cycle to improve software quality while relieving testers. In conclusion, experienced testers' knowledge was translated to Robot Framework scripts to continue benefiting future testing efforts.
Feature toggling is a multi-purpose technique for easily turning features on and off. I will describe the concept, different types of feature toggles, some best practices, and give some examples of how Visma currently uses feature toggling.
Test in Dockerized System Architecture of LINE NOWLINE Corporation
Johnny Wu
Test in Dockerized System Architecture of LINE NOW/ 在 LINE NOW docker 化系統架構中的測試
Summary:
LINE NOW 是一個利用 i-beacon 來提供線下不同的各種活動類型之服務. 我們利用了 docker 技術, 實現了microservices, 增快開發流程, 使得測試變得簡單方便. 在這個 session 中, 我們將會介紹測試面臨的挑戰, 以及 LINE NOW 團隊如何針對這些問題提供解決方法, 目前使用的系統架構以及相關工具, 還有改善過後的開發與測試流程。
This document discusses continuous delivery (CD) pipelines and how InstallCore uses CD. It describes a classic CD pipeline with development, build, test, and deployment stages. For InstallCore, testing occurs through unit tests, integration tests on a QA environment, and performance/regression tests on a staging environment. The document also explains how InstallCore scales CD by integrating JIRA for ticket management and control, using Robot Framework for automated testing, migrating from Bamboo to Jenkins for scalability, and moving from VMware to Ravello on AWS to enable parallel testing environments.
The document discusses why the author's company switched to using feature branching for their development workflow. Key reasons included reducing risks from untested code in production due to improperly configured feature toggles, which led to increased technical support costs. Feature branching provides a safer approach by having each new feature or change developed on a dedicated branch, with pull requests and testing occurring before code is merged to master. This allows for incremental changes to be made and tested independently, reducing risks compared to batching many changes together without proper testing.
The document discusses feature toggles in software development. It defines feature toggles as conditional statements that hide unfinished functionality. Feature toggles allow developers to add new code without disrupting existing functionality, enabling continuous integration. They also facilitate A/B testing and phased feature releases. The document outlines different types of toggles and methods for implementing them, noting that toggles should be minimized and removed once features are complete to maximize code quality. Overall, feature toggles enable rapid delivery of working software through frequent integration and testing.
The document discusses the current and missing parts of Samsung's open source QA process. It covers their use of compile-time testing, unit testing, and static analysis currently. Areas missing include runtime testing, graphical unit tests, code coverage, and pre-push continuous integration. The presentation proposes steps like making tests mandatory for new APIs, increasing test coverage 5-10% per release, improving graphical testing, and adding pre-push continuous integration through Jenkins and Phabricator hooks. It ends with questions about these proposals and announcements of job opportunities.
Smoke testing involves basic testing to check if a program runs and performs very basic functions like opening a window and buttons responding to clicks. GUI testing focuses on user interface elements like buttons, menus and windows. Functional testing verifies program features and functions according to requirements. Regression testing is done after functional testing to check that changes didn't break existing functionality, and confirmation testing ensures changes were implemented correctly.
This document summarizes a QNAP intern's report on using the Robot Framework for automated regression testing. It discusses how the framework allows tests to be written once and run every time with each new build. Test cases are stored as text files for version control and can be executed from the command line. The intern demonstrated how automated regression testing found issues across multiple builds and shortened the regression cycle to improve software quality while relieving testers. In conclusion, experienced testers' knowledge was translated to Robot Framework scripts to continue benefiting future testing efforts.
Feature toggling is a multi-purpose technique for easily turning features on and off. I will describe the concept, different types of feature toggles, some best practices, and give some examples of how Visma currently uses feature toggling.
Test in Dockerized System Architecture of LINE NOWLINE Corporation
Johnny Wu
Test in Dockerized System Architecture of LINE NOW/ 在 LINE NOW docker 化系統架構中的測試
Summary:
LINE NOW 是一個利用 i-beacon 來提供線下不同的各種活動類型之服務. 我們利用了 docker 技術, 實現了microservices, 增快開發流程, 使得測試變得簡單方便. 在這個 session 中, 我們將會介紹測試面臨的挑戰, 以及 LINE NOW 團隊如何針對這些問題提供解決方法, 目前使用的系統架構以及相關工具, 還有改善過後的開發與測試流程。
This document discusses continuous delivery (CD) pipelines and how InstallCore uses CD. It describes a classic CD pipeline with development, build, test, and deployment stages. For InstallCore, testing occurs through unit tests, integration tests on a QA environment, and performance/regression tests on a staging environment. The document also explains how InstallCore scales CD by integrating JIRA for ticket management and control, using Robot Framework for automated testing, migrating from Bamboo to Jenkins for scalability, and moving from VMware to Ravello on AWS to enable parallel testing environments.
The document discusses why the author's company switched to using feature branching for their development workflow. Key reasons included reducing risks from untested code in production due to improperly configured feature toggles, which led to increased technical support costs. Feature branching provides a safer approach by having each new feature or change developed on a dedicated branch, with pull requests and testing occurring before code is merged to master. This allows for incremental changes to be made and tested independently, reducing risks compared to batching many changes together without proper testing.
The document discusses feature toggles in software development. It defines feature toggles as conditional statements that hide unfinished functionality. Feature toggles allow developers to add new code without disrupting existing functionality, enabling continuous integration. They also facilitate A/B testing and phased feature releases. The document outlines different types of toggles and methods for implementing them, noting that toggles should be minimized and removed once features are complete to maximize code quality. Overall, feature toggles enable rapid delivery of working software through frequent integration and testing.
Once you understand why you want to practice test automation, there is only one question left - how to do that?
Unit tests, Component tests, End-to-End tests, Continuous integration, Code review, Tools...
The document discusses feature toggles, which allow hiding unfinished features from users and separating deployment from release. Feature toggles promote fearless deployment, continuous integration, and avoiding big bang releases. They improve software architecture by allowing testing in live environments with real data. The document also discusses branch by abstraction and using two feature toggles to verify new implementations asynchronously while users use the old code. It raises questions about failure handling, toggle libraries, toggle deletion, and testing combinations.
The document discusses the benefits of automated testing over manual testing for software development. It notes that manual testing is boring, inefficient, and error-prone, while automated testing makes development more effective and fun by finding errors early, allowing code to be refactored with confidence, and proving that code meets specifications. The document then provides examples of different types of automated tests, such as unit tests, integration tests, and acceptance tests, that can improve the development process.
The document provides tips for developing automated tests for the Boot to Gecko (B2G) mobile operating system. It outlines components of B2G like the emulator and build environment. It demonstrates starting the emulator, sending commands, and debugging. An existing WebAPI test is code walked through and run in the emulator. Participants are instructed to develop a new automated WebAPI test for B2G using Marionette that runs in the emulator. Contact information is provided for those interested in contributing.
Performance profiling and testing of symfony application 2Andrew Yatsenko
This document discusses performance profiling and testing of a Symfony application. It recommends using tools like the Symfony profiler toolbar, Blackfire, and logging to measure metrics like SQL query times, external API calls, memory usage, and more. Capturing these metrics during testing and in production helps identify bottlenecks in the code related to performance. The goal is to measure code quality from a performance perspective and ensure the application meets requirements for speed and responsiveness.
How hard can it be to start a software development project? It can be very intimidating to start at the blank page.
This talk offers some ideas how to make getting started less scary and more enjoyable, from the first keyboard stroke to a working usable system.
Code Quality Control in a PHP project. GeekTalks, Cherkassy 2020Andrew Yatsenko
When one experienced and 5 junior developers are working on the project, the team leader can monitor the quality of the code manually, using the help of simple static analyzers like phpmd and phpcs.
In this report, we will consider what to do next, with the growth of the team, when there are too many people for manual control, the teams already consist of strong developers. Approaches, methods of automation tools that we use on the open-source B2B eCommerce platform to control the quality of the code.
FxCop is a tool that analyzes code to validate that it complies with coding standards and detects defects. It includes many predefined rules and allows custom rules to be created. FxCop fits into the development lifecycle by allowing automated code reviews through command line integration or integration into the IDE. Custom reports can also be generated from FxCop results.
The document categorizes API testing into large, medium, and small tests. It also categorizes automation into UI, API, and unit tests. While unit tests and API tests are both code level, unit tests do not query databases, communicate over networks, access file systems, or run multiple tests concurrently like API tests can. The document provides examples of API test cases, such as testing return values based on inputs, tests with no returns, tests that trigger other APIs or events, and tests that modify resources.
Kotlin for Android Developer - Make our live easierTai Dang
Kotlin is an open-source programming language that was designed by JetBrains and first appeared in 2011. It is statically typed and supports functional programming while also being compatible with Java. Kotlin runs on the JVM and JavaScript and is officially supported by Google for Android development. It provides features like null safety, extension functions, and data classes while also being less verbose than Java.
Feature Toggle - What Why and How A technique that allows you to “switch on” or “switch off” features of a product. So till the time the entire story is ready to be released the feature is marked as “switched off”. So though everything that is being developed is in the trunk but it is not visible and is not executed till the time it is “switched on”. There is a lot more to feature toggles and this session will allow you to think away from the conventional approach of Branching and Merging and move towards CI/CD efficiently.
The document discusses agile testing practices and principles. It emphasizes that agile testing focuses on quality over speed, with the whole team sharing responsibility for quality. Agile testers work collaboratively with developers to ensure software meets customer needs. Exploratory testing and test automation are recommended techniques. Continuous integration with Jenkins is presented as a way to get early feedback and detect defects.
HKG15-411: Browser Testing Framework for LHGLinaro
HKG15-411: Browser Testing Framework for LHG
---------------------------------------------------
Speaker: Trevor Woerner, Will Chen
Date: February 12, 2015
---------------------------------------------------
★ Session Summary ★
The purpose of this talk is to provide the audience with an introduction to the testing framework used in Web browser performance testing as implemented by LHG. The browser test suite is used to compare browser performance and compliance by using a series of benchmarks in key test categories. Sample browser results for both Android and RDK will be presented.
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250839
Video: https://www.youtube.com/watch?v=TtAMRnzB2nw
Etherpad: http://pad.linaro.org/p/hkg15-411
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Unit testing is a software development method that involves writing small pieces of code called units to test individual functions or components. This helps ensure code works as intended and finds bugs early. Key benefits of unit testing include keeping code simple, making code more maintainable and robust, and providing regression tests. However, developers sometimes avoid unit testing due to perceptions that it is tedious or not valuable. Tools like NUnit and Visual Studio support automating unit tests. Test-driven development is a technique where tests are written before code to specify desired behavior.
Test automation_strategy_for_legacysystemsVodqaBLR
The document discusses strategies for test automation of legacy systems. It begins by outlining some of the challenges of legacy systems, including a lack of agile testing mindset, unclear requirements, and lack of technical skills. It then covers components of a full test automation puzzle like clarity on user stories, distinguishing test types/levels, and testing infrastructure. Specific strategies discussed include applying the Agile Testing Pyramid, refactoring code using the shortest branch technique or strangulation pattern, and taking a bottom-up testing approach.
QA Fes 2016. Артем Быковец. Как выживать тестировщику в Agile средеQAFest
Уже много было сказано о тестировании в Agile, но в своем докладе я хочу углубиться в детали и поговорить о:
- месте QA в классических моделях разработки: а был ли это действительно процесс обеспечения качества?
- Agile манифесте и его ценности для QA команды
- традиционном vs Agile подходе к разработке: риски, получение value, прозрачность процессов и нагрузка на команды
- тестовой документации в Agile: нужна ли она?
- том, как с пользой не писать Test Plan и что делать с тест кейсами и чек-листами
Kristian Karl - Experiences of Test Automation at Spotify - EuroSTAR 2013TEST Huddle
This document summarizes Spotify's experiences with test automation. It discusses why Spotify automates tests, including to facilitate faster development cycles with shorter release times. It outlines the types of tests Spotify aims to automate, such as usability, functionality, and regression. It describes challenges with test automation like maintaining flaky tests and test data. Spotify's goals are to create automated end-user regression tests across major platforms to facilitate testing workloads and deliver short feedback loops. Model-based testing is used where testers design tests using models and developers implement the automated code. The document demonstrates Spotify's test automation using examples and discusses tools used to support test automation.
This document provides an introduction to Robot Framework, an open source test automation framework for acceptance testing. It discusses Robot Framework's architecture, installation process, test structure, standard and external libraries, Selenium keywords, and provides a demo of creating a simple test case with Robot Framework.
This document discusses best practices for automated testing on iOS using XCUITest. XCUITest is the native UI testing framework for iOS that supports both Swift and Objective-C. The document recommends automating 5% of tests at the unit level and 95% at integration, functional, and UI testing levels. It provides guidance on testing with SDK/API integrations, mocking network layers, and achieving reliable, maintainable test code through practices like continuous testing, avoiding flaky tests, and optimizing page objects.
This document discusses strategies for continuous shift-left automated testing in mobile apps. It recommends establishing a mobile testing automation pyramid with increasing levels of testing from unit tests up to end-to-end UI tests. The pyramid advocates automating 5% unit testing, 10% integration testing, 15% functional testing, and keeping 60% for manual testing and 10% for non-functional testing. It provides best practices for setting up a robust test automation framework that facilitates continuous testing, avoids flaky tests, and maximizes code reusability and test execution speed while reducing human errors.
Once you understand why you want to practice test automation, there is only one question left - how to do that?
Unit tests, Component tests, End-to-End tests, Continuous integration, Code review, Tools...
The document discusses feature toggles, which allow hiding unfinished features from users and separating deployment from release. Feature toggles promote fearless deployment, continuous integration, and avoiding big bang releases. They improve software architecture by allowing testing in live environments with real data. The document also discusses branch by abstraction and using two feature toggles to verify new implementations asynchronously while users use the old code. It raises questions about failure handling, toggle libraries, toggle deletion, and testing combinations.
The document discusses the benefits of automated testing over manual testing for software development. It notes that manual testing is boring, inefficient, and error-prone, while automated testing makes development more effective and fun by finding errors early, allowing code to be refactored with confidence, and proving that code meets specifications. The document then provides examples of different types of automated tests, such as unit tests, integration tests, and acceptance tests, that can improve the development process.
The document provides tips for developing automated tests for the Boot to Gecko (B2G) mobile operating system. It outlines components of B2G like the emulator and build environment. It demonstrates starting the emulator, sending commands, and debugging. An existing WebAPI test is code walked through and run in the emulator. Participants are instructed to develop a new automated WebAPI test for B2G using Marionette that runs in the emulator. Contact information is provided for those interested in contributing.
Performance profiling and testing of symfony application 2Andrew Yatsenko
This document discusses performance profiling and testing of a Symfony application. It recommends using tools like the Symfony profiler toolbar, Blackfire, and logging to measure metrics like SQL query times, external API calls, memory usage, and more. Capturing these metrics during testing and in production helps identify bottlenecks in the code related to performance. The goal is to measure code quality from a performance perspective and ensure the application meets requirements for speed and responsiveness.
How hard can it be to start a software development project? It can be very intimidating to start at the blank page.
This talk offers some ideas how to make getting started less scary and more enjoyable, from the first keyboard stroke to a working usable system.
Code Quality Control in a PHP project. GeekTalks, Cherkassy 2020Andrew Yatsenko
When one experienced and 5 junior developers are working on the project, the team leader can monitor the quality of the code manually, using the help of simple static analyzers like phpmd and phpcs.
In this report, we will consider what to do next, with the growth of the team, when there are too many people for manual control, the teams already consist of strong developers. Approaches, methods of automation tools that we use on the open-source B2B eCommerce platform to control the quality of the code.
FxCop is a tool that analyzes code to validate that it complies with coding standards and detects defects. It includes many predefined rules and allows custom rules to be created. FxCop fits into the development lifecycle by allowing automated code reviews through command line integration or integration into the IDE. Custom reports can also be generated from FxCop results.
The document categorizes API testing into large, medium, and small tests. It also categorizes automation into UI, API, and unit tests. While unit tests and API tests are both code level, unit tests do not query databases, communicate over networks, access file systems, or run multiple tests concurrently like API tests can. The document provides examples of API test cases, such as testing return values based on inputs, tests with no returns, tests that trigger other APIs or events, and tests that modify resources.
Kotlin for Android Developer - Make our live easierTai Dang
Kotlin is an open-source programming language that was designed by JetBrains and first appeared in 2011. It is statically typed and supports functional programming while also being compatible with Java. Kotlin runs on the JVM and JavaScript and is officially supported by Google for Android development. It provides features like null safety, extension functions, and data classes while also being less verbose than Java.
Feature Toggle - What Why and How A technique that allows you to “switch on” or “switch off” features of a product. So till the time the entire story is ready to be released the feature is marked as “switched off”. So though everything that is being developed is in the trunk but it is not visible and is not executed till the time it is “switched on”. There is a lot more to feature toggles and this session will allow you to think away from the conventional approach of Branching and Merging and move towards CI/CD efficiently.
The document discusses agile testing practices and principles. It emphasizes that agile testing focuses on quality over speed, with the whole team sharing responsibility for quality. Agile testers work collaboratively with developers to ensure software meets customer needs. Exploratory testing and test automation are recommended techniques. Continuous integration with Jenkins is presented as a way to get early feedback and detect defects.
HKG15-411: Browser Testing Framework for LHGLinaro
HKG15-411: Browser Testing Framework for LHG
---------------------------------------------------
Speaker: Trevor Woerner, Will Chen
Date: February 12, 2015
---------------------------------------------------
★ Session Summary ★
The purpose of this talk is to provide the audience with an introduction to the testing framework used in Web browser performance testing as implemented by LHG. The browser test suite is used to compare browser performance and compliance by using a series of benchmarks in key test categories. Sample browser results for both Android and RDK will be presented.
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250839
Video: https://www.youtube.com/watch?v=TtAMRnzB2nw
Etherpad: http://pad.linaro.org/p/hkg15-411
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Unit testing is a software development method that involves writing small pieces of code called units to test individual functions or components. This helps ensure code works as intended and finds bugs early. Key benefits of unit testing include keeping code simple, making code more maintainable and robust, and providing regression tests. However, developers sometimes avoid unit testing due to perceptions that it is tedious or not valuable. Tools like NUnit and Visual Studio support automating unit tests. Test-driven development is a technique where tests are written before code to specify desired behavior.
Test automation_strategy_for_legacysystemsVodqaBLR
The document discusses strategies for test automation of legacy systems. It begins by outlining some of the challenges of legacy systems, including a lack of agile testing mindset, unclear requirements, and lack of technical skills. It then covers components of a full test automation puzzle like clarity on user stories, distinguishing test types/levels, and testing infrastructure. Specific strategies discussed include applying the Agile Testing Pyramid, refactoring code using the shortest branch technique or strangulation pattern, and taking a bottom-up testing approach.
QA Fes 2016. Артем Быковец. Как выживать тестировщику в Agile средеQAFest
Уже много было сказано о тестировании в Agile, но в своем докладе я хочу углубиться в детали и поговорить о:
- месте QA в классических моделях разработки: а был ли это действительно процесс обеспечения качества?
- Agile манифесте и его ценности для QA команды
- традиционном vs Agile подходе к разработке: риски, получение value, прозрачность процессов и нагрузка на команды
- тестовой документации в Agile: нужна ли она?
- том, как с пользой не писать Test Plan и что делать с тест кейсами и чек-листами
Kristian Karl - Experiences of Test Automation at Spotify - EuroSTAR 2013TEST Huddle
This document summarizes Spotify's experiences with test automation. It discusses why Spotify automates tests, including to facilitate faster development cycles with shorter release times. It outlines the types of tests Spotify aims to automate, such as usability, functionality, and regression. It describes challenges with test automation like maintaining flaky tests and test data. Spotify's goals are to create automated end-user regression tests across major platforms to facilitate testing workloads and deliver short feedback loops. Model-based testing is used where testers design tests using models and developers implement the automated code. The document demonstrates Spotify's test automation using examples and discusses tools used to support test automation.
This document provides an introduction to Robot Framework, an open source test automation framework for acceptance testing. It discusses Robot Framework's architecture, installation process, test structure, standard and external libraries, Selenium keywords, and provides a demo of creating a simple test case with Robot Framework.
This document discusses best practices for automated testing on iOS using XCUITest. XCUITest is the native UI testing framework for iOS that supports both Swift and Objective-C. The document recommends automating 5% of tests at the unit level and 95% at integration, functional, and UI testing levels. It provides guidance on testing with SDK/API integrations, mocking network layers, and achieving reliable, maintainable test code through practices like continuous testing, avoiding flaky tests, and optimizing page objects.
This document discusses strategies for continuous shift-left automated testing in mobile apps. It recommends establishing a mobile testing automation pyramid with increasing levels of testing from unit tests up to end-to-end UI tests. The pyramid advocates automating 5% unit testing, 10% integration testing, 15% functional testing, and keeping 60% for manual testing and 10% for non-functional testing. It provides best practices for setting up a robust test automation framework that facilitates continuous testing, avoids flaky tests, and maximizes code reusability and test execution speed while reducing human errors.
Cloud Native Testing, 2020 Edition: A Modern Blueprint for Pre-production Tes...OlyaSurits
Cloud native applications can benefit greatly from end-to-end testing before deployment, but integration testing of microservices is often discouraged because it's costly and difficult.
This talk proposes a modern blueprint for cloud native application testing, focusing on pre-production testing and in particular integration testing. Topics discussed include how to handle common challenges with end-to-end and integration testing, such as:
Dealing with state
How to speed up tests runs for improved developer feedback loops
How to test the configuration of a whole system in the era of Infrastructure-as-Code
We will also discuss other types of testing (such as testing in production), and pre-production workarounds often used as an alternative to integration testing (such as contract testing and test doubles), evaluating the pros and cons of each approach, and how they can complement each other.
"Experiences Of Test Automation At Spotify" with Kristian KarlTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-87-experiences-of-test-automation-at-spotify-
At Spotify, we want the manual testing effort to be focused as much as possible at feature testing, less on regression tests. But we still have to do regression. So, we tried to automate a big chunk of that. Regression tests are run on our Desktop, Android, iOS and WebPlayer clients, and also some backend services.
I will share with you how far we have come. What techniques, tools and methodologies we have tried. What experiences has been good, and what has been not that good.
Create Software Design with unit testing, build user experience with UX testing, check definition of done with functional testing – all these are my day-to-day activities. Indeed, I am a developer who has found the value of testing to deliver quality software.
In this presentation I share with you how I have come to use tests for: understanding the features, choosing the best user experience design, choosing the best technical solution, implementing the features and test them to create a reliable system.
You will see practical examples of how tools like Jasmine, Spock, Geb are used for the above types of tests. You will see a project with test code and we will discuss how testing can effectively enhance your professional performance.
Ship quality mobile apps with speed [Webinar]BrowserStack
In the world of agile, the need to ship apps faster has never been more apparent. This translates into shorter release and test cycles.
Learn how to speed up your test and release cycles through BrowserStack.
Key takeaways include:
Best practices on mobile app testing automation
How to decide which devices to test on
How to simulate real-world user scenarios
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.
Mobile Test Automation Made Awesome With AppiumvodQA
This document discusses mobile testing and the tool Appium. It covers the importance of mobile testing, the different types of mobile apps and their features, and the challenges of testing across different device types, OS versions, and configurations. It then discusses the testing approach including test types, tool selection criteria, and testing platforms. The document introduces Appium as an open source, cross-platform tool for mobile test automation and describes its philosophy, features including support for platforms, apps, languages, browsers, OS, and devices/emulators. It provides an overview of Appium's architecture and compares it to other tools. Finally, it outlines the toolset that will be used in a workshop including Eclipse IDE, Appium library, JUnit
Mobile Test Automation Made Awesome With AppiumvodQA
This document discusses mobile testing and the tool Appium. It covers the importance of mobile testing, the different types of mobile apps and their features, and the challenges of testing across different device types, OS versions, and configurations. It then discusses the testing approach including test types, tool selection criteria, and testing platforms. The document introduces Appium as an open source, cross-platform tool for mobile test automation and describes its philosophy, features including support for platforms, apps, languages, browsers, OS, and devices/emulators. It provides an overview of Appium's architecture and compares it to other tools. Finally, it outlines the toolset that will be used in a workshop including Eclipse IDE, Appium library, JUnit
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.
Have you ever wondered what the best way would be to test emails? Or how you would go about testing a messaging queue?
Making sure your components are correctly interacting with each other is both a tester and developer’s concern. Join us to get a better understanding of what you should test and how, both manually and automated.
This session is the first ever in which we will have two units working together to give you a nuanced insight on all aspects of integration testing. We’ll start off exploring the world of integration testing, defining the terminology, and creating a general understanding of what phases and kinds of testing exist. Later on we’ll delve into integration test automation, ranging from database integration testing to selenium UI testing and even as far as LDAP integration testing.
We have a wide variety of demos prepared where we will show you how easy it is to test various components of your infrastructure. Some examples:
- Database testing (JPA)
- Arquillian, exploring container testing, EJB testing and more
- Email testing
- SOAP testing using SoapUI
- LDAP testing
- JMS testing
See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html
With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure.
And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases.
The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions.
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.
Kristian Karl - Experiences of Test Automation at Spotify - EuroSTAR 2013TEST Huddle
EuroSTAR Software Testing Conference 2013 presentation on Experiences of Test Automation at Spotify by Kristian Karl.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
The document discusses software quality and testing practices used by LibrePlan. It describes how LibrePlan uses unit tests, integration tests, regression tests, and other types of tests. It also summarizes LibrePlan's use of tools like Jenkins for continuous integration, Cobertura for test coverage analysis, GNU Gettext for internationalization, and Sahi for automated web UI testing. Overall, the document provides an overview of LibrePlan's approach to ensuring software quality through testing.
Parallel Test Runs with Appium on Real Mobile Devices – Hands-on WebinarBitbar
Watch a live presentation at http://offer.bitbar.com/parallel-test-runs-with-appium-on-real-mobile-devices
Appium is an open source test automation framework and currently one of the hottest framework for mobile app, game and web testing. In this webinar, we’ll discuss about the best practices, how to use Appium for different types of apps, games and web apps, and how to use all new features around it – the parallel test runs, image recognition and more!
Stay tuned and join our upcoming webinars at http://bitbar.com/testing/webinars/
[webinar] Cutting-edge Functional UI Testing Techniques - w/ Adam CarmiApplitools
** Full webinar recording: **
It is no secret that many teams struggle with automated functional UI testing - some to the point where it is completely abandoned - even though the UI is the most significant interface of the system.
In this session, Adam Carmi -- Applitools CTO and Co-founder -- reviewed the main weaknesses of traditional approaches to UI testing, and how they negatively affect test stability, maintainability, coverage, execution speed, and overall ROI. He also discussed how these weaknesses become even more severe when running tests across multiple devices and browsers.
Adam demonstrated how Visual AI -- the innovative technology powering Applitools' testing engine -- can be applied on your existing pipeline to efficiently implement functional UI tests with a fraction of the effort while drastically increasing test coverage and reducing test execution time.
Adam also showed a live coding session, where he converted a traditional UI test into a Visual AI-based test in minutes, and executed it across dozens of devices and browsers in seconds using the Applitools Ultrafast Grid.
Integrating automated testing tools and concepts into pipelines.
1. Coded UI is used for UI testing and Postman + Newman for API testing of a license manager application. Tests are run in parallel on different browsers in the pipeline after deployment.
2. An existing testing framework uses Selenium for UI testing a web application. Tests are structured using page objects and run on Jenkins.
3. Tools and strategies discussed include Page Object Model, test frameworks, test environments, and communication during collaboration on testing. The goal is faster, more reliable releases through prioritized, efficient automated testing.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
18. Automated Testing
Scenario's (BDD)
Given I did not enter any credentials
When I click login
Then an error should be shown
Given I did enter an email as "aabb.com"
When I click login
Then an error should be shown
43. Testen met Frank
Scenario: prompted to log in
Given I am on the home screne
But I am not logged in
When I tap the Friends button
Then I should be on the login screen
44. Testen met Frank
When /^I tap the Friends button$/ do
touch("button marked:'Friends'")
end