The document discusses testing in Agile environments. It covers traditional vs Agile testing approaches, the role of testers in Agile projects, and specific technical skills for Agile testers. In Agile, testing is iterative and incremental, occurring alongside development. Testers collaborate with developers to help define requirements and acceptance criteria, automate tests, and find bugs through exploratory testing. Their role focuses more on communication and facilitating quality than traditional documentation-heavy testing.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Software Testing Attacks for Mobile and Embedded DevicesXBOSoft
Jon Hagar author of "Software Test Attacks to Break Mobile and Embedded Devices" presents Software testing concepts for mobile and imbedded devices in this webinar- hosted by XBOSoft.
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
Proactive SQA™ Shifting Left w/Proactive Software Quality PracticesXBOSoft
This webinar hosted by XBOSoft featured our guest speaker, Robin Goldsmith. Robin, an expert in software requirements and business analysis, presented how to develop a definition of software quality as a first step any software development process. Although most of what is called SQA today actually is just testing, true SQA is much different from quality control (QC) testing. SQA can and should do far more, contributing proactively to assure the software process in fact does the right things well so it truly produces high quality cheaper, preventing errors or catching them earlier when they can be fixed more easily. This interactive webinar positions SQA and explains the six proactive functions it should perform to provide far greater value.
Agile User Acceptance Testing - Incorporating UAT into AgileXBOSoft
In this quarterly XBOSoft webinar, we discussed the deficiencies of the #agile process in incorporating the user and how to alleviate these issues to create user acceptance for agile. We also demonstrated in Jira how this is implemented with the SynapseRT plug-in by Go2group.
Defect Patterns Analysis for Agile and Waterfall - XBOSoft Webinar with Micha...XBOSoft
Whether you’re waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team’s success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. We’ll also look at techniques that use defect curves to “predict the trajectory” of a project and its Development and QA phases.
Is this possible? Artificial Intelligence Based Test Automation but with no AI? Well, according to Jeremias Roessler, it is! Find out how in this quarterly webinar slidedeck with XBOSoft's special guest speaker, Jeremy Rößler. What good are 400 additional AI-generated UI tests, if we don’t want to maintain our existing human-created ones? This question lies at the heart of AI-based test generation. Recheck-web addresses this issue elegantly and without any “AI-magic” … using a whole different approach to test automation. This refreshingly unusual approach to test automation (difference testing) has many advantages over conventional test automation and he shows how to overcome the oracle problem. This approach makes tests easy to create and maintain, robust and more complete. You can use this approach today in your existing UI testing setup for websites (currently available for Selenium/Java, more to come).
The Three Pillars Approach to an Agile Testing StrategyTechWell
Far too often, organizations focus solely on the development teams and their technical practices as their agile adoption strategy. And then there’s the near constant focus on acquiring development tools. Often the testing activity and the testing teams are left behind in agile adoption, or even worse, they’re simply along for the ride. This is not an effective transformation strategy. Join experienced agile coach Bob Galen as he shares the Three Pillars framework for establishing a balanced strategic plan for quality and testing. The Three Pillars focus on development and test automation, testing practices, and collaboration activities that ensure you have a balanced approach to agile testing. Specifically, Bob explores risk-based testing, exploratory testing, paired collaboration around agile requirements, agile test design, and TDD-BDD-functional testing automation as tactics within a balanced framework. Leave with ideas to immediately initiate or re-tool a much more effective and balanced agile testing strategy.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Software Testing Attacks for Mobile and Embedded DevicesXBOSoft
Jon Hagar author of "Software Test Attacks to Break Mobile and Embedded Devices" presents Software testing concepts for mobile and imbedded devices in this webinar- hosted by XBOSoft.
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
Proactive SQA™ Shifting Left w/Proactive Software Quality PracticesXBOSoft
This webinar hosted by XBOSoft featured our guest speaker, Robin Goldsmith. Robin, an expert in software requirements and business analysis, presented how to develop a definition of software quality as a first step any software development process. Although most of what is called SQA today actually is just testing, true SQA is much different from quality control (QC) testing. SQA can and should do far more, contributing proactively to assure the software process in fact does the right things well so it truly produces high quality cheaper, preventing errors or catching them earlier when they can be fixed more easily. This interactive webinar positions SQA and explains the six proactive functions it should perform to provide far greater value.
Agile User Acceptance Testing - Incorporating UAT into AgileXBOSoft
In this quarterly XBOSoft webinar, we discussed the deficiencies of the #agile process in incorporating the user and how to alleviate these issues to create user acceptance for agile. We also demonstrated in Jira how this is implemented with the SynapseRT plug-in by Go2group.
Defect Patterns Analysis for Agile and Waterfall - XBOSoft Webinar with Micha...XBOSoft
Whether you’re waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team’s success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. We’ll also look at techniques that use defect curves to “predict the trajectory” of a project and its Development and QA phases.
Is this possible? Artificial Intelligence Based Test Automation but with no AI? Well, according to Jeremias Roessler, it is! Find out how in this quarterly webinar slidedeck with XBOSoft's special guest speaker, Jeremy Rößler. What good are 400 additional AI-generated UI tests, if we don’t want to maintain our existing human-created ones? This question lies at the heart of AI-based test generation. Recheck-web addresses this issue elegantly and without any “AI-magic” … using a whole different approach to test automation. This refreshingly unusual approach to test automation (difference testing) has many advantages over conventional test automation and he shows how to overcome the oracle problem. This approach makes tests easy to create and maintain, robust and more complete. You can use this approach today in your existing UI testing setup for websites (currently available for Selenium/Java, more to come).
The Three Pillars Approach to an Agile Testing StrategyTechWell
Far too often, organizations focus solely on the development teams and their technical practices as their agile adoption strategy. And then there’s the near constant focus on acquiring development tools. Often the testing activity and the testing teams are left behind in agile adoption, or even worse, they’re simply along for the ride. This is not an effective transformation strategy. Join experienced agile coach Bob Galen as he shares the Three Pillars framework for establishing a balanced strategic plan for quality and testing. The Three Pillars focus on development and test automation, testing practices, and collaboration activities that ensure you have a balanced approach to agile testing. Specifically, Bob explores risk-based testing, exploratory testing, paired collaboration around agile requirements, agile test design, and TDD-BDD-functional testing automation as tactics within a balanced framework. Leave with ideas to immediately initiate or re-tool a much more effective and balanced agile testing strategy.
A Non-profit testing community and certification organization.
A global alliance of visionary industry leaders, prominent authors, leading educational institutions and testing evangelists who are passionate about proliferation of agile in testing.
The Mission:
- To grow agile testing awareness, practices and acceptance.
- To create a learning road-map specifically in agile testing space.
- To identify the milestones that can be evaluated, certified and thus recognized.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Evolve or Die: Healthcare IT Testing | QASymphony WebinarQASymphony
Modern software testing for Healthcare Organizations. Learn about best practices for software testing in the healthcare industry featuring Mike Cooper, Chief Quality Officer of Healthcare IT Leaders and Kevin Dunne, VP of Business Development at QASymphony
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
Discussion about Input and Output of every Scrum Events. Inside about what to inspect and adapt within these events. Entirely based on Scrum Guide and pretty much similar to PSM workshop.
Closing the Requirements and Testing Loop WebinarQASymphony
QASYMPHONY & BLUEPRINT PARTNER UP
Learn about the new partnership between QASymphony and Blueprint. Connecting software requirements with proper test coverage still remains an age old problem for software development teams. This new partnership will provide alignment between requirements and testing teams of all types to get the visibility and traceability needed to understand their requirements coverage.
In this webinar, Kevin Dunne, QASymphony's VP of Strategy and Business Development and Ruth Zive, VP of Marketing at Blueprint will answer the following questions:
What is QASymphonys qTest Platform?
How is this platform enhanced by Blueprint?
How does the integration between qTest and Blueprint work?
Why does your team need this offering?
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
High performing organizations don't trade off quality, throughput, and reliability: they work to improve all of these and use their software delivery capability to drive organizational performance. In this talk, Jez presents the results from DevOps Research and Assessment's five-year research program, including how continuous delivery and good architecture produce higher software delivery performance, and how to measure culture and its impact on IT and organizational culture. They explain the importance of knowing how (and what) to measure so you focus on what’s important and communicate progress to peers, leaders, and stakeholders. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to keep getting better at building, delivering, and operating software systems.
More details:
https://confengine.com/agile-india-2019/proposal/8524/building-and-scaling-high-performing-technology-organizations
Conference link: https://2019.agileindia.org
QA team transition to agile testing at Alcatel LucentAgileSparks
In this session I will outline/explore the journey of a common QA team without coding skills into Agile testing arena. Main focus on Acceptance Test Driven Development and executable specs. The session will be based on a real case study from Alcatel Lucent Haifa. At the end of the session you will understand the concept of executable specs,and ATDD, You will see real example of test implementation in ATDD tool (Cucumber) and will understand the steps required to make such transition with some do/not do tips in tool and process implementation (based on Alcatel case study).
You will get (printed) the suggested implementation plan and do/not do tips of ATDD automation tools implementation
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Continuous Deployment and Testing Workshop from Better Software WestCory Foy
In this workshop from the 2015 SQE Better Software West conference, Cory Foy details the Continuous Paradigm companies are embracing - including Continuous Integration, Continuous Deployment, and Continuous Testing. This presentation was co-created by Jared Richardson.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
A Non-profit testing community and certification organization.
A global alliance of visionary industry leaders, prominent authors, leading educational institutions and testing evangelists who are passionate about proliferation of agile in testing.
The Mission:
- To grow agile testing awareness, practices and acceptance.
- To create a learning road-map specifically in agile testing space.
- To identify the milestones that can be evaluated, certified and thus recognized.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Evolve or Die: Healthcare IT Testing | QASymphony WebinarQASymphony
Modern software testing for Healthcare Organizations. Learn about best practices for software testing in the healthcare industry featuring Mike Cooper, Chief Quality Officer of Healthcare IT Leaders and Kevin Dunne, VP of Business Development at QASymphony
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
Discussion about Input and Output of every Scrum Events. Inside about what to inspect and adapt within these events. Entirely based on Scrum Guide and pretty much similar to PSM workshop.
Closing the Requirements and Testing Loop WebinarQASymphony
QASYMPHONY & BLUEPRINT PARTNER UP
Learn about the new partnership between QASymphony and Blueprint. Connecting software requirements with proper test coverage still remains an age old problem for software development teams. This new partnership will provide alignment between requirements and testing teams of all types to get the visibility and traceability needed to understand their requirements coverage.
In this webinar, Kevin Dunne, QASymphony's VP of Strategy and Business Development and Ruth Zive, VP of Marketing at Blueprint will answer the following questions:
What is QASymphonys qTest Platform?
How is this platform enhanced by Blueprint?
How does the integration between qTest and Blueprint work?
Why does your team need this offering?
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
High performing organizations don't trade off quality, throughput, and reliability: they work to improve all of these and use their software delivery capability to drive organizational performance. In this talk, Jez presents the results from DevOps Research and Assessment's five-year research program, including how continuous delivery and good architecture produce higher software delivery performance, and how to measure culture and its impact on IT and organizational culture. They explain the importance of knowing how (and what) to measure so you focus on what’s important and communicate progress to peers, leaders, and stakeholders. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to keep getting better at building, delivering, and operating software systems.
More details:
https://confengine.com/agile-india-2019/proposal/8524/building-and-scaling-high-performing-technology-organizations
Conference link: https://2019.agileindia.org
QA team transition to agile testing at Alcatel LucentAgileSparks
In this session I will outline/explore the journey of a common QA team without coding skills into Agile testing arena. Main focus on Acceptance Test Driven Development and executable specs. The session will be based on a real case study from Alcatel Lucent Haifa. At the end of the session you will understand the concept of executable specs,and ATDD, You will see real example of test implementation in ATDD tool (Cucumber) and will understand the steps required to make such transition with some do/not do tips in tool and process implementation (based on Alcatel case study).
You will get (printed) the suggested implementation plan and do/not do tips of ATDD automation tools implementation
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Continuous Deployment and Testing Workshop from Better Software WestCory Foy
In this workshop from the 2015 SQE Better Software West conference, Cory Foy details the Continuous Paradigm companies are embracing - including Continuous Integration, Continuous Deployment, and Continuous Testing. This presentation was co-created by Jared Richardson.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
Conferência
As TIC e a Saúde no Portugal de 2011
15 de Dezembro de 2011
Auditório do Centro Hospitalar Psiquiátrico de Lisboa
Av. Brasil, Lisboa
Coordenação: Prof. Drª Maria Helena Monteiro
PROGRAMA
08:30 Recepção dos Participantes 08:50 Boas Vindas – Prof. Dr. José Dias Coelho (APDSI) Dr. Cunha Ribeiro em representação do Senhor Ministro da Saúde Dr. Paulo Macedo 09:00 A IBM – a Saúde e a Investigação Dr.ª Cristina Semião | Directora do Sector Público, IBM 09:20 Software AG – Um Caso de Estudo das TIC na Saúde – Parnassia Bavo Groep Mr. Mark Rhoden | Senior Vice President EMEA (apresentação na língua inglesa) 09:40 Os registo de doentes (patient registries) como instrumentos de suporte à prática clínica, à gestão/administração e às politicas em saúde Prof. Dr. António Vaz Carneiro | Director do Centro de Estudos de Medicina Baseada na Evidência da Faculdade de Medicina da UL 10:10 O Cidadão e a Saúde – novos modelos de prestação de serviços … Dr. Raul Mascarenhas | Presidente do Conselho de Administração da SPMS
Café (10:30 a 11:00)
11:00 – Debate – Interoperabilidade e Registo de Saúde Electrónico – Sonho ou Realidade em Portugal? Moderação – Dr. Adalberto Campos Fernandes (ENSP/UNL) - Prof. Dr. Henrique Martins | Comissão para a Informatização Clínica - Prof. Dr. José Carlos Nascimento | Universidade do Minho - Dr. Luis Campos | Centro Hospitalar Lisboa Oeste 12:00 – Debate – TeleMedicina – Experiências Cá e Lá … Moderação – Eng.ª Sara Carrasqueiro (ENSP/UNL) - Dr. Miguel Soares de Oliveira | INEM - Dr. Paulo Freitas | Instituto Marquês de Valle Flôr - Dr.ª Teresa Delgado | Hospital Santa Maria Lisboa
Almoço Livre (13:00 a 14.00)
14:00 – Debate – A transformação tecnológica na Saúde em Portugal – a quadratura do círculo no SNS Moderação – Prof. Dr. Álvaro Rocha (UFP) - Dr. Ponciano Oliveira | Vogal do Conselho Directivo da ARS Norte, IP - Dr. José Manuel Azenha Tereso | Presidente do Conselho Directivo da ARS Centro, IP - Dr. Cunha Ribeiro | Presidente do Conselho Directivo da ARS de Lisboa e Vale do Tejo, IP - Dr. José Alberto Robalo | Presidente do Conselho Directivo da ARS Alentejo, IP - Dr. Martins dos Santos | Presidente do Conselho Directivo da ARS Algarve, IP * 15:30 – A Plataforma Digital do Registo Oncológico Regional Sul – Uma experiência inovadora Dr.ª Ana Miranda | IPO Lisboa
Café (16:00 a 16:30)
16:30 - A Gestão do Risco nos Grandes Hospitais Eng.º Rui Gomes | Director das Tecnologias e Informação do HPFF 17:00 - Activity Based Cost na Gestão da Saúde Prof. Dr.ª Ana Paula Harfouche | IPO Lisboa | UTL/ISCSP 17:30 – Network Innovation na Saúde Dr. Paulo Nunes de Abreu | groupVision Education Services – Fórum Hospital do Futuro
18:00 Encerramento
O Empreendedorismo e a Inovação na Saúde
Eng. Joaquim Cunha | Director Executivo da Health Cluster Portugal)
18:30 Fim da Conferência
– Prof. Dr.ª Maria Helena Monteiro | UTL/ISCSP/CAPP/APDSI
– Eng. António Vasconcelos da Cunha | APDSI
A rework of metade's slides at http://www.slideshare.net/metade/linked-data-on-the-bbc for a SAMT 2009 Industry Day presentation.
Details several linked data projects going on at the BBC, and why/how we do it.
Digital Leadership Series : Shawn O'Neal Capgemini
Shawn O’Neal is VP of Global Marketing Data and Analytics at Unilever, part of the Consumer & Marketing Insights (CMI) team, and he leads the company’s Global People Data Program.
The ultimate objective of the program is to enable 1 billion relationships through digital data analysis and new ways of
connecting with people.
In his 12 years at Unilever, Shawn has worked across a range of roles in customer development
and consumer & marketing insights, with a particular focus on strategy, analysis, and the optimal use of information for
decision-making.
Big Data Day LA 2015 - Large Scale Distinct Count -- The HyperLogLog algorith...Data Con LA
"At OpenX we not only use the tools in big data ecosystems to solve our business problems, but also explore the cutting edge algorithms for practical uses. HyperLogLog is one of the algorithm that we use intensively in our internal system. It has really low computation cost and can easily plug into map-reduce framework (hadoop or spark). Some of the applications that worth to highlight are:
* high cardinality test
* distinct count of unique users over time
* Visualize hyperloglog for fraud detection"
L'enjeu du Big Data Marketing : l'enrichissement de l'expérience utilisateurs!
Les objectifs induits sont l'amélioration de la conversion, l'augmentation du panier moyen, la diminution des taux de rebond et de sortie, l'accroissement de la productivité et de l'efficacité interne de l'entreprise.
Testing for agile teams . What's the difference between this and other testing ? What are the goals for such testing ?
Is agile testing needed at all ? Why ?
You will find some answers inside and mist likely will be directed to the right way.
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Behaviour Driven Development: Oltre i limiti del possibileIosif Itkin
The QA Financial Forum: Milan 2019
23 January at the Excelsior Hotel Gallia.
Anna-Maria Lukina, Exactpro Business Development Director
The QA Financial Forum: Milan is one of the leading fintech conferences in Italy. The event focuses on the latest achievements in software risk management and automation of software testing. The predominant theme of the Milan event will be Quality Assurance for the entire Software Development Life Cycle (SDLC).
The topics under discussion will feature:
- Technologies for Automation & AI
- DevOps & CI/CD
- Value Stream Management
- Test Data Management
- Regulatory Compliance
- App Security & DevSecOps
- Testing and quality assurance of Blockchain platforms
The official language of the event is Italian.
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Basic overview of software test types, methodologies.
Explaining and reasons to test and common pitfalls with various testing methodologies.
Example scenarios for the viewer to think about test strategies.
Tips to avoid having to write tests in the first place.
Content created and presented by Nico Heidtke at the "Die Programmierer" meetup organized by Binary-Gears in Darmstadt, Germany at 02.07.2019.
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
EASY TUTORIAL OF HOW TO USE CAPCUT BY: FEBLESS HERNANEFebless Hernane
CapCut is an easy-to-use video editing app perfect for beginners. To start, download and open CapCut on your phone. Tap "New Project" and select the videos or photos you want to edit. You can trim clips by dragging the edges, add text by tapping "Text," and include music by selecting "Audio." Enhance your video with filters and effects from the "Effects" menu. When you're happy with your video, tap the export button to save and share it. CapCut makes video editing simple and fun for everyone!
Hello everyone! I am thrilled to present my latest portfolio on LinkedIn, marking the culmination of my architectural journey thus far. Over the span of five years, I've been fortunate to acquire a wealth of knowledge under the guidance of esteemed professors and industry mentors. From rigorous academic pursuits to practical engagements, each experience has contributed to my growth and refinement as an architecture student. This portfolio not only showcases my projects but also underscores my attention to detail and to innovative architecture as a profession.
Visual Style and Aesthetics: Basics of Visual Design
Visual Design for Enterprise Applications
Range of Visual Styles.
Mobile Interfaces:
Challenges and Opportunities of Mobile Design
Approach to Mobile Design
Patterns
Storytelling For The Web: Integrate Storytelling in your Design ProcessChiara Aliotta
In this slides I explain how I have used storytelling techniques to elevate websites and brands and create memorable user experiences. You can discover practical tips as I showcase the elements of good storytelling and its applied to some examples of diverse brands/projects..
Between Filth and Fortune- Urban Cattle Foraging Realities by Devi S Nair, An...Mansi Shah
This study examines cattle rearing in urban and rural settings, focusing on milk production and consumption. By exploring a case in Ahmedabad, it highlights the challenges and processes in dairy farming across different environments, emphasising the need for sustainable practices and the essential role of milk in daily consumption.
2. Table of contents
1. Traditional style QA
2. Agile Approaches
3. An Agile Tester
4. Traditional vs. Agile
5. Role Testers Play
6. Testing & Testers on Agile Projects
7. Question: While a developer is coding a task, it is impossible for a tester to
test it (it doesn't exist yet). What then is the role of a tester at this point.
8. Question: Is the tester now involved in unit testing? Is this done parallel to
black box testing?
9. Question: What does the tester do during a sprint where primarily
infrastructural changes have been made, that may only be testable in unit
testing?
10. Specific Technical Skills For Agile Tester‟s Toolkit
http://qtp.blogspot.com 2
3. Traditional Style Quality Assurance
Process and tools are a key part of QA and Testing.
QA people seem to love documentation.
QA people want to see the written specification.
And where is testing without a plan?
So, is there a role for QA in Agile projects?
Maybe, but the role is different, the tasks are different.
http://qtp.blogspot.com 3
4. Agile approaches are changing the conversation
about software development
Agile shifted our attention to small teams.
.
Incrementally delivering quality software.
The old ideas about testing at the end of the coding phase no longer applicable.
We need to think about the role of Quality.
Assurance in Agile Projects.
Definitely NOT business-as-usual.
http://qtp.blogspot.com 4
5. An Agile Tester
A professional tester who embraces
change, collaborates well with both technical and
business people, and understands the concept of
using tests to document requirements and drive
development.
Agile testers tend to have good technical
skills, know how to collaborate with others to
automate tests, and are also experienced
exploratory testers.
They‟re willing to learn what customers do so that
they can better understand the customers‟
software requirements.
http://qtp.blogspot.com 5
6. Traditional vs. Agile Testing
Phased Model e.g. Waterfall
Requirements Specifications Code Testing Release
Time
Agile:
F Iterative & Incremental
E
Each story is expanded, coded & tested
D D Possible release after each iteration
C C C
A B A B A B A B
http://qtp.blogspot.com 6
7. Traditional vs. Agile Testing
Traditional Agile
In the phased approach diagram (see previous Agile is iterative and incremental (see previous
slide), it is clear that testing happens at the end, slide). This means that the testers test each
right before release. The diagram is idealistic, increment of coding as soon as it is finished. An
because it gives the impression there is as much iteration might be as short as one week, or as
time for testing as there is for coding. In many long as a month. The team builds and tests a little
projects, this is not the case. The testing gets bit of code, making sure it works correctly, and
“squished” because coding takes longer than then moves on to next piece that needs to be
expected, and because teams get into a code- built. Programmers never get ahead of the
and-fix cycle at the end. testers, because a story is not “done” until it has
been tested.
Tests are usually created from a requirements Rather than creating tests from a requirements
document. document that was created by business analysts
before anyone ever thought of writing a line of
code, someone will need to write tests that
illustrate the requirements for each story days or
hours before coding begins.
http://qtp.blogspot.com 7
8. Role Testers Play
The role of the tester with agile methods is an area that has received increasing attention.
Initially with a focus on unit testing and „acceptance‟ testing it appeared the system tester
did not have a role in agile.
Unit Testing
Acceptance
Testing & System Testers are no longer
required?
Typical responsibilities for testers in agile can include (not limited to):
As Cem Kaner put it:
„The nature of the tester's role
changes in iterative projects. • Facilitate communication between the technical & business stakeholders
1
We are no longer the high-
profile victims, we are no 2
• Support early validation of requirements
longer the lonely advocates of
quality, we are merely (!) • Help the business stakeholders define acceptance criteria
3
competent service
providers, collaborating with a • Create automated acceptance tests
group that wants to achieve 4
high quality.‟
• Perform manual/exploratory tests on early-stage code
http://qtp.blogspot.com 8
5
10. It comes as no surprise to testers that
working software is not the same as code –
the tester clearly needs to be involved in not
only assessing the product, but in deciding
how the product is to be assessed.
However, with automated unit tests in the
hands of the coders, and confirmation-
focused acceptance testing driven by the
customer, testers should be aware that they
will not be the sole – or even the primary –
owner of deciding what works, and what
doesn‟t.
http://qtp.blogspot.com 10
11. Testers need to be able to interact directly
with designers and coders to understand the
technological imperatives and restrictions that
affect the software and its unit tests.
Conversations and shared
understandings
Overall less
documentation
will take the required
place of
some documentation http://qtp.blogspot.com 11
12. Testing will be driven by what is important to a user, rather than to
fulfill a procedural requirement. It is better to have communication
between tester, customer and designer than to maintain
independence of the test team.
In practice, it is common to find large-scale automated unit
testing on agile projects, to confirm that code works as expected.
The product will be judged by the customer typically by
manual, confirmatory tests, with close observation for
undesirable behaviors. Testing by testers is often driven by the
need to measure the system‟s performance and to find surprises
– tools are very much in evidence, but rigid test scripts and
procedures do not give the requisite opportunity for
discovery, diagnosis and exploitation.
http://qtp.blogspot.com 12
13. Testers are key collaborators with the customer, and on
some agile projects will take on much of the role of the
customer in designing and executing confirmation-driven
acceptance tests. However, although testers traditionally
make good customer advocates, working closely with a
customer is preferable to becoming a proxy.
Test strategies which lean heavily on an unchanging set
of requirements (for example: designing and coding tests to be
bought together with code late in the project; prioritizing tests based on
a fixed risk assessment; testing only what has been agreed in the
contract; reporting bugs only against fixed requirements) may be
considered to be fatally flawed in the light of this value.
Iterative collaboration is favored over a negotiated bill of
work.
http://qtp.blogspot.com 13
14. While a developer is coding a task, it is
impossible for a tester to test it (it doesn't
exist yet). What then is the role of a tester
at this point.
http://qtp.blogspot.com 14
15. Testers can prepare their test plans, test
cases, and automated tests for the user
stories before (or while) they are
implemented. This helps the team
discover any inconsistency or ambiguity
in the user stories even before the
developers write any code.
http://qtp.blogspot.com 15
16. The tester could be working with the
customer to fine tune the stories in the
sprint.
http://qtp.blogspot.com 16
17. They can often be involved in designing
the tests that the coder will write to perform
TDD.
http://qtp.blogspot.com 17
18. If the agile team is fairly advanced then the
tester would normally be writing the ATDD
(Acceptance Test Driven Development)
tests. These could be in a tool such as
Fitnesse or Robot Framework or they
could be more advanced ruby tests or
even some other programming language.
Or in some cases, simple record and
playback can often be beneficial for a
small number of tests.
http://qtp.blogspot.com 18
19. They would obviously be writing planning
some exploratory testing scenarios or
ideas.
http://qtp.blogspot.com 19
20. The tricky thing to comprehend sometimes
for the team is that the story does not have
to be complete in order to drop it to the test
stack for testing. For example the coders
could drop a screen with half of the fields
planned on it. The tester could test this
half whilst the other half is being coded
and hence feedback in with early test
results. Testing doesn't have to take place
on "finished" stories.
http://qtp.blogspot.com 20
21. Is the tester now involved in unit testing?
Is this done parallel to black box testing?
http://qtp.blogspot.com 21
22. Don’t do Testers only test code that
Testers Unit Tests passes all of the automated
unit, integration and acceptance
tests, which are all written by
the developers. This split may
be different elsewhere, though;
for example your testers could
be writing automated
acceptance tests.
The whole point of unit tests is to test
the software is correct to avoid wasting
time later down the line. It's all about
instant feedback
http://qtp.blogspot.com 22
23. What does the tester do during a sprint
where primarily infrastructural changes
have been made, that may only be
testable in unit testing?
http://qtp.blogspot.com 23
24. Testers workload will vary between
sprints, but regression tests still need to be
run on these changes...
http://qtp.blogspot.com 24
25. You may also find that having the testers
spend the first couple of days of each sprint
testing the tasks from the previous sprint may
help, however it's better to get them to nail
down the things that the developers are going
to be working on by writing their test plans.
http://qtp.blogspot.com 25
26. Ensure that project or sprint requirements are
clear, measurable and testable. In an ideal
world each requirement will have a fit criterion
written down at this stage. Determine what
information needs to be automatically logged
to troubleshoot any defects.
http://qtp.blogspot.com 26
27. Prepare a project specific test strategy and
determine which QA steps are going to be
required and at which project stages:
integration, stress, compatibility, usability, perf
ormance, beta testing etc. Determine
acceptable defect thresholds and work out
classification system for defect
severity, specify guidelines for defect
reporting.
http://qtp.blogspot.com 27
28. Specify, arrange and prepare test environment:
test infrastructure and mock services as
necessary; prepare test data; write scripts to
quickly refresh test environment when necessary;
establish processes for defect
tracking, communication and resolution; prepare
for recruitment or recruit users for beta, usability
or acceptance testing. Write test scripts.
http://qtp.blogspot.com 28
29. Ideally the tester would be working with the team
and the customer (who by the way, is part of the
team!) to define the planned stories and build in
some good, detailed acceptance criteria. This is
invaluable and can save loads of time later down
the line. The tester could also be learning new
automation techniques, planning test
environments, helping to document the outcome
of the planning.
http://qtp.blogspot.com 29
31. Automation Skills
For automation to -> we need to apply
succeed -> good design practices
a single &
We strive to keep each automated test to
clear purpose
Learn how to evaluate and choose the right tools, so you
can help your team create maintainable automated
regression tests. You can free up time for essential testing
activities such as exploratory testing.
http://qtp.blogspot.com 31
32. Acceptance Test-driven Development
Communication skills and good domain
understanding enable testers to help business
experts give good examples of both desired and
undesired system behavior.
We can turn these examples into tests that
help the programmers understand what code to
write. This is called acceptance test-driven
development, and it is a major step toward
building quality into the code and preventing defects.
http://qtp.blogspot.com 32
33. Learning Styles
auditory learn by
Learning learners listening
Styles visual Learn by
learners see pictures
We all have blind spots that may prevent us from learning or triggers
where we shut down and don‟t hear the message anymore. Keep
your emotional “hot buttons” in mind and focus on what you can learn
from instructors, material, or teammates to enhance your abilities.
Mentors with different backgrounds or from other industries besides
testing and software development might work best with your learning
style. Don‟t limit yourself to coaches, mentors, and instructors who
work specifically in software testing.
http://qtp.blogspot.com 33
34. Learning Resources Examples
Many good software
Testing books
Plenty of free material on the Internet
Resources your peers can provide
Communities of practice are another good place to
find mentors and learn together
Conferences are an obvious way to get a lot of new
ideas in a very short period of time
Mailing lists and social networks
Testing communities, such as Weekend Testers
http://qtp.blogspot.com 34
35. References
• AGILE TESTING A PRACTICAL GUIDE FOR TESTERS AND AGILE
TEAMS by Lisa Crispin & Janet Gregory
• http://sqa.stackexchange.com/questions/1824/the-role-of-a-
software-tester-in-an-agile-environment
• http://searchsoftwarequality.techtarget.com/news/1243805/Role-
of-testing-in-agile-projects
• http://www.kohl.ca/blog/archives/000116.html
• http://www.mcbreen.ab.ca/talks/CAMUG.pdf
• http://newsweaver.ie/qualtech/e_article000847213.cfm?x=b11,0,w
• http://stackoverflow.com/questions/1640911/role-of-testers-in-
agile
• LEARNING FOR AGILE TESTERS, Part 2 by Lisa Crispin and Janet
Gregor, Better Software Magazine Sept/Oct 2011
http://qtp.blogspot.com 35