EuroSTAR Software Testing Conference 2010 presentation on The Mobile App Quality Challenge by Doron Reuveni. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Mickiel Vroon - Test Environment, The Future Achilles’ HeelTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Test Environment, The Future Achilles’ Heel by Mickiel Vroon. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Vipul Kocher - Software Testing, A Framework Based ApproachTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Software Testing, A Framework Based Approach by Vipul Kocher. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Gitte Ottosen - Agility and Process Maturity, Of Course They Mix!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agility and Process Maturity, Of Course They Mix! by Gitte Ottosen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Mixing Open And Commercial Tools' by Mauro GarofaloTEST Huddle
- Mixing open source and commercial tools can provide benefits but also risks that require careful integration. A case study describes blending open source and commercial testing tools for a Java application. Subversion, JIRA, Eclipse, IBM Rational Functional Tester, and Maveryx were combined in the test environment. The strategy was to reuse tests developed in Rational Functional Tester for legacy functionality and develop new tests for new features using Maveryx.
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Bart Knaack - The Truth About Model-Based Quality ImprovementsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Truth About Model-Based Quality Improvements by Bart Knaack. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Mickiel Vroon - Test Environment, The Future Achilles’ HeelTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Test Environment, The Future Achilles’ Heel by Mickiel Vroon. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Vipul Kocher - Software Testing, A Framework Based ApproachTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Software Testing, A Framework Based Approach by Vipul Kocher. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Gitte Ottosen - Agility and Process Maturity, Of Course They Mix!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agility and Process Maturity, Of Course They Mix! by Gitte Ottosen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Mixing Open And Commercial Tools' by Mauro GarofaloTEST Huddle
- Mixing open source and commercial tools can provide benefits but also risks that require careful integration. A case study describes blending open source and commercial testing tools for a Java application. Subversion, JIRA, Eclipse, IBM Rational Functional Tester, and Maveryx were combined in the test environment. The strategy was to reuse tests developed in Rational Functional Tester for legacy functionality and develop new tests for new features using Maveryx.
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Bart Knaack - The Truth About Model-Based Quality ImprovementsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on The Truth About Model-Based Quality Improvements by Bart Knaack. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Peter Zimmerer - Establishing Testing Knowledge and Experience Sharing at Sie...TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Establishing Testing Knowledge and Experience Sharing at Siemens by Peter Zimmerer. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software TestingTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Lauri Pietarinen - What's Wrong With My Test DataTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on What's Wrong With My Test Data by Lauri Pietarinen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Thomas Axen - Lean Kaizen Applied To Software Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Lean Kaizen Applied To Software Testing by Thomas Axen . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Otto Vinter - Analysing Your Defect Data for Improvement PotentialTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Analysing Your Defect Data for Improvement Potential by Otto Vinter. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Continuous Quality Improvements – A Journey Through The Largest Scrum Projec...TEST Huddle
In this presentation you will learn about how the testing process and continuous quality improvements are aligned to the scrum process in a large software project. We hope that our hands -on experience will give you inspiration on how to tailor the test process in an agile environment. The project has been running for more than two years, with six successful releases to end users. We would like to share our experiences with managing test processes in a large scrum project – our do’s and don’ts, our success stories and also our lessons learned. The project is the largest scrum project in Norway to date.
The project scope is to implement system support for managing a new pension reform for all inhabitants in Norway that are members of the pension fund, and replacing existing system due to outdated technology. Approximately 750 000 project hours will be spent and between 100-180 people are involved in the project: thirteen scrum teams, plus two project management and acceptance testing teams, and one business expert team. Each scrum team contains all the knowledge and expertise needed for developing high quality software: Scrum master, business expert, technical architect, UX designer, developers, build/deploy responsible, and of course, dedicated test resources.
Each software delivery in this project contains five sprints. Each sprint is three weeks, followed by acceptance testing before the delivery is shipped. Test driven development is used in all levels of development, from unit tests all the way up to functional system testing. All test levels up to system integration testing is performed during the development sprint by the scrum teams. We tried to automate UI tests, but this was not successful. However, tests in all other levels are successfully automated, and after each delivery, a fully automated regression test suite is shipped with the code.
Paul Gerrard - Advancing Testing Using Axioms - EuroSTAR 2010TEST Huddle
The document discusses testing axioms, which are context-neutral rules for testing systems. It proposes that testing axioms can be used to advance testing practices by providing a framework for critical thinking about testing. Specifically, separating axioms, context, and values allows testers to clarify positions and approaches for different contexts. It also suggests testing axioms can help identify important skills for testers, such as understanding test models and their limitations. Finally, it explores ideas from "quantum testing" such as assigning significance to individual tests, rather than attempting to quantify their value.
Derk jan de Grood - ET, Best of Both WorldsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Clive Bates - A Pragmatic Approach to Improving Your Testing Process - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on A Pragmatic Approach to Improving Your Testing Process by Clive Bates. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
John Brennen - Red Hot Testing in a Green WorldTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Red Hot Testing in a Green World by John Brennen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Using Functional ,Test Automation to Prevent Defects from Escaping the Develo...TEST Huddle
This document discusses using functional test automation to prevent defects from escaping the development phase. It recommends automating acceptance tests during development to catch bugs early from the user perspective. The process involves preparing for automation by exploring and selecting test candidates, automating the tests as close to development as possible, and repeating the automation across areas, platforms and versions to prevent regression bugs. Continuous integration and handling test errors are also suggested to provide feedback and react to issues identified through automation. The overall goal is to shift testing left in the development cycle through early and frequent automation from a user perspective.
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Kasper Hanselman - Imagination is More Important Than KnowledgeTEST Huddle
The document discusses the need for software testing to adapt to today's complex, networked world. It argues that most testing still focuses on structured functional testing as if for standalone software, rather than integrated systems. It recommends that testers specialize in areas like usability, security, and gain domain expertise. Testers need to be flexible and creative in their approaches. The testing process also needs to align more with project management methods and tools to effectively deliver results.
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Tester Needed? No Thanks, We Use MBT! by Elise Greveraars. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Jelle Calsbeek - Stay Agile with Model Based Testing revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Evolution of New Feature Verification in 3G Networks by Michael Monaghan. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Mats Grindal - Risk-Based Testing - Details of Our Success TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Risk-Based Testing - Details of Our Success by Mats Grindal. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
End users, and more precisely end users involved in acceptance testing decide whether a new application or system will go live or not. Therefore it is very important they are in the same pursuit of quality as the rest of the project. End users are no dedicated testers, although sometimes we expect them to be. Just by looking at their available time for testing, we already know they are not. The fact that they are not trained to be testers, doesn’t make it easier.
But are we really looking for dedicated testers here?
During this presentation, Erik will explain how you can involve end users in such a way that we optimize their added value during their testing activities. An error often made in projects is that end users are only involved during test execution. It’s by having them participate in the test process on regular, well selected moments that we can get the best out of acceptance testing.
By means of a case study, Erik points out these moments. To start with, the acceptance testers need to know the goal of their testing activities. Knowing that, the acceptance testers are already involved at the end of the analysis phase in order to help the writing and prioritisation of high level test scenarios together with setting up the entry criteria for starting the acceptance test phase. Consequently, the acceptance testers will get demos on a regular basis of the software already delivered. These demos deliver valuable information, both for the project team as for the end users.
And finally, after having assessed the test readiness of the system through system testing, the end users will execute their test cases closely monitored by the test coordinator. While executing the tests, it is up to the test coordinator to make sure the end users are always updated on the defects.
The presentation will provide the audience with practical advice, examples and templates on how to set up their acceptance testing in a flexible way without drowning in administrative tasks.
Ruud Teunissen - Personal Test Improvement - Dealing with the FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Personal Test Improvement - Dealing with the Future by Ruud Teunissen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Roar Borlund & Christian Carlsen - Real Exploratory Testing, Now With...TEST Huddle
Exploratory testing approaches like "hotspot" and "coffee break" were presented as ways to optimize time spent testing and find more defects when performing exploratory testing in a service-oriented architecture (SOA). The "hotspot" approach resulted in finding more defects on average but took more time per defect. The "coffee break" approach found fewer defects but in less time. Both approaches provided broader test coverage and additional knowledge of the system compared to traditional testing. The presentation concluded that using a customized mix of both exploratory testing methods can minimize wasted time and add value to a project.
'Architecture Testing: Wrongly Ignored!' by Peter ZimmererTEST Huddle
State-of-the-art testing approaches typically include different testing levels like reviews, unit testing, component testing, integration testing, system testing, and acceptance testing. There is also common sense that typically unit testing is done by developers (they are responsible to check the quality of their units at least to some extent) and system testing is done by professional independent testers. But, who is responsible to adequately test the architecture which is one of the key artifacts in developing and maintaining flexible, powerful, and sustainable products and systems? History has shown that too many project failures and troubles are caused by deficiencies in the architecture.Furthermore, what does the term architecture testing mean and why is this term seldom used?
To answer these questions, Peter describes what architecture testing is all about and explains a list of pragmatic practices and experiences to implement it successfully. He offers practical advice on the required tasks and activities as well as the needed involvement, contributions, and responsibilities of software architects in the area of testing – because a close cooperation between testers and architects is the key to drive and sustain a culture of prevention rather than detection across the lifecycle.
Finally, if we claim to be in pursuit of quality then adequate architecture testing is not only a lever for success but a necessity. And this results not only in better quality but also speeds up development by facilitating change and decreasing maintenance efforts.
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Bolton - Two Futures of Software TestingTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Lauri Pietarinen - What's Wrong With My Test DataTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on What's Wrong With My Test Data by Lauri Pietarinen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Thomas Axen - Lean Kaizen Applied To Software Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Lean Kaizen Applied To Software Testing by Thomas Axen . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Otto Vinter - Analysing Your Defect Data for Improvement PotentialTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Analysing Your Defect Data for Improvement Potential by Otto Vinter. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
'Continuous Quality Improvements – A Journey Through The Largest Scrum Projec...TEST Huddle
In this presentation you will learn about how the testing process and continuous quality improvements are aligned to the scrum process in a large software project. We hope that our hands -on experience will give you inspiration on how to tailor the test process in an agile environment. The project has been running for more than two years, with six successful releases to end users. We would like to share our experiences with managing test processes in a large scrum project – our do’s and don’ts, our success stories and also our lessons learned. The project is the largest scrum project in Norway to date.
The project scope is to implement system support for managing a new pension reform for all inhabitants in Norway that are members of the pension fund, and replacing existing system due to outdated technology. Approximately 750 000 project hours will be spent and between 100-180 people are involved in the project: thirteen scrum teams, plus two project management and acceptance testing teams, and one business expert team. Each scrum team contains all the knowledge and expertise needed for developing high quality software: Scrum master, business expert, technical architect, UX designer, developers, build/deploy responsible, and of course, dedicated test resources.
Each software delivery in this project contains five sprints. Each sprint is three weeks, followed by acceptance testing before the delivery is shipped. Test driven development is used in all levels of development, from unit tests all the way up to functional system testing. All test levels up to system integration testing is performed during the development sprint by the scrum teams. We tried to automate UI tests, but this was not successful. However, tests in all other levels are successfully automated, and after each delivery, a fully automated regression test suite is shipped with the code.
Paul Gerrard - Advancing Testing Using Axioms - EuroSTAR 2010TEST Huddle
The document discusses testing axioms, which are context-neutral rules for testing systems. It proposes that testing axioms can be used to advance testing practices by providing a framework for critical thinking about testing. Specifically, separating axioms, context, and values allows testers to clarify positions and approaches for different contexts. It also suggests testing axioms can help identify important skills for testers, such as understanding test models and their limitations. Finally, it explores ideas from "quantum testing" such as assigning significance to individual tests, rather than attempting to quantify their value.
Derk jan de Grood - ET, Best of Both WorldsTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on ET, Best of Both Worlds by Derk jan de Grood. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Clive Bates - A Pragmatic Approach to Improving Your Testing Process - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on A Pragmatic Approach to Improving Your Testing Process by Clive Bates. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
John Brennen - Red Hot Testing in a Green WorldTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Red Hot Testing in a Green World by John Brennen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Using Functional ,Test Automation to Prevent Defects from Escaping the Develo...TEST Huddle
This document discusses using functional test automation to prevent defects from escaping the development phase. It recommends automating acceptance tests during development to catch bugs early from the user perspective. The process involves preparing for automation by exploring and selecting test candidates, automating the tests as close to development as possible, and repeating the automation across areas, platforms and versions to prevent regression bugs. Continuous integration and handling test errors are also suggested to provide feedback and react to issues identified through automation. The overall goal is to shift testing left in the development cycle through early and frequent automation from a user perspective.
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Kasper Hanselman - Imagination is More Important Than KnowledgeTEST Huddle
The document discusses the need for software testing to adapt to today's complex, networked world. It argues that most testing still focuses on structured functional testing as if for standalone software, rather than integrated systems. It recommends that testers specialize in areas like usability, security, and gain domain expertise. Testers need to be flexible and creative in their approaches. The testing process also needs to align more with project management methods and tools to effectively deliver results.
Elise Greveraars - Tester Needed? No Thanks, We Use MBT!TEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Tester Needed? No Thanks, We Use MBT! by Elise Greveraars. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Jelle Calsbeek - Stay Agile with Model Based Testing revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Evolution of New Feature Verification in 3G Networks by Michael Monaghan. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Mats Grindal - Risk-Based Testing - Details of Our Success TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Risk-Based Testing - Details of Our Success by Mats Grindal. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
End users, and more precisely end users involved in acceptance testing decide whether a new application or system will go live or not. Therefore it is very important they are in the same pursuit of quality as the rest of the project. End users are no dedicated testers, although sometimes we expect them to be. Just by looking at their available time for testing, we already know they are not. The fact that they are not trained to be testers, doesn’t make it easier.
But are we really looking for dedicated testers here?
During this presentation, Erik will explain how you can involve end users in such a way that we optimize their added value during their testing activities. An error often made in projects is that end users are only involved during test execution. It’s by having them participate in the test process on regular, well selected moments that we can get the best out of acceptance testing.
By means of a case study, Erik points out these moments. To start with, the acceptance testers need to know the goal of their testing activities. Knowing that, the acceptance testers are already involved at the end of the analysis phase in order to help the writing and prioritisation of high level test scenarios together with setting up the entry criteria for starting the acceptance test phase. Consequently, the acceptance testers will get demos on a regular basis of the software already delivered. These demos deliver valuable information, both for the project team as for the end users.
And finally, after having assessed the test readiness of the system through system testing, the end users will execute their test cases closely monitored by the test coordinator. While executing the tests, it is up to the test coordinator to make sure the end users are always updated on the defects.
The presentation will provide the audience with practical advice, examples and templates on how to set up their acceptance testing in a flexible way without drowning in administrative tasks.
Ruud Teunissen - Personal Test Improvement - Dealing with the FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Personal Test Improvement - Dealing with the Future by Ruud Teunissen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Michael Roar Borlund & Christian Carlsen - Real Exploratory Testing, Now With...TEST Huddle
Exploratory testing approaches like "hotspot" and "coffee break" were presented as ways to optimize time spent testing and find more defects when performing exploratory testing in a service-oriented architecture (SOA). The "hotspot" approach resulted in finding more defects on average but took more time per defect. The "coffee break" approach found fewer defects but in less time. Both approaches provided broader test coverage and additional knowledge of the system compared to traditional testing. The presentation concluded that using a customized mix of both exploratory testing methods can minimize wasted time and add value to a project.
'Architecture Testing: Wrongly Ignored!' by Peter ZimmererTEST Huddle
State-of-the-art testing approaches typically include different testing levels like reviews, unit testing, component testing, integration testing, system testing, and acceptance testing. There is also common sense that typically unit testing is done by developers (they are responsible to check the quality of their units at least to some extent) and system testing is done by professional independent testers. But, who is responsible to adequately test the architecture which is one of the key artifacts in developing and maintaining flexible, powerful, and sustainable products and systems? History has shown that too many project failures and troubles are caused by deficiencies in the architecture.Furthermore, what does the term architecture testing mean and why is this term seldom used?
To answer these questions, Peter describes what architecture testing is all about and explains a list of pragmatic practices and experiences to implement it successfully. He offers practical advice on the required tasks and activities as well as the needed involvement, contributions, and responsibilities of software architects in the area of testing – because a close cooperation between testers and architects is the key to drive and sustain a culture of prevention rather than detection across the lifecycle.
Finally, if we claim to be in pursuit of quality then adequate architecture testing is not only a lever for success but a necessity. And this results not only in better quality but also speeds up development by facilitating change and decreasing maintenance efforts.
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Presentation about how to set a scope for testing mobile applications. Basic information, and only an overview. Needs to be applied to specific contexts.
Building a useful set of devices for testing apps requires significant knowledge of the Android ecosystem. Once assembled, the device matrix provides broad, efficient coverage with minimal investment.
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.
Join Stacey Brown, President of MindLink Resources, for a webinar that will examine the top 10 qualities of a quality assurance (QA) tester. Learn how to bring out these traits in your current QA staff and how to watch for these soft skills when screening new candidates.
When localizing products, the QA step is essential in confirming the translation and making sure the product was successfully prepared for the target market. Managers trust the QA staff to catch translation and engineering errors and ensure product readiness to avoid quality issues caught by the end customer. Many managers make the mistake of assigning this critical role to a linguist who may not have the right characteristics of a good tester. When selecting QA staff, it is important to consider skills beyond just linguistic and technical. There are many “soft skills” to watch for in a candidate that will give localization managers the confidence that even small errors will be reported by their tester.
In this webinar, Stacey will discuss the top 10 qualities of a quality assurance (QA) tester, how to bring out these traits in current QA staff, and how to watch for these soft skills when screening new candidates.
About the presenter
Stacey Brown is the Talent Management Specialist and President of Mindlink Resources, LLC.. She has a passion for surrounding herself with talented people. For the past 15 years she has successfully built teams of contractors providing a variety of services at large fortune 500 companies in the Pacific Northwest. She specifically has over 12 years of experience recruiting, training and managing QA specialists. Stacey has a degree in Communications and an MBA in Technology Management.
This Doc. useful to in interview questions.
Plz open in full screen & read it & Download it.
Note:- first download and then see presentation its really batter to see & read it.
Different testing requirements that mobile applications have, challenges and solutions Challenges 1. Complex mobile testing matrix, Expensive test environment 2. Repetitive testing 3. Mobile testing for devices located at various locations Solutions: • Risk Based Testing approach • Using Mobile device emulators • Use of Automation tools • Leveraging external services
The document discusses quality assurance frameworks for software development. It defines quality as meeting requirements and outlines the components of quality assurance including software testing, quality control, and software configuration management. It also discusses developing a software quality assurance plan and references common quality standards like ISO9000, CMM, PCMM, and CMMI. The goal of quality assurance is to ensure software products fulfill criteria and have attributes to meet user needs through systematic quality control activities during development.
The document provides an overview of quality assurance and software testing processes. It describes key concepts like requirements gathering, test planning, test case development, defect reporting, retesting and sign off. It also covers quality standards, software development life cycles, testing methodologies, documentation artifacts, and project management structures.
The document discusses beginner quality assurance (QA) testing of websites. It defines QA and explains that QA testing ensures quality in work activities and that products meet requirements. Website QA has some unique aspects because websites are constantly evolving and updated. The document recommends implementing both web standards and company guidelines for effective QA processes. It outlines various QA testing methods including validation testing, data comparison, usability testing, and provides guidelines for drafting checklists and questions for testers.
This document provides an overview of software testing for beginners. It discusses what software testing is, why it's important, and the roles and skills of testers. It also covers the software development and testing lifecycles, common errors, test planning, case development techniques, defect tracking, and types of test reports. The goal is to help beginners gain practical knowledge about software testing processes in real work environments.
Quality Assurance is of Tremendous Importance in Pharma and Health care sector.
A brief of that is try to explain here..
A Trust of the Customer on Product is solely based on the Effective QA
Mobile App Testing: Moving Outside the LabTechWell
No matter how thorough the test team or how expansive the test lab, Chris Munroe knows that defects still abound in mobile apps after launch. With more “non-software” companies launching mobile apps every day, testers have increased pressure to ensure apps are secure and function as intended. In retail and media especially, audiences are incredibly diverse and expect apps to work every time, everywhere, and on every device. These expectations make it imperative for companies to take every possible step to make their mobile apps defect free. This is increasingly difficult to do when all your testing occurs within the confines of the lab—and your users live in the wild. Using real-world examples from USA Today, Chris identifies why you need to test your mobile apps both inside and outside the lab—and do so in a way that is secure, effective, and timely.
This document provides an overview of crowdsourced testing and uTest's approach. It discusses how crowdsourcing can help address the challenges of testing across diverse real-world environments by providing on-demand access to global testers. The document outlines uTest's services, including functional, load, usability, localization and security testing. It addresses myths about crowdsourced testing and how uTest manages its global community of over 100,000 testers through rating and reputation systems to ensure quality. Customers can benefit from in-the-wild testing, unmatched coverage, faster time to market and lower total cost of testing.
Matt Johnston from uTest presented on getting testing help from the crowd. He discussed how app quality is now judged more harshly by users and the need for outside-in quality perspectives. USA Today uses a blended approach of in-house, outsourced, and crowdsourced testing with uTest to test across diverse environments and meet tight deadlines while maintaining a high quality bar. Partnering with uTest helped USA Today reduce bugs, improve usability, and consistently achieve high app store ratings.
Using Crowd sourced testing to regression-test responsive web applications - ...Marc Fasel
Crowd-sourced testing is a relatively new testing approach where an anonymous crowd of testers take on different testing tasks for web-based and mobile applications. We have used this approach to regression test our responsive web application on desktop and mobile devices with great results: it increased our test coverage while drastically reducing the time for regression testing. This talk introduces the concept of crowd-sourced testing, talks about our journey of implementing crowd-sourced testing, and our experience after more than a year of using it.
- The presentation discusses various topics related to mobile application testing such as types of mobile applications, challenges in mobile testing, automation tools, and common errors.
- It covers the different types of mobile applications like native, web-based, and hybrid apps. Testing types include functional, performance, usability, and more. Challenges include device fragmentation, networks, and usability.
- Automation tools discussed include Appium, Ranorex, and Android DDMS. Common errors pertain to functionality, interfaces, interrupt handling, and compatibility across devices.
Mobile opportunity and options - for CIOsTim McGovern
This document discusses trends in mobile devices and applications. It notes rapid growth in smartphones, mobile internet usage, and capabilities of internet-connected devices. Popular mobile platforms are iPhone, Android and Blackberry. Developing professional mobile applications can cost between tens of thousands to hundreds of thousands depending on complexity. The author's organization released a mobile app with most development done internally and some outsourced testing. Key lessons are to set clear goals and metrics for mobile initiatives.
'What the top 10 Most Disruptive Technology Trends Mean for QA and Testing' b...TEST Huddle
This document discusses 10 disruptive technologies and their impact on software testing: 1) Mobile apps, 2) Mobile OS wars, 3) Tabletmania, 4) 4G's speed and productivity, 5) HTML5, 6) IPv6, 7) The cloud, 8) Geo-location, 9) NoSQL databases, and 10) Social media. It explains how each technology is changing the way software is developed and tested, creating new demands for testing across devices, platforms, locations and cloud environments. It emphasizes that software testing must innovate to keep up with the growing pressures of mobile, social and cloud technologies.
Crowd Catcher: take control of the Crowd (part 2 of 3) | QualiTest GroupQualitest
QualiTest hosts a webinar: Crowd Catcher: Take control of the Crowd (part 2 of 3)
QualiTest is proud to team up with Applause to discuss and explore Crowd Testing Apps. We'll learn about Acceptance to Delight and learn about the fundamentals involved with Crowd Testing Apps.
Hosted by:
Biraj Nakarja - Camelot Global
Sanji Alwis - Applause
Jack Dillon - QualiTest Group
Hosted on: November 11th, 2015
QualiTest is the world’s second largest pure play software testing and QA company. Testing and QA is all that we do! visit us at: www.QualiTestGroup.com
Testing in the Wild: Practices for Testing Beyond the LabTechWell
The stakes in the mobile app marketplace are very high, with thousands of apps vying for the limited space on users’ mobile devices. Organizations must ensure that their apps work as intended from day one and to do that must implement a successful mobile testing strategy leveraging in-the-wild testing. Matt Johnston describes how to create and implement a tailored in-the-wild testing strategy to boost app success and improve user experience. Matt provides strategies, tips, and real-world examples and advice on topics ranging from fragmentation issues, to the different problems inherent in web and mobile apps, to deciding what devices you must test vs. those you should test. After hearing real-world examples of how testing in the wild affects app quality, leave with an understanding of and actionable information about how to launch apps that perform as intended in the hands of end-users—from day one.
Four Best Practices for Modern Performance TestingSOASTA
This document discusses best practices for performance testing mobile applications. It begins by acknowledging that there is no single best practice, and that approaches need to be adapted to each situation. It then asks key questions about how mobile is different and how to adapt. The document outlines how performance is important for mobile due to high abandonment rates from poor performance. It also discusses how to assess the user and load profile, address network variability, utilize cloud-based testing, and measure device performance. The summary emphasizes adapting performance analysis and testing approaches to the mobile context.
This presentation by Sirish Kosaraju, COO, RapidValue Solutions explains the best practices of enabling the mobile channel for organizations. It also addresses how to structure your IT org for mobile development, the technology & business changes you will need to consider. Through customer learnings (UOP, Karmaloop Case studies) we will share best practices on improving conversions, increasing sales and promoting the mobile app usage. The follow of the presentation is as follows:
1. Mobility Overview
2. Best Practices for Mobility - Factors to consider
3. Facebook Mobile Strategy Case Study
4. Charting out the Business Strategy
5. Creating Project Plan & Roadmap
6. Considering organizational changes required
7. Measuring usage & end-user feedback
8. Sales & Marketing (Promoting consumer apps)
9. Customer Learning - KarmaLoop, University of Phoenix Case Studies
10. Summary
Mobile App Testing Strategy by RapidValue SolutionsRapidValue
There has been an increase in the adoption of smartphones, tablets and several mobile devices with the passage of time. And it has led to an enormous growth of mobile applications in recent years. Mobile device is considered to be the primary medium of interaction for the customers and also, businesses worldwide. And mobile applications are, actually, driving the communication.
People, generally, do not give much importance to mobile application testing because of its expensive nature. But it is very much essential to ensure that the consumers have a great experience, every time they use the application.
The aim of mobile application testing should be to acquire knowledge about the quality of the service that you are offering. Does it work properly or not? Will it provide services as per the expectation of the customer? These questions need to be answered to ensure that the customer comes back to you, for your service again. Mobile testing is becoming more and more complicated and complex with each passing day. Strategies are invented and used to simplify the mobile application testing.
This presentation primarily addresses, the strategy to be adopted in mobile app testing, the types of mobile app testing and the stages to be followed, before the application is set live.
uTest is the world's largest provider of in-the-wild testing services with over 70,000 testers globally. They provide functional, load, usability, localization, and security testing for over 2,000 customers across various industries. uTest offers better applications through real-world testing across devices and locations, faster time to market by creating test cycles within days, and lower total cost than other testing providers.
Bug deBug Chennai 2012 Talk - Future of testing impact of mobile devices by S...RIA RUI Society
Over last couple of years, mobile devices have shown a phenomenal growth, at the same time PC industry is on a declining path. Due to this, we are experiencing a paradigm shift on how applications are built, tested, and used by the end users, and has a potential to create a disruption in the tradition way of software development and QA. Though it started with consumers, enterprises are also embracing mobility more and more, especially after the stupendous success of iPad. At the same time enterprises are also facing challenges in the area of provisioning, data management, device management, and security. Mobile devices are also used differently compared to traditional computing platforms. Due to this mobility devices and platforms throw up a new kind of challenges to testing fraternity. Calsoft Labs, with its unique competence and experience of working with leading Software and Hardeware companies, has been in the forefront of mobility. Calsoft Labs’ Mobility & Testing practice have been working together for some time to build methodologies, processes, and frameworks to address the challenges arising because of the above mentioned challenges shift and to create a new paradigm in application and product testing.
UserZoom - The #1 Customer and UX Research and Analytics Platform (Javier Dar...UXPA International
UserZoom is the leading Customer and User Experience Research and Analytics Platform. The all-in-one, cloud-based software is the most feature-rich UX research and testing solution in the market. It is designed to support UX Professionals and Online Marketers around the world to create and run remote usability studies – fast, easy and agile. In the market since 2001 and with more than 250 customers in over 25 countries, UserZoom enables leading companies such as Google, eBay, Rakuten and Twitter to cost-effectively test, measure and improve User Experience and increase conversion rates of their Websites and Mobile Apps. UserZoom offices can be found in London, Silicon Valley, Barcelona and Munich.
Four best practices for performance testing mobile apps soasta and utopiaSOASTA
This document discusses best practices for performance testing mobile applications. It begins by acknowledging that there is no single best practice, and that approaches need to be adapted to each situation. It then covers how mobile testing differs from traditional web testing due to factors like device and network diversity. The document provides guidelines for assessing the user and load profile, utilizing network simulation tools, addressing device performance metrics, and leveraging cloud-based solutions. It emphasizes the importance of testing across different networks and devices to fully evaluate the mobile user experience.
This document discusses trends in mobile devices and applications. It notes the rapid growth of smartphones and internet-connected mobile devices. It also discusses trends around the ubiquity of mobile devices and their increasing capabilities. The document provides information on developing applications for different mobile platforms and estimates costs for professional app development. It shares lessons learned from developing mobile applications, including setting goals and metrics.
Similar to Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010 (20)
Why We Need Diversity in Testing- AccentureTEST Huddle
In this webinar Rasa (Testing capability lead for Denmark) and Matthias (EALA Testing capability lead) will share some of their own experiences why diversity matters, give insights into how Accenture as a global firm is promoting diversity and how we are in the process of changing our attitudes and processes to make all of this sustainable
Keys to continuous testing for faster delivery euro star webinar TEST Huddle
Your business needs to deliver faster. To accommodate, Development needs to introduce fewer changes but in a much more frequent cadence. This creates a challenge for test teams to keep up with the rapid pace of change without compromising on quality. Automation is paramount to the success or failure of Continuous Delivery, and Continuous Testing enables early and frequent quality feedback throughout the CI/CD pipeline.
In this webinar, Eran & Ayal will explore how to implement Continuous Testing to ensure high quality releases in a Continuous Delivery environment; including what to test and when to automate new functionality in order to optimize your efforts.
Why you Shouldnt Automated But You Will Anyway TEST Huddle
The document discusses automation in software testing. It begins by outlining common claims made about the benefits of automation, such as saving time and improving quality, but argues that these claims often don't hold true. Automation does not inherently save time, guarantee quality, or reduce resources needed. It also does not always save money when development, maintenance, and infrastructure costs are considered. The document provides a formula for determining when automation is worthwhile based on how many times a test case would need to be rerun manually. It concludes by acknowledging that, despite these drawbacks, organizations will still automate testing because it is exciting, managers demand it, and it benefits careers.
In this webinar Carsten will explore the role of the tester in a Scrum team. He will examine where the tester play an important role in Scrum and how you can contribute to a teams performance.
Leveraging Visual Testing with Your Functional TestsTEST Huddle
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability
Big Data: The Magic to Attain New HeightsTEST Huddle
This document discusses how big data and data science can be used to attain new heights, likening it to magic. It provides an overview of Ken Johnston's background and experiences in data science. It then discusses six keys to a "big" magic show with big data: trying multiple times, addressing issues with over-counting, experimentation techniques like A/B testing, infrastructure for big data, tools and skills, and security, privacy and fraud protection. The document emphasizes the importance of an assistant to help the data scientist or data engineer with various tasks.
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
The document discusses Test Driven Development (TDD) and Test Driven Design. It uses the analogy of building a lightsaber and later a Death Star to illustrate the TDD process and benefits. Some benefits mentioned are better test coverage, less debugging, and better design. The document provides tips for practicing TDD including planning ahead, defining boundaries, taking small steps to pass each test, and maintaining discipline. It emphasizes trying TDD in a team and considering Behavior Driven Development (BDD) as well.
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
3 key takeaways
- Do you know the meaning of your organisation, system, product?
- Can you deliver the important risks right away?
- How can you communicate about the (process and product) risks your dealing with?
View Webinar recording: https://huddle.eurostarsoftwaretesting.com/resource/test-management/is-there-a-risk/
Are Your Tests Well-Travelled? Thoughts About Test CoverageTEST Huddle
This document summarizes a presentation on test coverage given by Dorothy Graham. It uses an analogy of travel to different locations to explain what test coverage means and some caveats. Coverage refers to the relationship between tests and the parts of a system being tested, but achieving 100% coverage does not mean everything is tested. There are four caveats discussed: coverage only measures one aspect of testing, a single test can achieve coverage, coverage does not indicate quality, and it only applies to the existing system not missing pieces. The key recommendation is to ask "coverage of what?" when the term is used rather than assuming more coverage is always better.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.
http://huddle.eurostarsoftwaretesting.com/resource/webinar/need-testers-agile-teams/
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Testers & Teams on the Agile Fluency™ Journey TEST Huddle
The document discusses the Agile Fluency model, which aims to help teams and testers improve their agile skills and practices over time. It describes a pathway with increasing levels of fluency that provide more benefits, including delivering value, optimizing value, and innovating. Reaching higher levels requires investments in training, coaching, and changing team structures and roles. The model can help organizations determine what level of fluency they need and what investments are required for testing teams to operate at that level.
Practical Test Strategy Using HeuristicsTEST Huddle
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Key Takeaways:
- A diagramming method that helps discuss roles
- A one page analysis heuristic for roles
- Why roles matter on projects
https://huddle.eurostarsoftwaretesting.com/resource/people-skills/thinking-through-your-role/
Key Takeaways:
- What will this release contain
- What impact will it have on your test runs
- How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests
- Looking forward, when will the W3C spec be complete
- What can we expect from Selenium 4
https://huddle.eurostarsoftwaretesting.com/
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010
1. The Mobile App Quality Challenge: How To Build Quality Into Your Mobile AppsDoron Reuveni |uTest CEO & Co-Founder |doronr@utest.com
2. uTest| on-demand testing
Agenda
•The Mobile Boom
•A Strategy For Mobile App Quality
•Mobile Testing Challenges
•Crowdsourcing 101
•How Crowdsourced Testing Works
•Sneak Preview of Mobile Testing Tool
1
4. uTest| on-demand testing
The Mobile Boom
3
•$6.2 billion to be spent in 2010 at mobile app stores
•Mobile app stores expected to exceed4.5B downloads in 2010
•Expected to surpass $21.6 billion in 2013
•US subscribers:
204K (1985)
277MM (2009)
5. uTest| on-demand testing
Why Is Mobile Booming?
4
•Mobile is always on, always accessible
•Takes the web with you
Connectivity
Publishing
Sharing
•It’s smarter than traditional web
Geo-intelligent
Contextual
•Combines the best of traditional web and phones
•Continues to innovate
Laptops smart phones net books tablets
6. uTest| on-demand testing
Mobile Meets The Enterprise
5
•Not just for kids (or consumers)
•Mobile applications in the enterprise:
Business apps: CRM, ERP and HR systems
Productivity apps: docs, spreadsheets and presentations
Collaboration apps: email, IM and publishing
•Clinical, financial and customer data being accessed
•Growing pressure for QA to ensure mobile apps work properly and are private and secure
Handsets makers & models
Operating systems
Carriers
Locations
10. uTest| on-demand testing
Mobile Web Path
9
•Argument For
Single platform (the web)
One app to build, launch and maintain
All that’s needed for some companies
•Argument Against
Less controlled user experience
Slower user experience
No app store distribution
Lack of standards across mobile browsers
11. uTest| on-demand testing
Native Apps Path
10
•Argument For
Rich media functionality
Controlled user experience
Faster experience for users
App store distribution
•Argument Against
Multi-platform
Must build, test and maintain multiple apps
Not necessary for some companies
12. uTest| on-demand testing
Alternative Paths
11
•Wholesale Applications Community (WAC)
Consortium of dozens of mobile leaders
–Carriers: AT&T, China Mobile, Orange, Verizon and Sprint
–OEMs: LG, Samsung and Sony Ericsson
Goal: build app once and have it work on all devices, carriers & OS
Good theory and wonderful on paper… but will it work?
–J2EE all over again?
–Competing interests?
–Trying to be all things to all people?
•Hybrid apps
Native app “shell” or “wrapper”
Shared back-end with existing web app (data, functionality, etc)
13. uTest| on-demand testing
Before You Begin
12
•Regardless of which path you choose, back-end work remains
API / web services
Architecture
Database
Back-end functionality
•The important lesson: app quality begins before coding or testing
14. uTest| on-demand testing
Word To The Wise
13
•Start with your users –what do theywant?
Reach users on their terms (web; mobile web; native apps)
What are your users trying to access?
–Static content vs. rich content
–Commerce vs. functionality
•Key fact
Consumer conversion (from surf to purchase) on iPhoneor Android native apps is 3X -10X times that of mobile web sites
Why?
–User comfort with device
–Usability of the native app
–Page load speed
•Forget about making the mobile web; make the web mobile
17. uTest| on-demand testing
1. Coverage
•Mobile Testing Matrix Is Insane
16
OS & Browser
FeaturesHandset Makers& Models
18. uTest| on-demand testing
1. Coverage
•Mobile Testing Matrix Is Insane
17
OS & Browser
Features
Handset Makers
& ModelsWirelessCarriers
19. uTest| on-demand testing
1. Coverage
•Mobile Testing Matrix Is Insane
18OS & Browser
Features
Handset Makers
& ModelsWirelessCarriersLocation
20. uTest| on-demand testing
2. Managing Resources & Costs
•Managing peaks & valleys; unexpected twists & turns
•Enough to make QA leaders sick
21. uTest| on-demand testing
3. Time-to-Market
•Never-ending race for each new app and version
•Can exhaust the best test managers and teams
22. uTest| on-demand testing
4. Mobile App Quality
•Becoming impossible for QA leaders to assure quality
23. uTest| on-demand testing
What’s At Stake
22
•Billions of dollars and the futureof apps
•Mobile app competition hotter than ever
Media attention
User adoption
App store approvals
•Pressure to build, test & launch apps never been higher
•Apps device sales
24. uTest| on-demand testing
CROWDSOURCING DEFINED:
23
“Taking a service traditionally performed by a person or team and sourcing it to a large online group of people as an open project.”
-Jeff Howe Wiredjournalist & author of Crowdsourcing
27. uTest| on-demand testing
From Mob to Community
And mobsdon’t work in every category
Example: delivering a skilled service like software testing or development requires an orderly “community” capable of consistently producing the desired results
26
31. uTest| on-demand testing
Crowdsourced Testing 101
•Traditionally, companies had two options:
Option 1: Build robust in-house staff & lab
–Cost prohibitive for many companies
Option 2: Outsource or offshore
–Loss of control, communication challenges and quality risks
•A third, alternative trend has emerged to complement:
Option 3: Crowdsourcing
–On-demand extension of in-house testing efforts
–Coverage across location, language, OS, browser, handset or carrier
30
32. uTest| on-demand testing
Where Crowdsourcing Fits
•In-House vs. Offshoring
31In-HousePros:
•More control
•More visibility
•App/biz knowledgeCons:
•Fixed costs
•Scalability
•Coverage
•Higher commitment
OffshoringPros:
•Perceived cost
•Scalability
•Lower commitmentCons:
•Adaptability
•Diversity of testers
•Transparency
•Communication
•Hidden costs
Crowdsourcing
Pros:
•Coverage
•Agility
•Creativity
•Total costCons:
•Coordination
•Learning curve
•Signal-to-noise ratio
33. uTest| on-demand testing
Where Crowdsourcing Fits
•Manual vs. Automated
32ManualPros:
•Agility
•Creativity
•Explores the edgesCons:
•Scalability
•Repetitive tasks
•Human error
•Exhaustive coverage
AutomatedPros:
•Good for mainstream UX
•Scalability
•Cost
•Speed for repetitive tasksCons:
•In-the-lab vs. In-the-wild
•Ignores the unexpected
•Limits imagination
•Hinders adaptabilityCrowdsourcing
34. uTest| on-demand testing
Where Crowdsourcing Fits
•Exploratory vs. Scripted
33ExploratoryPros:
•Agility
•Creative
•Explores the edgesCons:
•Scale
•Repetitive
•Human Error
ScriptedPros:
•Predictability
•Scalability
•ControlCons:
•In-the-lab vs. In-the-wild
•Ignores the unexpected
•Limits testers’ creativity
Crowdsourcing
35. uTest| on-demand testing
Where Crowdsourcing Fits
•On-Device vs. Off-Device
34On-DevicePros:
•Agility
•Creative
•Explores the edgesCons:
•Time-consuming
•Cost-prohibitive
•Coverage
Off-DevicePros:
•Cost
•Speed
•ConvenienceCons:
•In-the-lab vs. In-the-wild
•Limited user expertise
•Detached from real world UX
Crowdsourcing
36. uTest| on-demand testing
How Crowdsourced Testing Works
35CustomersTesting CommunityTesters paidSpecify Testing Needs
-Handset Maker, Model & OS
-Carrier, Location & Language
Customerapproves
Selected testers invited
to projectTesters report in real-time
37. uTest| on-demand testing
Crowdsourced Testing Benefits
36
•Crowdsourced testing benefits:
Higher quality apps:
–Real-world testing;
–Invite favorite testers back
Get to market faster:
–2-3 day test cycles instead of 2-3 weeks
–24x7 testing cycles
Contain costs:
–Costs a fraction of traditional outsourced/offshore testing
–No long-term contracts or fixed costs
40. uTest| on-demand testing
Case Study: 1Cast
•Seattle-based mobile company
•iPhone& Android apps for news & videos
Challenge:
–Launch leading apps in a multi-platform world --with a startup team
–Between Wi-Fi, 3G, Edge, and others, 1Cast needed more hands-on testing resources than they could afford to hire
Strategy:
–Using only in-house QA was unrealistic financially
–Unwilling to commit or relinquish control to an offshore testing firm
–Researched creative alternatives and discovered crowdsourced testing
Results:
–Global testing coverage at a fraction of the cost of alternatives
–Specified testing requirements and built a virtual testing team
–Integrated crowdsourcedtesting into product development methodology to support testing of weekly builds
39
41. uTest| on-demand testing
Case Study: Tapulous
•Palo Alto-based mobile company
•Gaming apps for iPhoneand Android
Challenge:
–Ensure functionality for Tap Tap Revenge across OS, carrier, device and location ahead of a major upcoming launch
–Testing specific features, including multi-player online mode, post-game screens, offline usage and 3G connectivity
Strategy:
–In-house team was too familiar with app; needed a fresh set of eyes
–Outsourcing firms were prohibitively expensive and excessive
–Crowdsourcing was an ideal blend of beta users, in-house and outsourcing
Results:
–Testing coverage across all of North America; usability and functionality
–Several high-priority bugs discovered beforehigh-profile launch
–Achieved comprehensive testing coverage in weeks, not months over a blend of devices, locations and users
40
45. uTest| on-demand testing
Remote Mobile Access
•A story…
A tester –let’s say Roy from Boston –reports a critical bug on your Blackberry app
Your QA manager and developer review it, reproduce it and ultimately, the bug is fixed
The developer or tester wants to see the bug fix in the wild –ON the actual device that first encountered the bug
Now, you can “borrow” that tester’s device remotely
•Can also be used for
Reproducing bugs on the device
Running automated diagnostics scripts on the device
44