Presented on Testwarez 2012 (the biggest Polish conference about testing and quality).
If you are interested, please read my article on the same topic: http://pl.coremag.eu/fileadmin/user_upload/redaktion/coremag_pl/Downloads/Core_magazineTestWarez_2012.pdf
Exploratory testing in practice, short story how approach influenced on strategyZbyszek Mockun
This document discusses exploratory testing techniques and how one company implemented exploratory testing. It defines exploratory testing as an approach rather than a technique. The company used exploratory techniques like tours and testing heuristics. Initially, their exploratory testing process lacked structure and traceability. To improve it, they implemented a session-based test management approach. This involved planning testing sessions, taking notes within a tool, and having debrief sessions. It helped provide structure while maintaining the flexibility of exploratory testing. They were then able to measure and audit their exploratory testing more effectively.
Presentation from first Poznań Testing and Quality group meeting. I with Lukasz presented how we build and share knowledge in QA team in Cognifide
Authors: Zbyszek Moćkun, Łukasz Morawski
Learn how agile and test automation interact in the real world
To be presented at Aqua SW Test Automation Open Day at Hi-tech College (http://www.aquasw.com/services_training.php#an2)
Our comprehensive SAP testing solution gives you the confidence that your SAP ERP application will support your business exactly as required from the day of go-live.
Whether you are installing, upgrading or enhancing SAP, Original Software provides the most efficient way of validating that it correctly supports all your mission critical business processes.
"I would recommend this as great way to accelerate an upgrade. It keeps costs down, enables business and project people to spend less time in manual validation, and focuses effort on areas of change. It has reduced risk for Marston’s." Phil Court, Head of Information Systems, Marston’s
- Document all your SAP user processes in detail
- Create detailed proof of testing
- Create training videos for every SAP user task
- Fully automated - zero burden on SAP users or IT
See more at: http://www.origsoft.com/solutions/sap-erp-testing/
Shirly Ronen - rapid release flow and agile testing-asAgileSparks
This document describes a rapid agile release flow with three types of releases:
1. CR or production change requests that upload user stories daily to production for testing without releasing to customers.
2. A business release that takes all CRs and makes them available internally but not yet to customers.
3. A station-customer release that releases a group of features to customers after preparations like documentation.
It discusses splitting production from customer releases, freezing user stories and code at different stages, and performing various tests during the process.
Shirly Ronen - User story testing activitiesAgileSparks
The document discusses testing user stories throughout the development process from planning through deployment. It emphasizes testing early by writing automated unit tests during development. Testers work closely with developers to understand the approach and test in the development environment. This helps find defects early and prevent issues. The goal is to deliver working software through continuous testing, including acceptance criteria, exploratory testing, automation, and regression testing.
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex EnvironmentsAgileSparks
The document discusses challenges in testing complex systems with legacy code and minimal automation. It recommends optimizing testing in agile by:
1) Breaking stories into testable chunks that can flow quickly to testing within sprints.
2) Involving QA early in architecture design to ensure testability.
3) Taking an incremental approach to automating tests for new features while refactoring legacy code.
4) Integrating continuously using a staged approach with independent integration testing.
Evolving the Product Management Process to Match Company GrowthSVPMA
The document discusses evolving a product management process to match company growth. It proposes combining elements of waterfall and agile methodologies. The hybrid approach emphasizes predictability from waterfall with adaptability from agile. It incorporates frequent customer feedback and testing. Project teams work in time boxes to incrementally deliver prioritized features through defined phases like concept, definition, design, development, certification and launch.
Exploratory testing in practice, short story how approach influenced on strategyZbyszek Mockun
This document discusses exploratory testing techniques and how one company implemented exploratory testing. It defines exploratory testing as an approach rather than a technique. The company used exploratory techniques like tours and testing heuristics. Initially, their exploratory testing process lacked structure and traceability. To improve it, they implemented a session-based test management approach. This involved planning testing sessions, taking notes within a tool, and having debrief sessions. It helped provide structure while maintaining the flexibility of exploratory testing. They were then able to measure and audit their exploratory testing more effectively.
Presentation from first Poznań Testing and Quality group meeting. I with Lukasz presented how we build and share knowledge in QA team in Cognifide
Authors: Zbyszek Moćkun, Łukasz Morawski
Learn how agile and test automation interact in the real world
To be presented at Aqua SW Test Automation Open Day at Hi-tech College (http://www.aquasw.com/services_training.php#an2)
Our comprehensive SAP testing solution gives you the confidence that your SAP ERP application will support your business exactly as required from the day of go-live.
Whether you are installing, upgrading or enhancing SAP, Original Software provides the most efficient way of validating that it correctly supports all your mission critical business processes.
"I would recommend this as great way to accelerate an upgrade. It keeps costs down, enables business and project people to spend less time in manual validation, and focuses effort on areas of change. It has reduced risk for Marston’s." Phil Court, Head of Information Systems, Marston’s
- Document all your SAP user processes in detail
- Create detailed proof of testing
- Create training videos for every SAP user task
- Fully automated - zero burden on SAP users or IT
See more at: http://www.origsoft.com/solutions/sap-erp-testing/
Shirly Ronen - rapid release flow and agile testing-asAgileSparks
This document describes a rapid agile release flow with three types of releases:
1. CR or production change requests that upload user stories daily to production for testing without releasing to customers.
2. A business release that takes all CRs and makes them available internally but not yet to customers.
3. A station-customer release that releases a group of features to customers after preparations like documentation.
It discusses splitting production from customer releases, freezing user stories and code at different stages, and performing various tests during the process.
Shirly Ronen - User story testing activitiesAgileSparks
The document discusses testing user stories throughout the development process from planning through deployment. It emphasizes testing early by writing automated unit tests during development. Testers work closely with developers to understand the approach and test in the development environment. This helps find defects early and prevent issues. The goal is to deliver working software through continuous testing, including acceptance criteria, exploratory testing, automation, and regression testing.
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex EnvironmentsAgileSparks
The document discusses challenges in testing complex systems with legacy code and minimal automation. It recommends optimizing testing in agile by:
1) Breaking stories into testable chunks that can flow quickly to testing within sprints.
2) Involving QA early in architecture design to ensure testability.
3) Taking an incremental approach to automating tests for new features while refactoring legacy code.
4) Integrating continuously using a staged approach with independent integration testing.
Evolving the Product Management Process to Match Company GrowthSVPMA
The document discusses evolving a product management process to match company growth. It proposes combining elements of waterfall and agile methodologies. The hybrid approach emphasizes predictability from waterfall with adaptability from agile. It incorporates frequent customer feedback and testing. Project teams work in time boxes to incrementally deliver prioritized features through defined phases like concept, definition, design, development, certification and launch.
Combining Performance Testing And Modelling For Easy Jet.Com V 1.0dannyq
This document discusses combining performance testing and modeling for easyJet.com. It outlines the business context of easyJet relying on its website for 98% of revenue. Challenges with agile development include a narrow testing window. Performance testing identifies defects while modeling predicts performance under scenarios. Testing focuses on highest risk areas. Modeling validates demand and capacity. Benefits include confidence in release decisions.
Segue Manufacturing Services provides custom design, manufacturing, and outsourcing solutions for power and control cabinets, precision electromechanical assemblies, and engineered interconnects. They have over 20 years of experience and facilities in Lowell, MA and Xiamen, China with over 500 employees. Segue offers services from product design through high volume manufacturing and global supply chain management.
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
Shirly Ronen - Documenting an agile defectAgileSparks
This document discusses best practices for documenting defects in an agile environment. It recommends documenting defects at a "just enough" level based on the type of defect and stage in the process. More detailed documentation is needed the further removed the defect reporter is from the developer fixing it. Defects should be traced to user stories and functionality, not modules. The focus should be on functional quality and backlog progress over a big defects list. Short, just-in-time discussions replace big bug meetings.
The document describes the experience of inverting the test pyramid for an organization that provides revenue management systems to hotels. It discusses:
1) Moving from a primarily manual testing approach with many end-to-end UI tests to focusing more on unit and integration tests by designing for testability.
2) This transition helped reduce regression times from months to weeks by grouping tests more efficiently and avoiding duplicative tests.
3) Challenges included dealing with legacy code not designed for testing, mapping acceptance tests across different levels, and building team competencies - but benefits included automation as part of development and improved collaboration.
This document discusses how to bake quality into an agile scrum model. It covers quality driven by scrum practices like short iterations and frequent course corrections. It also discusses quality of requirements, architecture/design, code, verification/testing and maturing the definition of done. Automated testing, code reviews, continuous integration and refactoring are recommended to ensure code quality. Quality is baked in through quality user stories, engineering standards/best practices, exploratory testing and peer reviews.
This document provides an overview of Quality Function Deployment (QFD), a design planning process driven by customer requirements. It discusses:
1. The history and key aspects of QFD including the "House of Quality" matrix and deploying the "Voice of the Customer" throughout the organization.
2. How QFD uses planning matrices at different stages to translate customer requirements into technical requirements, product requirements, process requirements, and control requirements.
3. The objectives of QFD which are to determine the voice of the customer and examine the company's response to customer needs.
QA is dead long live the new QA - Agile Dev and QA Conference IsraelYuval Yeret
So we've gone Agile, we've implemented "Agile Teams". How are organizations dealing with the increased forces of running faster and faster loops from need to delivery? How does it affect how QA people and QA groups look into the future?
The document provides a profile summary of an individual with over 12 years of experience in research and development, operations management, and welding processes. They currently work as a senior manager focusing on welding development and hold various certifications in welding inspection, project management, and safety training. The profile outlines the individual's educational background, areas of expertise, work history, accomplishments, and technical skills.
This document provides an agenda and overview for a webinar on quality coding features in Visual Studio 2012. The webinar will cover new tools for unit testing, code reviews, code analysis, and code clones. It will also review features for quality in requirements, development, and testing such as storyboarding, test environments, and exploratory testing. Attendees are encouraged to join the free webinar to learn about and see demonstrations of these Visual Studio 2012 features for improving code quality.
This document discusses quality systems and processes for building high performance homes. It outlines the goals of making quality practices widely available to builders to improve home performance. Various metrics are presented that show the economic benefits of quality, including reduced costs, higher profits and customer satisfaction. A hotspot process is described as a way to identify, train on and inspect recurring quality issues. Developing quality management systems for new and existing homes is presented as an area for further research.
Quality Coding: What's New with Visual Studio 2012Imaginet
The newest release of Visual Studio 2012 is rich with new tools that enhance standard developer activities. In this session, we’ll review and demonstrate some of these new features, such as Unit Testing, Code Reviews, Code Clones, and other developer tools. Come join us for this free Webinar!
Quality Coding: What’s New with Visual Studio 2012Imaginet
This document provides an agenda for a webinar on quality coding features in Visual Studio 2012. The webinar will review new unit testing, code review, code analysis, and code clone detection tools. It will also cover quality improvements for requirements, manual testing, exploratory testing, and automated testing. Attendees will see demonstrations of features like the unit test runner, code reviews, and exploratory testing in Microsoft Test Manager.
Change agile for XP Days 2012 benelux v1.0Ben Linders
This document discusses using agile principles and methods for change projects. It describes how change projects differ from traditional software development projects and outlines how scrum and other agile frameworks can be adapted for change management. Key aspects covered include defining product owners, release planning, estimating work, and defining "done" for change projects versus software projects.
Agile Project Outsourcing - Dealing with RFP and RFISiddhi
The document discusses an RFP for an agile software development project between a customer and supplier. It includes questions about the supplier's experience with agile methodologies, processes and tools, testing approach, contracting models, resource estimates, and release planning. The supplier is asked to describe their proposed agile project setup and execution strategy, including onsite/offshore team composition and coordination, estimation methodology, and contracting approach. They are also asked to justify their responses and provide substantiation for estimates and plans.
Ravit Danino HP - Roles and Collaboration in AgileAgileSparks
Roles and collaboration have changed in Agile. Entire teams now work together throughout a sprint rather than having separate roles confined to specific phases. The whole team, including developers, business analysts, testers, and documentation specialists, collaborates continuously. They plan iterations together, provide feedback to each other, and ensure code meets quality standards through coffee and end-to-end testing. With Agile, customers also become key enablers by providing early feedback to help shape requirements and the product.
This curriculum vitae summarizes the qualifications and experience of Pradeep Kulkarni. He has over 20 years of experience in quality assurance roles, including supplier quality, customer quality, and plant quality. He holds certifications in areas like Six Sigma Green Belt and aerospace auditing. Kulkarni has worked for automotive companies like Mahindra & Mahindra and diesel engine manufacturer Wartsila India, leading quality teams and implementing quality systems. He aims to reduce defects and drive continuous improvement through tools like Six Sigma, quality audits, and corrective action plans.
The document discusses the importance of documenting processes through detailed process flow charts and SIPOC diagrams for continuous improvement purposes. It states that processes, no matter the complexity, should be documented with an overview process flow chart including details on process steps, inputs/outputs, tools used, and key performance indicators. This documentation forms the basis of a Quality Assurance Plan (QAP) that can be used to increase customer satisfaction, drive process understanding for management, and identify areas for improvement through measurement of process indicators. The document provides an example process flow chart and explains what a SIPOC diagram is and how it can help map the suppliers, inputs, process steps, outputs, and customers of a process.
Presentation from second Poznań Testing and Quality group.
This presentation sum up my experience (about 5 years) with automation, as engineer or manager
Combining Performance Testing And Modelling For Easy Jet.Com V 1.0dannyq
This document discusses combining performance testing and modeling for easyJet.com. It outlines the business context of easyJet relying on its website for 98% of revenue. Challenges with agile development include a narrow testing window. Performance testing identifies defects while modeling predicts performance under scenarios. Testing focuses on highest risk areas. Modeling validates demand and capacity. Benefits include confidence in release decisions.
Segue Manufacturing Services provides custom design, manufacturing, and outsourcing solutions for power and control cabinets, precision electromechanical assemblies, and engineered interconnects. They have over 20 years of experience and facilities in Lowell, MA and Xiamen, China with over 500 employees. Segue offers services from product design through high volume manufacturing and global supply chain management.
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
Shirly Ronen - Documenting an agile defectAgileSparks
This document discusses best practices for documenting defects in an agile environment. It recommends documenting defects at a "just enough" level based on the type of defect and stage in the process. More detailed documentation is needed the further removed the defect reporter is from the developer fixing it. Defects should be traced to user stories and functionality, not modules. The focus should be on functional quality and backlog progress over a big defects list. Short, just-in-time discussions replace big bug meetings.
The document describes the experience of inverting the test pyramid for an organization that provides revenue management systems to hotels. It discusses:
1) Moving from a primarily manual testing approach with many end-to-end UI tests to focusing more on unit and integration tests by designing for testability.
2) This transition helped reduce regression times from months to weeks by grouping tests more efficiently and avoiding duplicative tests.
3) Challenges included dealing with legacy code not designed for testing, mapping acceptance tests across different levels, and building team competencies - but benefits included automation as part of development and improved collaboration.
This document discusses how to bake quality into an agile scrum model. It covers quality driven by scrum practices like short iterations and frequent course corrections. It also discusses quality of requirements, architecture/design, code, verification/testing and maturing the definition of done. Automated testing, code reviews, continuous integration and refactoring are recommended to ensure code quality. Quality is baked in through quality user stories, engineering standards/best practices, exploratory testing and peer reviews.
This document provides an overview of Quality Function Deployment (QFD), a design planning process driven by customer requirements. It discusses:
1. The history and key aspects of QFD including the "House of Quality" matrix and deploying the "Voice of the Customer" throughout the organization.
2. How QFD uses planning matrices at different stages to translate customer requirements into technical requirements, product requirements, process requirements, and control requirements.
3. The objectives of QFD which are to determine the voice of the customer and examine the company's response to customer needs.
QA is dead long live the new QA - Agile Dev and QA Conference IsraelYuval Yeret
So we've gone Agile, we've implemented "Agile Teams". How are organizations dealing with the increased forces of running faster and faster loops from need to delivery? How does it affect how QA people and QA groups look into the future?
The document provides a profile summary of an individual with over 12 years of experience in research and development, operations management, and welding processes. They currently work as a senior manager focusing on welding development and hold various certifications in welding inspection, project management, and safety training. The profile outlines the individual's educational background, areas of expertise, work history, accomplishments, and technical skills.
This document provides an agenda and overview for a webinar on quality coding features in Visual Studio 2012. The webinar will cover new tools for unit testing, code reviews, code analysis, and code clones. It will also review features for quality in requirements, development, and testing such as storyboarding, test environments, and exploratory testing. Attendees are encouraged to join the free webinar to learn about and see demonstrations of these Visual Studio 2012 features for improving code quality.
This document discusses quality systems and processes for building high performance homes. It outlines the goals of making quality practices widely available to builders to improve home performance. Various metrics are presented that show the economic benefits of quality, including reduced costs, higher profits and customer satisfaction. A hotspot process is described as a way to identify, train on and inspect recurring quality issues. Developing quality management systems for new and existing homes is presented as an area for further research.
Quality Coding: What's New with Visual Studio 2012Imaginet
The newest release of Visual Studio 2012 is rich with new tools that enhance standard developer activities. In this session, we’ll review and demonstrate some of these new features, such as Unit Testing, Code Reviews, Code Clones, and other developer tools. Come join us for this free Webinar!
Quality Coding: What’s New with Visual Studio 2012Imaginet
This document provides an agenda for a webinar on quality coding features in Visual Studio 2012. The webinar will review new unit testing, code review, code analysis, and code clone detection tools. It will also cover quality improvements for requirements, manual testing, exploratory testing, and automated testing. Attendees will see demonstrations of features like the unit test runner, code reviews, and exploratory testing in Microsoft Test Manager.
Change agile for XP Days 2012 benelux v1.0Ben Linders
This document discusses using agile principles and methods for change projects. It describes how change projects differ from traditional software development projects and outlines how scrum and other agile frameworks can be adapted for change management. Key aspects covered include defining product owners, release planning, estimating work, and defining "done" for change projects versus software projects.
Agile Project Outsourcing - Dealing with RFP and RFISiddhi
The document discusses an RFP for an agile software development project between a customer and supplier. It includes questions about the supplier's experience with agile methodologies, processes and tools, testing approach, contracting models, resource estimates, and release planning. The supplier is asked to describe their proposed agile project setup and execution strategy, including onsite/offshore team composition and coordination, estimation methodology, and contracting approach. They are also asked to justify their responses and provide substantiation for estimates and plans.
Ravit Danino HP - Roles and Collaboration in AgileAgileSparks
Roles and collaboration have changed in Agile. Entire teams now work together throughout a sprint rather than having separate roles confined to specific phases. The whole team, including developers, business analysts, testers, and documentation specialists, collaborates continuously. They plan iterations together, provide feedback to each other, and ensure code meets quality standards through coffee and end-to-end testing. With Agile, customers also become key enablers by providing early feedback to help shape requirements and the product.
This curriculum vitae summarizes the qualifications and experience of Pradeep Kulkarni. He has over 20 years of experience in quality assurance roles, including supplier quality, customer quality, and plant quality. He holds certifications in areas like Six Sigma Green Belt and aerospace auditing. Kulkarni has worked for automotive companies like Mahindra & Mahindra and diesel engine manufacturer Wartsila India, leading quality teams and implementing quality systems. He aims to reduce defects and drive continuous improvement through tools like Six Sigma, quality audits, and corrective action plans.
The document discusses the importance of documenting processes through detailed process flow charts and SIPOC diagrams for continuous improvement purposes. It states that processes, no matter the complexity, should be documented with an overview process flow chart including details on process steps, inputs/outputs, tools used, and key performance indicators. This documentation forms the basis of a Quality Assurance Plan (QAP) that can be used to increase customer satisfaction, drive process understanding for management, and identify areas for improvement through measurement of process indicators. The document provides an example process flow chart and explains what a SIPOC diagram is and how it can help map the suppliers, inputs, process steps, outputs, and customers of a process.
Presentation from second Poznań Testing and Quality group.
This presentation sum up my experience (about 5 years) with automation, as engineer or manager
Project quality (and test process) metricsZbyszek Mockun
The document discusses project quality and testing process metrics. It describes various types of metrics that can be used, including code quality, test case execution, requirement coverage, bugs, defect density, and automation coverage metrics. The document emphasizes that metrics should be used to control processes, risks, and encourage good practices, but people and processes are also important. Visualizing metrics and finding the right level of detail are also discussed.
automated exploratory test tools for web application. Make your test agile. Do not overpay for your automation. Test all aspects (performance, layout, analytic) not only concentrate on one specific thing.
Test automation lessons from WebSphere Application ServerRobbie Minshall
The document discusses WebSphere testing at IBM. It provides an overview of IBM's:
- Extensive testing resources including over 200 engineers and thousands of systems.
- Daily regression testing of over 1.7 million tests.
- Transition from waterfall to agile development which reduced cycle times and resources needed for testing.
- Use of cloud resources to speed up test deployment and automation.
- Focus on creating meaningful regressions through techniques like integration acceptance tests run continuously on each build.
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included:
1) Comparing waterfall vs agile testing approaches in areas like test requirements, strategy, team structure and test automation.
2) Outlining a testing checklist using the "5 Ws and 2 Hs" (Why, What, When, Who, Where, How, How Long) to plan testing.
3) Discussing trade-off considerations around testing scope, resources and quality goals.
4) Describing the software testing ecosystem involving various stakeholders.
5) Emphasizing the importance of root cause analysis (RCA) at different
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included:
1) Comparing waterfall vs agile testing approaches. Agile testing focuses on incremental requirements, test strategies, and collaborative teams.
2) Using the "5 Ws and 2 Hs" (why, what, when, where, who, how, how long) as a testing checklist.
3) Discussing tradeoffs around test scope, resources, defects, and timelines that require risk mitigation.
4) Describing a software testing ecosystem with various stakeholders involved in development, management, testing, and more.
5) Emp
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
This document discusses key lessons for leadership in test and QA professions. It covers: 1) Differences between waterfall and agile testing approaches. 2) Using a testing checklist of 5 Ws and 2 Hs. 3) Tradeoffs involved in testing economics and scope. 4) The software testing ecosystem involving various stakeholders. The overall message is on adapting testing strategies to agile environments while maintaining quality.
Vaidyanathan Ramalingam presented key lessons on software testing for test and QA professionals. Some of the highlights included:
1) Comparing waterfall vs agile testing approaches. Agile testing focuses on incremental requirements, test strategies, and collaborative teams.
2) Using the "5 Ws and 2 Hs" (why, what, when, where, who, how, how long) as a testing checklist.
3) Discussing tradeoffs around test scope, resources, defects, and timelines that require risk mitigation.
4) Describing a software testing ecosystem with various stakeholders involved in development, management, testing, and more.
5) Emp
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Flexing your Agile Muscle - Agile Technical Concepts ExplainedSandy Mamoli
Continuous integration, acceptance test driven development (ATDD), specification by example and continuous deployment: The list of have-to-know concepts is growing and you have this nagging feeling that you should really get started so you won’t miss out on the fun.
Learn what basic Agile technical concepts mean, understand how you can benefit from using them and get ideas for how you might get started. Also, you will be able to explain to your boss or project manager why Agile technical concepts are well worth the investment.
This session will keep things on a strictly conceptual level - so whether you’re a developer or an interested manager please come along.
Similar to Between Scrum and Kanban - define test process for Agile methodologies (20)
Thinking of getting a dog? Be aware that breeds like Pit Bulls, Rottweilers, and German Shepherds can be loyal and dangerous. Proper training and socialization are crucial to preventing aggressive behaviors. Ensure safety by understanding their needs and always supervising interactions. Stay safe, and enjoy your furry friends!
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
Executive Directors Chat Leveraging AI for Diversity, Equity, and InclusionTechSoup
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
Dynamic changes in projects (suite your process to actual needs) – ex. When client not deliver requriements/not answer on question you can’t plan sprint, so you can’t use scrum
Musielismy sie zmierzyc z wizualizacja stanu projektu za pomoca taskboarda. Minimalizacja raportow QA, jak informowac o statusie testow na biezaca – integracja z taskboardemJak dobrze zarzadzac testami eksploracyjnymiJak zarzadzac statusami nowych funkcjonalnosciStatus pracy qa na taskboardzie – czyli w tym samym miejscu gdzie i status pracy reszty zespoluProject status on TaskboardStatus of all tasks visualised on Taskboard for client/ PMNo need of additional reportsQA ReportsRemove the need of qa reportsVisualistion issue state incliding testingVisualisation QA activitiesOne tool – how to repleace Test Case Management reportsHow to manage exploratory testingHow to manage issues status according to visualisationDefine QA role in projectsDefine the place of qa in our processOne process for different methodologies: Scrum, Scrum-approach, KanbanMeasure the quality and qa workScripting doesn’t work
Kiedy konczymy prace – czy mozemy polegac na kliencie.W Scrum, aby skonczyc sprint wszystkie itemy musza trafic w stan Done, ciezko tutaj polegac na kliencie.Sprint konczy sie demo, po ktorym klient robi sign off, niestety czest jest niedostepny lub nie czeka z sing off, wiec chcemy sie pozbyc tej zmiennejdo czesci z funkcjonalnosci dodaje poprawkiStan done w naszym wypadku jest ostatnim na po prawej stronie w taskboard, aby latwo klient widzial co czeka na niego. Jesli klient naprawde wspolpracuje, to dodajemy oczywiscie kolumne sign off.W Kanbanie nie jest to juz konieczne, nie mamy ograniczenia czasoweg, mozemy spokojnie czekac
Tutaj kilka slow dlaczego jest wazne aby qa byl kolejny stanem w etapie wytwarzania oprogramowani. Standrdowe workflowy niestety ich nie maja u musimy je edytowac
Zmieniaj tylko te czesci ktore nie sa widocznie dla klientow, nie wymagaja ich udzialu jesli to mozliwe
Jak rozroznic taski, dlaczego dla niektorych warto uproscic workflowy, punkt widzenia – czy mamy klienta dla taska czy niSingle – czyli bez klienta, jestesmy sami sobie klientem, np dzielimy prace na pewne kawalki – na przyklad takie jakie mozemy zrobic przez jeden dzien – planowanie pracy.- Client oriented – czyli takie ktore wymagaja wspolrpacy z roznymi rolami, nie zawsze to qa musi zaakceptowac taski, moze to byc technical lead, project manager, analityk, ...
Obrazek do poprawy,Cykl zycia softwaru – blecy akceptacji podczas wytwarzania funkcjonalnosci, bledy regresyjne sa dla juz oddanej funkcjonalnosci
Regresyjne – standard issue type (czyli dla rzeczy ktore juz skonczylismy – patrz slajd o Done)Akceptacyjne sub issue type, zawsze pod funkcjonalnoscia dla ktorej byly znalezione
Sub issue as failed test scenario (usuniete, ale rowniez wazne)
Dlaczego warto miec scisly proces i furtkeCzyli o wypinaniu i konwersji do standard issue typeesionCzy naprawde musimy wszystko naprawiac, moze czesc zechcemy naparwic pozniej, wiec zmienmy je z akceptance na reg
Przypomnijmy ze story posiada zawsze cala historie pod soba- All failed issues attached to storyHelicopter view - Zawsze patzym an calosc a nie czastkeQa testuje tylko story, gdy juz cale jest naprawione, testownaie pomniejszych rzeczy nie ma sensu:Przelaczanie sie miedzy wieloma funkcjonalnosciami nie jest efektywnieWplyw wprowadzonych zmian na reszte funkcjonalnosciPotrzebujemy retetowac cala funkcjonalnosc, czy nie? Decyzja do qa co tak naprawde musimy powtorzyc
Klienta interesuje ostateczny status, czy cos zostalo skonczone, lub w jakim miejscu sie znajduje, nie interesuje go ilosc skryptow testowych, ktore przeszy, ktore nie, tylko czy funkcjonalnosc jest gotowa czy nie. Praktycznie zaden PM czy klient mimo dostepu do narzedzi zarzadzania testami tam nie zagladal, zawsze wymagali oddzielnych raportow, na prosbe klienta, zawsze byl potrzebny test amnager ktory przedstawial dodatkowe stanyGoogle wygralo bo poprostu zwracala informacje ktore szukalismy. Tak samo u nas z taskboard. Jedno miejsce ktore dostarcza tego czego potrzebujemyAcceptance issues are hidden – widzimy jedynie ich liczbe dla konkretnergo taska - ale to juz konfiguracja
Skrypting nie dziala, nie chcemy tak pracowac jednak:Musimy informowac jakos o statusie funkcjonalnosciZarzadzac testami automatycznymiZarzadzac testami regresjiDostarczac skrypty testowe dla klienta – wykonywane przez nich w czasie UATScripting nie sprawdza sie w testach akceptacyjnych, gdy poznajemy aplikacje – chcemy ja poznawac tak jak nasz uzytkownik, mamy problem ze znalezieniem statusu funkcjonalnosci bo jest rozbity, zawsze sa jakies bledy z jirze mimo 100% wykonalnosci testowBardzo wazne tutaj. Poniewz ccemy szybko wykrywac bledy, mamy testowanie ciagle, tak naprawde nie ma czasu na scripting creation in advance
Raport wykoania testow nie mial sensu, nigdy nie bylismy w stanie napisac ile, ..Liczby klamalyUsuniete ze slajdow, ale warto wspomniec: -Infinite space in finite time - Manage your tests depends on timeMimo 100% egzekucji i tak trzba bylo sprawdzac status w 2 miejscach jira i qmetryOddzielne jiryStatus wymagan – ciezko bylo go znalesc, czy polaczyc go – JIRA – test Case managemen tool, zeby autoamtycznie sie updatetowalCo ma retestowc 0 tylko testy ktore poszly failedCo jesli zostala przepisana czesc funkcjonalnosci jeszcze raz wykonac testy ktore byly pass (jesli to zrobie z raportu wyjdzie ze nic nie zrobilem tego dnia)Opowiadanie czeczkaNot all issues assigned to test case4 failed tests – 6 issues assigned10 more issues in JIRA without test scenarion in test runAutomated tests in scope or not (CI)
Ciag dalszy poprzedniego slajduTesty eksploracyjne okazaly sie lepsze bo daja wieksza mozliwosc zarzadzania testerom, szczegolnie przy akceptaycjnych, retescie, oszczedzaja czas, sa wydajniejsze, koncentruja sie na calej funkcjonalnosci, a nie konkretnym przypadku testowym. Ich wyniki sa tez bardziej miarodajne i mowia wiecej. Latwiej je tez planowac jesli jestesmy ograniczni czasem, wykryc najbardziej krytyczne bledy najszybciej. Czy tez uczyc sie z uzytkownikiemAgile manifesto – postawienie na czlowieka, jego wiedze i doswiadzcenie, to on podejmuje decyzje, no i mozliwosc zarzadzania czasem –dostosowanie poziomu testow do mozliwosci czasowych
Heuristics, TestingDojos, SessionBasedTesting, CrossTesting, Checklists, RapidTesting, Tools, Context-Aware, DomainKnowledgeTesting Dojos – pair testing, work with othere, learn from themCross Testing – not pair testing but the idea that the same part should be tested by two testers / one after another. review other works, check what he find, talk and compare results. Different testers may be sensitive to differentfactors, or make different observations. The same tester may see different things atdifferent times or when intentionally shifting focus to different things.
Inne spojrzenie na metryki - 2 lata temu jedna z przentacjina testwarez byla o metrykach, rpzeczytalem wiele artylulow, jednak nigdzie nie znalezlem nic o tych ktore sa dla mnie najwazniejsze.
Qa do not improve quality, so measure on qa level .
Screen z metryka – szybkosc qa zalezy od jakosci jaka dostajemhy. Jest to tak naprade suma wszelkich testow jak i retestow. Czyli jesli cos dostaniemy zlego, odrzucimy to kilka razy, to nasza efektywnosc jest roznie mierzonaManager – przetestowaliscie tylko jedno storyQA przetestowalismy 4 story (za jazdtm razem to samo), ale za kazdym razem dostawalismy je z bledem