The document discusses how agile development and continuous deployment disrupt traditional functional testing processes. It describes how testing practices have evolved from waterfall development with long release cycles to frequent daily releases. This requires testing to be more automated, with practices like acceptance testing driven development (ATDD) where testing defines requirements and drives the engineering process. It presents a cloud-based platform for ATDD that supports collaboration and test management integration.
Synthesizing Continuous Deployment Practices in Software DevelopmentAkond Rahman
Continuous deployment speeds up the process of existing agile methods, such as Scrum, and Extreme Programming (XP) through the automatic deployment of software changes to end-users upon passing of automated tests. Continuous deployment has become an emerging software engineering process amongst numerous software companies, such as Facebook, Github, Netflix, and Rally Software. A systematic analysis of software practices used in continuous deployment can facilitate a better understanding of continuous deployment as a software engineering process. Such analysis can also help software practitioners in having a shared vocabulary of practices and in choosing the software practices that they can use to implement continuous deployment. The goal of this paper is to aid software practitioners in implementing continuous deployment through a systematic analysis of software practices that are used by software companies. We studied the continuous deployment practices of 19 software companies by performing a qualitative analysis of Internet artifacts and by conducting follow-up inquiries. In total, we found 11 software practices that are used by 19 software companies. We also found that in terms of use, eight of the 11 software practices are common across 14 software companies. We observe that continuous deployment necessitates the consistent use of sound software engineering practices such as automated testing, automated deployment, and code review.
Unit testing involves writing code to test individual units or components in isolation to determine if they are functioning as expected. Writing tests first, before production code (test-driven development or TDD) can lead to higher quality code, easier debugging, and increased confidence in changes. The TDD process involves writing a failing test, then code to pass the test, and refactoring code as needed. To apply TDD effectively, tests should focus on logical code, avoid duplications, and isolate dependencies to keep tests simple and maintainable. Both server-side and client-side code need testing, focusing on things like business rules, view models, repositories, and UI logic.
The document discusses testing concepts such as code with tests vs without tests, test-oriented development, and different types of testing including unit testing, integration testing, and acceptance testing. It provides examples of test-driven development (TDD) and behavior-driven development (BDD) processes. The document also discusses tips for testing, including only testing what is necessary and identifying the appropriate types of testing for an application. Frameworks and tools for test automation and continuous integration are also mentioned.
Istqb intro with question answer for exam preparationKevalkumar Shah
The document provides an overview of software testing concepts including definitions of software testing, who can perform testing, common terminology, the software development life cycle (SDLC), testing methods and levels, and more. It defines software testing as the process of comparing expected and actual results to identify defects. It outlines the typical stages of the SDLC as initial, analysis, design, coding, testing, and delivery/maintenance phases. It also describes black box, white box, and grey box testing methods and the five levels of testing: unit, module, integration, system, and acceptance.
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
TOPS Technologies offer Professional Software Testing Training in Ahmedabad.
Ahmedabad Office (C G Road)
903 Samedh Complex,
Next to Associated Petrol Pump,
CG Road,
Ahmedabad 380009.
http://www.tops-int.com/live-project-training-software-testing.html
Most experienced IT Training Institute in Ahmedabad known for providing software testing course as per Industry Standards and Requirement.
Capital One DevOps Case Study: A Bank with the Heart of Tech CompanySimform
Many organizations want to adopt DevOps to work their way through digital transformation. This case study of Capital One's journey of adopting DevOps and what distinctive tools and methods they introduced to stay ahead of the competition.
This document discusses software engineering and software testing. Software engineering is concerned with developing large software through applying engineering principles. The challenge is to produce high quality software within budget and schedule constraints. Software testing is the process of finding errors in software and involves both manual and automated testing. Different types of testing include unit, integration, system, and acceptance testing. The goal of testing is to uncover defects early and reduce costs.
Synthesizing Continuous Deployment Practices in Software DevelopmentAkond Rahman
Continuous deployment speeds up the process of existing agile methods, such as Scrum, and Extreme Programming (XP) through the automatic deployment of software changes to end-users upon passing of automated tests. Continuous deployment has become an emerging software engineering process amongst numerous software companies, such as Facebook, Github, Netflix, and Rally Software. A systematic analysis of software practices used in continuous deployment can facilitate a better understanding of continuous deployment as a software engineering process. Such analysis can also help software practitioners in having a shared vocabulary of practices and in choosing the software practices that they can use to implement continuous deployment. The goal of this paper is to aid software practitioners in implementing continuous deployment through a systematic analysis of software practices that are used by software companies. We studied the continuous deployment practices of 19 software companies by performing a qualitative analysis of Internet artifacts and by conducting follow-up inquiries. In total, we found 11 software practices that are used by 19 software companies. We also found that in terms of use, eight of the 11 software practices are common across 14 software companies. We observe that continuous deployment necessitates the consistent use of sound software engineering practices such as automated testing, automated deployment, and code review.
Unit testing involves writing code to test individual units or components in isolation to determine if they are functioning as expected. Writing tests first, before production code (test-driven development or TDD) can lead to higher quality code, easier debugging, and increased confidence in changes. The TDD process involves writing a failing test, then code to pass the test, and refactoring code as needed. To apply TDD effectively, tests should focus on logical code, avoid duplications, and isolate dependencies to keep tests simple and maintainable. Both server-side and client-side code need testing, focusing on things like business rules, view models, repositories, and UI logic.
The document discusses testing concepts such as code with tests vs without tests, test-oriented development, and different types of testing including unit testing, integration testing, and acceptance testing. It provides examples of test-driven development (TDD) and behavior-driven development (BDD) processes. The document also discusses tips for testing, including only testing what is necessary and identifying the appropriate types of testing for an application. Frameworks and tools for test automation and continuous integration are also mentioned.
Istqb intro with question answer for exam preparationKevalkumar Shah
The document provides an overview of software testing concepts including definitions of software testing, who can perform testing, common terminology, the software development life cycle (SDLC), testing methods and levels, and more. It defines software testing as the process of comparing expected and actual results to identify defects. It outlines the typical stages of the SDLC as initial, analysis, design, coding, testing, and delivery/maintenance phases. It also describes black box, white box, and grey box testing methods and the five levels of testing: unit, module, integration, system, and acceptance.
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
TOPS Technologies offer Professional Software Testing Training in Ahmedabad.
Ahmedabad Office (C G Road)
903 Samedh Complex,
Next to Associated Petrol Pump,
CG Road,
Ahmedabad 380009.
http://www.tops-int.com/live-project-training-software-testing.html
Most experienced IT Training Institute in Ahmedabad known for providing software testing course as per Industry Standards and Requirement.
Capital One DevOps Case Study: A Bank with the Heart of Tech CompanySimform
Many organizations want to adopt DevOps to work their way through digital transformation. This case study of Capital One's journey of adopting DevOps and what distinctive tools and methods they introduced to stay ahead of the competition.
This document discusses software engineering and software testing. Software engineering is concerned with developing large software through applying engineering principles. The challenge is to produce high quality software within budget and schedule constraints. Software testing is the process of finding errors in software and involves both manual and automated testing. Different types of testing include unit, integration, system, and acceptance testing. The goal of testing is to uncover defects early and reduce costs.
The document discusses key concepts in software testing and quality analysis from the viewpoint of customers and producers. It defines bugs and errors, and outlines common causes like complexity, changing requirements, and time pressure. Testing aims to discover faults and weaknesses through execution with the intent of finding errors. The document also mentions software development lifecycles like waterfall model and V-model, as well as standards organizations. It stresses finding and fixing defects early to improve quality.
Types of Software Testing: Definition, Objectives and AdvantagesSimform
Software testing is a crucial part of the development process. This presentation gives you a glimpse of different types of testing, their objectives, and their advantages.
The document discusses various types of software testing concepts including manual vs automated testing, test beds, test data, positive and negative test cases, defect priority and severity levels, test plans, security and recovery testing, and more. It provides definitions and explanations of these key testing concepts.
Basically this slid will help to Learn software quality testing on scratch level.
Software testing is the quality measures conducted to provide stakeholders with information about the quality of the product or service. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It is an important part of the entire Software Development ensuring that the functionalities of the system are tested to the finest and assures the quality, correctness and completeness of the product. Software testing, depending on the testing method employed, can be implemented at any time in the development process.
Stages of testing:
o Test planning
o Test Analysis
o Test verification & Construction
o Test execution
o Defect tracking and management
o Quality Analysis Bug tracking
o Report
o Final testing & implementation
The document introduces various agile test tools. It begins by explaining how agile methodologies like Scrum differ from traditional development in requiring testing throughout the process. It then defines terms like test-driven development, acceptance testing, and behavior-driven development. The bulk of the document describes test tools in two categories: those that describe requirements and tests using domain-specific languages, and those for executing tests. Tools covered include RSpec, FIT, FitNesse, Cucumber, Robot Framework, Selenium, and others. Advantages of agile test tools are discussed, along with challenges to adopting new tools and techniques. Links and books for further resources are provided at the end.
The document provides an overview of the ISTQB Agile Tester certification. It begins by comparing traditional waterfall software development methodology to agile methodology. With waterfall, requirements are gathered upfront and the customer only sees the final product, while with agile development is iterative with working software delivered in short iterations. An example compares developing a word processing competitor under the two methodologies. The rest of the document outlines agile principles, practices for testing in agile, roles of testers, agile testing techniques and tools.
Everything You Need to Know About Unit Testing in Test Driven Development (TDD) with Case Studies!
TDD can be defined as a programming practice that instructs developers to write new code only if an automated test has failed. This avoids duplication of code.
The primary goal of TDD is to make the code clearer, simple and bug-free.
This PDF contains the case studies of Test Driven Development. Special thanks to the Experts- Jeff Langr, Frederico Gonçalves and J. B. Rainsberger for their valuable comments!
These case studies are the part of our blog on "How to do Unit Testing in Test Driven Development(TDD)?" which covers the following topics-
1) What is Unit Testing?
2) What is Test-Driven Development (TDD)?
3) Example of TDD with Unit Tests
4) Best Practices for Writing Unit Tests
5) Benefits of Unit Testing
6) Limitations of Unit Testing in the Traditional Approach
7) Case Studies of TDD
Blog Link-
https://www.simform.com/unit-testing-tdd/#casestudies
The document outlines a test plan for a Waste Management Inspection Tracking System (WMITS) software. It includes sections on test scope and objectives, interfaces to be tested, testing strategies including unit, integration, validation and high-order testing, a test schedule, and resources and staffing. The testing aims to minimize bugs and defects by thoroughly testing all components, functions, and the integrated system prior to release.
Testing is the process of evaluating a system or its components to find whether it satisfies specified requirements. Testing is generally done by software testers, developers, project managers, and end users. There are different types of testing like unit testing, integration testing, system testing, and acceptance testing. Testing is performed at various stages of the software development life cycle to verify that the system is built correctly and meets requirements.
The document discusses various topics related to technical interview questions for software testing. It covers software testing basics like the PDCA cycle and different testing types (white box, black box, gray box). It also discusses usability testing, defect categories, defining a testing policy, preparing acceptance plans, configuration management, code coverage tools, and different testing models. Key software development phases like design, coding, and their relative defect rates are examined. The roles of different testing teams and how test documents span the SDLC are outlined. Common testing concepts like test cases, logs, traceability, entry/exit criteria, verification vs validation are defined.
Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Top 50 Software Testing Interview Question and Answers will help you to prepare yourself for Software Testing Interviews. It covers questions for beginners, intermediate and experienced professionals.
Below topics are covered in this PPT:
Market Trends in Software Testing
What is Software testing
Top 50 interview questions
1. Beginners level questions
2. Intermediate level questions
3. Advance level questions
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
The document discusses testing best practices for rich client applications. It outlines the challenges of testing user interfaces and interactions. It then describes different levels of testing from ad hoc to crowdsourcing. Unit testing, continuous integration, and automated functional testing are explained. The current state of testing tools for Titanium is presented along with a demo. Future directions including more automation and crowdsourced testing are envisioned.
To be able to effectively and sustainably test in Agile projects the test activities must be properly integrated in the Agile approach. To be efficient and effective automation is essential. In this webinar Rik will cover subjects like Footholds for testing from the Manifesto, the role of Product Owner, Scrum Master and Agile team members, Test Strategy and Test Levels (e.g. E2E-testing), TMap & ISTQB (Agile Extension) and DevOps.
Key Takeaways:
1) Be adaptive
2) Use a risk-based approach
3) Testing activities must be automated as much as possible
www.eurostarconferences,com
http://testhuddle.com/resource/integrate-test-activities-in-agile/
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
This document provides an overview of fundamentals of software testing. It discusses the five parts of the fundamental test process in broad chronological order: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and test closure activities. It also covers topics like regression testing, confirmation testing, the differences between re-testing and regression testing, and the importance of independence in testing.
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
It's a 1st Unit PPT of Subject Software Testing & Quality from the Book "Software Testing & Quality Assurance" by Kshirsagar Naik and Priyadarshi Tripathy
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Effective Testing Practices in an Agile EnvironmentRaj Indugula
This is a practitioner’s view of testing and testing practices within an iterative development environment. We will explore the challenges of testing within such an environment and ways to better integrate the QA professional into what is inherently a developer-centric methodology. If quality is paramount, then we ought to move testing to the front of the line and test early and often. Automation lies at the heart of agility and we will look at how test automation techniques and test-first design philosophy might be applied at multiple-levels to drive quality.
The document discusses key concepts in software testing and quality analysis from the viewpoint of customers and producers. It defines bugs and errors, and outlines common causes like complexity, changing requirements, and time pressure. Testing aims to discover faults and weaknesses through execution with the intent of finding errors. The document also mentions software development lifecycles like waterfall model and V-model, as well as standards organizations. It stresses finding and fixing defects early to improve quality.
Types of Software Testing: Definition, Objectives and AdvantagesSimform
Software testing is a crucial part of the development process. This presentation gives you a glimpse of different types of testing, their objectives, and their advantages.
The document discusses various types of software testing concepts including manual vs automated testing, test beds, test data, positive and negative test cases, defect priority and severity levels, test plans, security and recovery testing, and more. It provides definitions and explanations of these key testing concepts.
Basically this slid will help to Learn software quality testing on scratch level.
Software testing is the quality measures conducted to provide stakeholders with information about the quality of the product or service. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It is an important part of the entire Software Development ensuring that the functionalities of the system are tested to the finest and assures the quality, correctness and completeness of the product. Software testing, depending on the testing method employed, can be implemented at any time in the development process.
Stages of testing:
o Test planning
o Test Analysis
o Test verification & Construction
o Test execution
o Defect tracking and management
o Quality Analysis Bug tracking
o Report
o Final testing & implementation
The document introduces various agile test tools. It begins by explaining how agile methodologies like Scrum differ from traditional development in requiring testing throughout the process. It then defines terms like test-driven development, acceptance testing, and behavior-driven development. The bulk of the document describes test tools in two categories: those that describe requirements and tests using domain-specific languages, and those for executing tests. Tools covered include RSpec, FIT, FitNesse, Cucumber, Robot Framework, Selenium, and others. Advantages of agile test tools are discussed, along with challenges to adopting new tools and techniques. Links and books for further resources are provided at the end.
The document provides an overview of the ISTQB Agile Tester certification. It begins by comparing traditional waterfall software development methodology to agile methodology. With waterfall, requirements are gathered upfront and the customer only sees the final product, while with agile development is iterative with working software delivered in short iterations. An example compares developing a word processing competitor under the two methodologies. The rest of the document outlines agile principles, practices for testing in agile, roles of testers, agile testing techniques and tools.
Everything You Need to Know About Unit Testing in Test Driven Development (TDD) with Case Studies!
TDD can be defined as a programming practice that instructs developers to write new code only if an automated test has failed. This avoids duplication of code.
The primary goal of TDD is to make the code clearer, simple and bug-free.
This PDF contains the case studies of Test Driven Development. Special thanks to the Experts- Jeff Langr, Frederico Gonçalves and J. B. Rainsberger for their valuable comments!
These case studies are the part of our blog on "How to do Unit Testing in Test Driven Development(TDD)?" which covers the following topics-
1) What is Unit Testing?
2) What is Test-Driven Development (TDD)?
3) Example of TDD with Unit Tests
4) Best Practices for Writing Unit Tests
5) Benefits of Unit Testing
6) Limitations of Unit Testing in the Traditional Approach
7) Case Studies of TDD
Blog Link-
https://www.simform.com/unit-testing-tdd/#casestudies
The document outlines a test plan for a Waste Management Inspection Tracking System (WMITS) software. It includes sections on test scope and objectives, interfaces to be tested, testing strategies including unit, integration, validation and high-order testing, a test schedule, and resources and staffing. The testing aims to minimize bugs and defects by thoroughly testing all components, functions, and the integrated system prior to release.
Testing is the process of evaluating a system or its components to find whether it satisfies specified requirements. Testing is generally done by software testers, developers, project managers, and end users. There are different types of testing like unit testing, integration testing, system testing, and acceptance testing. Testing is performed at various stages of the software development life cycle to verify that the system is built correctly and meets requirements.
The document discusses various topics related to technical interview questions for software testing. It covers software testing basics like the PDCA cycle and different testing types (white box, black box, gray box). It also discusses usability testing, defect categories, defining a testing policy, preparing acceptance plans, configuration management, code coverage tools, and different testing models. Key software development phases like design, coding, and their relative defect rates are examined. The roles of different testing teams and how test documents span the SDLC are outlined. Common testing concepts like test cases, logs, traceability, entry/exit criteria, verification vs validation are defined.
Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Top 50 Software Testing Interview Question and Answers will help you to prepare yourself for Software Testing Interviews. It covers questions for beginners, intermediate and experienced professionals.
Below topics are covered in this PPT:
Market Trends in Software Testing
What is Software testing
Top 50 interview questions
1. Beginners level questions
2. Intermediate level questions
3. Advance level questions
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
The document discusses testing best practices for rich client applications. It outlines the challenges of testing user interfaces and interactions. It then describes different levels of testing from ad hoc to crowdsourcing. Unit testing, continuous integration, and automated functional testing are explained. The current state of testing tools for Titanium is presented along with a demo. Future directions including more automation and crowdsourced testing are envisioned.
To be able to effectively and sustainably test in Agile projects the test activities must be properly integrated in the Agile approach. To be efficient and effective automation is essential. In this webinar Rik will cover subjects like Footholds for testing from the Manifesto, the role of Product Owner, Scrum Master and Agile team members, Test Strategy and Test Levels (e.g. E2E-testing), TMap & ISTQB (Agile Extension) and DevOps.
Key Takeaways:
1) Be adaptive
2) Use a risk-based approach
3) Testing activities must be automated as much as possible
www.eurostarconferences,com
http://testhuddle.com/resource/integrate-test-activities-in-agile/
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
This document provides an overview of fundamentals of software testing. It discusses the five parts of the fundamental test process in broad chronological order: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and test closure activities. It also covers topics like regression testing, confirmation testing, the differences between re-testing and regression testing, and the importance of independence in testing.
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
It's a 1st Unit PPT of Subject Software Testing & Quality from the Book "Software Testing & Quality Assurance" by Kshirsagar Naik and Priyadarshi Tripathy
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Effective Testing Practices in an Agile EnvironmentRaj Indugula
This is a practitioner’s view of testing and testing practices within an iterative development environment. We will explore the challenges of testing within such an environment and ways to better integrate the QA professional into what is inherently a developer-centric methodology. If quality is paramount, then we ought to move testing to the front of the line and test early and often. Automation lies at the heart of agility and we will look at how test automation techniques and test-first design philosophy might be applied at multiple-levels to drive quality.
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.
Creating a successful continuous testing environment by Eran KinsbrunerQA or the Highway
This document discusses continuous testing and provides an overview of key concepts. It defines continuous testing as executing automated tests as part of the software delivery pipeline to rapidly obtain feedback on release candidates. The benefits of continuous testing discussed include fast feedback, continuous visibility, and testing that matches different skill levels. It also covers topics like test authoring best practices, key performance indicators for continuous testing, and the potential future role of machine learning. Continuous testing is presented as a way to mature an organization's path toward DevOps practices.
Learn how to establish a greater sense of confidence in your release cycle, along with the practices and processes to create a high-performing engineering culture within your team.
SDT provides software testing services and products to help customers create quality software on time and on budget. They offer a full suite of testing solutions including test transformation services, outsourcing, test automation tools, test methodologies, and training courses. Their unified test automation tool and managed testing services help clients achieve the most effective testing at the lowest cost.
IBM is reviewing their DevOps roadmap and solutions. They discuss how software delivery is critical for business success but many companies do not leverage it effectively. IBM's DevOps approach uses tools and practices to enable continuous software delivery and reduce time to customer feedback. They have acquired UrbanCode to strengthen their release and deployment capabilities. Future plans include further tool integrations across the development lifecycle.
Quality Jam: BDD, TDD and ATDD for the EnterpriseQASymphony
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
Software organizations that want to maximize the yield of Software Testing find that choosing the right testing strategy is hard, and most testing managers are ill-prepared for this. The organization has to learn how to plan testing efforts based on the characteristics of each project and the many ways the software product is to be used. This tutorial is intended for Software professionals who are likely to be responsible for defining the strategy and planning of the testing effort and managing it through its life cycle. These roles are usually Testing Managers or Project Managers.
IBM i Application Lifecycle Management with Remain SoftwareRemain Software
Integrated Toolset for IBM i Application Lifecycle Management. Seamlessly integrated modules for total control over application lifecycle
- Code quality assurance
- Real-time overview of business critical software assets
- Support for regulatory, certification and audit requirements towards IT department and software modernization projects
- Methodology independent process automation
- Streamlined collaboration and communication
- Increased productivity among team members
- Support for projects’ management
- Improved work quality
Live Webinar- Making Test Automation 10x Faster for Continuous Delivery- By R...RapidValue
A live webinar hosted by RapidValue Solutions on "Making Test Automation 10X Faster for Continuous Delivery".
Key takeaways:
1. Achieving test automation in a DevOps world
2. Building a business-tailored test automation framework
3. Overcoming limitations of open source tools
4. Case study: Creating 2000+ test cases in less than a month for a product development firm
5. Demo: Zero-code test automation for non-testers using AccuRate ( test automation suite by RapidValue)
Applying DevOps for more reliable Public Sector Software DeliverySanjeev Sharma
Government agencies and contractors must build the competency to deliver software with greater predictability, quality, speed and frequency. The alternative of higher costs and late delivery is no longer acceptable - politically, economically or justifiably. This session will share findings from client experiences and lay out the DevOps approach that is help agencies and their contractors address the challenges inherent in software application delivery.
This presentation includes challenges in testing, levels of testing, best practices and policies, Test Drive Design(TDD),
Behavioral Driven Design (BDD Testing), TDD v/s BDD
Introducing Software Development TechnologiesJohn Miller
SDT provides software testing services and products to help customers create quality software on time and on budget. They ensure predictable quality, minimize risks, and reduce costs through their rightsourcing model which blends internal and external testing resources. SDT's Unified TestPro is a test automation tool that supports various software types and allows for parallel design and automation to increase productivity.
Dedicated Testing Team Available for Hire.
Best Suitable Engagement Model as per your Requirement
1. Project to Project
2. Per Hour Basis
3. Per Accepted Bug Basis
UiPath 2020.10 LTS Release Partner Technical Mastermind session focused on enabling partners for the 20.10 release through various sales and technical enablement activities including:
1) Partner Mastermind webinars to discuss the 20.10 partner enablement plan and provide technical self-learning.
2) Technical live sessions over multiple weeks to cover each product family.
3) Updates to the partner portal including technical documentation.
The goal is to transition partners from continuous maintenance to continuous automation through alignment and reuse across the enterprise to rapidly and sustainably scale automation.
Curiosity and Infuse Consulting Present: Sustainable Test Automation Strategi...Curiosity Software Ireland
This webinar was co-hosted by Infuse Consulting and Curiosity Software on 27th September 2022. Watch the on demand recording here: https://opentestingplatform.curiositysoftware.ie/generate-rigorous-automated-tests-webinar
Your test automation rates are too low to match the speed of CI/CD, while suboptimal coverage is constantly letting bugs slip through. What do you do?
Many organisations treat this as a resourcing problem, often approaching services providers to navigate an automation skills shortage. Yet, hiring more people to perform the same processes is unsustainable, as the demand for automation persists sprint-over-sprint. In-house testing further risks growing dependent on a scripted framework that they can’t easily access or target for coverage. They risk throwing money constantly at external engineers to write repetitive scripts, fix brittle tests, and source test data. These suboptimal processes must be fixed first – people alone cannot fix test automation ROI.
This webinar will explore approaches to sustainable test automation that grows more efficient sprint-over-sprint, while targeting testing to de-risk the latest system changes. Nalin Parbhu, CEO of Infuse, and Curiosity’s George Blundell will draw on automation project experience from a range of different organisations. They will discuss collaborative approaches that automate processes surrounding test execution, while maximising reusability and optimising in-sprint test coverage. You will see solutions to perennial test automation barriers, including:
1. Collaborative test modelling, future proofing automation frameworks by maintaining intuitive living documentation.
2. In-sprint test and data generation, rapidly creating scripts from reusable flowchart models.
3. Automated test maintenance, targeting in-sprint coverage as requirements and systems change.
This document describes IBM's Quick Start Service Offering for IBM UrbanCode Deploy. The Quick Start involves:
1. Installing and configuring the UrbanCode Deploy solution environment and prototyping an initial configuration integration using out-of-the-box plugins.
2. Prototyping and demonstrating initial automation of a deployment process for a single well-defined application.
3. Providing mentoring for up to two consultants and training for up to 12 additional team members to enable adoption of the tools.
The Quick Start is delivered over 2 weeks, with an initial virtual preparation period followed by 1 week of on-site activities including installation, configuration, prototyping, and training
Similar to Acceptance Testing Driven Development, TDD (20)
Managing requirements and collaboration in Jira with BDDLaurent PY
This document discusses managing requirements and collaboration in Jira using behavior-driven development (BDD). It outlines how BDD in Jira allows for formulation, automation, and discovery of requirements through examples mapped to scenarios. Examples of system behavior are documented using business terminology to create shared understanding. This living documentation is then automated and can be navigated. The document also discusses how Cucumber allows teams to deploy software 10 times per day through a model of independent microteams using BDD and test-driven development for 100% automated testing and a continuous integration/delivery pipeline.
BDD can help save Agile by facilitating three main outcomes: shared understanding, business readable specifications, and living documentation. BDD involves discovering business needs through workshops, formulating examples and scenarios in a business-readable way, and automating tests to create living documentation that ensures everything continues to work as intended. Practicing BDD improves collaboration, delivers working software based on business needs, and guides development with up-to-date documentation.
Continuous testing for Agile and DevOps teamsLaurent PY
In this webinar we presented a continuous testing framework enabling agile teams to test their software from idea to production.
It is based on Behaviour Driven Development (BDD), automated testing and product analytics.
The document discusses a progressive approach to balancing quality and speed in software development. It proposes a 3-step process: 1) Testing the initial idea with examples and definitions of success, 2) Testing a first increment in production and measuring impact, and 3) Making the feature fully available once validation and automation are completed. The approach aims to test value first, invest progressively in quality, gain user feedback, and create an environment for experimentation.
Développement d'un grand projet piloté par les tests (BDD)Laurent PY
Déploiement de l'approche BDD (Behavior Driven Development) dans un grand projet billettique de 150 années/hommes avec des équipes distribuées. Par Hiptest et Parkeon
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).
Accélérer les tests d’acceptation avec un DSL et du refactoringLaurent PY
Le pilotage des développements par les tests d’acceptation reste un problème difficile à maîtriser dans les projets agiles. D’une part, il est compliqué d’impliquer les analystes métier dans la réalisation de scripts de tests automatisés, et d’autre part les tests de hauts niveaux qu’ils peuvent produire sont souvent difficiles à maintenir et automatiser.
L’approche proposée, supportée par une plate-forme appelée Zest, associe la définition des scénarios de tests d’acceptation sur la base d’un DSL (Domain-Specific Language) construit incrémentalement avec des mots d’action, et des fonctions de refactoring qui permettent en permanence d’optimiser les scénarios pour en faciliter l’automatisation et leur maintenance.
Le pilotage des développements par les tests d’acceptation reste un problème difficile à maîtriser dans les projets agiles. D’une part, il est compliqué d’impliquer les analystes métier dans la réalisation de scripts de tests automatisés, et d’autre part les tests de hauts niveaux qu’ils peuvent produire sont souvent difficiles à maintenir et automatiser.
L’approche proposée, supportée par une plate-forme appelée Zest, associe la définition des scénarios de tests d’acceptation sur la base d’un DSL (Domain-Specific Language) construit incrémentalement avec des mots d’action, et des fonctions de refactoring qui permettent en permanence d’optimiser les scénarios pour en faciliter l’automatisation et leur maintenance.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
4. Testing: Time for disruption ?
Software testing vendors:
N°1: HP (QC, QTP, BPT)
N°2: IBM (RQM, RTW)
N°3: Micro Focus (SilkCentral,
SilkTest)
Where do we find the best practices?
Do you think they use Quality Center?
5. Smartesting engineering process (early years 2004-2006)
Water fall process
–Very few tests made by developers (No TDD)
–1 release every 6 months
–1 month (x5 engineers) spent on acceptance testing before
rolling out
–Very poor QA impacting customers feedback
6. Introducing agile development (2006)
Introduction of agile: Scrum, TDD (unit &
integration testing), pair programming…
–Continuous integration
–1 release every 3 months
–4 man/days spent on acceptance testing before
rolling out
–Very good Quality
7. Going to the cloud (2012)
Introduction of continuous deployment and DevOps
–SEVERAL releases a DAY! Enable business agility
–Acceptance Testing Driven Development (ATDD)
–Engineering process driven by testing !
http://www.thucydides.info/blog/295-does-atdd-really-save-you-time
With ATDD and TDD projects delivered 31% faster with 4 times fewer defects
9. 9
Req Management &
Definition
Test Planning Execution Defect management
Agility leads to short iterations, less planning, and massive
automation (with rise of mobile, virtualization)
Value chain is shrunk acceptance test is the requirement⇒
(elicitation)
Testing drives the engineering process !!!
The testing value chain is being shaken
12. 12
Acceptance Testing Driven Development (ATDD) in a
Nutshell
Begin with the end in mind
Test is THE definition of done
Written prior to development
Confirmed with stakeholders
May or May not be automated
Support Critique
Code Level Unit Testing Inspections, code
quality analysis
Business Level Acceptance
testing
Exploratory
testing
Test in natural language
Test fixture
Code
13. 13
ATDD in a Nutshell
Some Benefits
–Collaboration and Communication
–Team knows what successful implementation means
–Achieving better coverage of business expectations
–Shorten the feedback cycle (lean)
And some Challenges:
–Change in process so must have management support
–Find the right Balance People/Process/Tool
19. 20
Lessons learned: The concepts
Steps & scenarios are the key elements
Gherkin language
Scenario=list of free step
20. 21
Lessons learned: Abstraction
Function/Keyword/Action Word…
Data: physical VS logical
Graphical flow (no semantic to strong semantic)
Behavior: IF THEN ELSE, WHILE
Rules
Easy
Easy
Medium
Hard
Hard
21. 22
Lessons learned: Action Word
Keyword/Action Word are easy to understand
Powerful abstraction for maintenance
But, It can be hard to get the right factorization
Not every step needs to be reusable
Definition of Smart: Right balance between two levels
22. 23
Should be parameterized (use logical data & data tables)
Can include several other steps and Action Words
Enable different levels of abstraction (Workflow, feature)
Lessons learned: Action Word
AW1 AW2
AW3 AW4 AW5 AW5 AW6
Workflow
Feature
23. 24
Lessons learned: Scenario, Action Word, Step, data
With these simple concepts you can get:
Flexibility to describe business domain
Powerful refactoring capabilities
25. 26
Platform in the cloud for ATDD
Use Case 1: You are agile and do continuous integration
ATDD Platform
Create acceptance tests
Tester
Validate
acceptance criteria
Business Analyst
use
acceptance criteria
Developer
Code
repository
Integrate with
• Smartesting DSL
• Smart refactoring capabilities
• Collaboration
• Smartesting DSL
• Smart refactoring capabilities
• Collaboration
26. 27
Platform in the cloud for ATDD
Use Case 2: You are in a more traditional environment and got a test
management tool
ATDD Platform
• Smartesting DSL
• Smart refactoring capabilities
• Collaboration
• Smartesting DSL
• Smart refactoring capabilities
• Collaboration
Test
Management
Tool QC/QTP
RQM/RTW
Requirement
Management
Tool
RRC
27. 28
Platform in the cloud for ATDD
Setup your project and be ready to start in
60 Seconds
29. 30
ALM market dynamic
New software delivery models
Testing is the biggest ALM segment
Distributed Testing segment represents more than $2b in
2013 10% (http://www.gartner.com/id=2098416)
Increasingly focused on Web & mobile
Security testing is the fastest growing segment
30. 31
More Cloud
ALM paas: $315m in 2016 (http://www.gartner.com/id=2188816)
Started by defect management, load tests, dev or test lab provisioning
Drivers
–Agile development
–Speed of deployment and business agility
Inhibitors
–Managing the transition
–Lack of integration (OSLC)
31. 32
Test earlier & more automation
Definition level
–More ATDD
–Testing driving the engineering process
–More & smarter tools to support design and maintenance
Test Execution
–Test lab, virtualization
–New generation of Automation Tools
33. 34
Daily Apple TV giveaway
Complete your session surveys online each day at a conference kiosk or on
your Innovate 2013 Portal!
Each day that you complete all of that day’s session surveys, your name will
be entered to win the daily Apple TV!
On Wednesday be sure to complete your full conference evaluation to receive
your free conference t-shirt!
I am delighted to share with you some thoughts Smartesting 10+ years old company: - push quality upfront with early test design - speed up test design and maintenance by a factor of ten! We are at the stone age compared to what developers do. - Testing is not a pain. This is cool and testing is THE opportunity to streamline
As introduction I will share with you our own experience in testing our product Then I will present the traditional testing process and the testing value chain to show you the way it s being disrupted. One of the main conclusion we ’ ve come to is that, as tester, we need a language If we still write tests as free text, we will never be able to Handle very quickly, to iterate and be agile! So not only we ’ ve come to this conclusion I will end up with the perspectives and different trends we foresee in the testing market.
So Let ’ s start by an interesting tweet from Alex Osterwalder The next tweet was about the disruption that ’ s happening
Let ’ s focus on testing. The 3 leaders (for testing tool) of this market Now let me ask you a question: where do we find the best practices? Do these guys use a test management tool? BTW how many of you use QC or RQM You can raise your hand that ’ s not a shame
Now let ’ s have a look at our own history as software vendor We were developing a MDT solution. So quite complex develoments… Testing was a nightmare=> Poor Quality I remember the feedback of a customer
So we made the decision to be more agile, do ExP, deploy scrum One of the key building block was continuous integration Doing the acceptance testing is no more a pain and and we can roll out rapidly with a good quality. So that ’ s fine. Our developers enjoy extreme programming and scrum even if there are some drawbacks to pair programming
we made the decision to develop a platform in the cloud Implement 3 missions: testing upfront & enabling ATDD… So we had to go one step further and do DevOps and continuous deployment (SciFi) To achieve continuous delivery of valuable software => testing has to be “ continuous We start every feature by… and I DO TEST
What is agility about? If we have to iterate very quicly, we don t have time to synch 3 repo: Ex, Test, Dev with 3 different owners I will mainly focus on the last 2points.
This is another way to see the pb. For big project we usualy have Just to mention some of the problem
Gartner predicted that mobile App dev will outnumber native PC projects by a ratio of 4:1 by 2015. I will not mention in this pres: security & performance to focus on functional. Continuous testing: “ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
An acceptance test is a formal description of the behavior of an application, generally expressed as an example or usage scenario Tests are the requirements. TEST ARE THE DEFINITION OF DONE Testing is no more the last step of the development process before moving into production, it is the first one! Focus developments efforts on acceptance tests Use acceptance tests to facilitate discussion about future change requests Brian Marick’s Agile Testing Quadrant
Use Test to build a shared understanding of the domain and of the objectives : YOU know what successful implementation means Focus developments efforts on acceptance tests You increase you quality and efficiently support continous delivery of valuable software
Accelerate the testing cycle at the business level! At smartesting we have automated 100% of our test so that we have an immediate feed-back, we can deploy de build and more importantly, we get the feed-back directly from the end user and can iterate quickly
So acceptance test is a formal description of the behavior of an application , formal description we use to build a shared understanding of the business domain. What we need now to be really lean is a test language. Not just free text. But Some concepts to handle. The same concepts will be used for the test automation and to do some analytics. I cannot iterate rapidly trough this loop if I have just text like in QC or Excel.
Author Notes: This template has been created in PowerPoint 2003 Depending on how the source file was formatted, some slides will not ideally reformat once the template is applied. Therefore, some reformatting will be necessary. Reapply slide layouts: Task Pane / Slide Layout Can be applied thru normal or slide sorter view May have to reapply the layouts more than once in order to take effect Limit altering slide layout attributes on your slide (fonts, positioning, text box anchoring, positioning, etc.), this will create less reformatting rework when switching templates in the future or repurposing this slide in other presentations. Use “shift returns” if text wraps are needed to wrap around imagery. If slide layout customization is needed, it ’s advised to break the customized text box from the slide layout by selecting the bounding box of the altered text box and cutting it from the slide, apply either the title slide layout or the blank layout, and then paste the text box back onto the slide. Your custom-formatting of the text layout will then be retained for future repurposing in other presentations. Recolor graphics if needed by using the embedded color palette swatches already in this template. Slide text: Don ’t create long sentences or paragraphs on slides. Use concise bulleted list format. Use speaker notes for supporting bulleted content to avoid slides that are too text heavy. Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. When referring to IBM products, use the correct full name, do not abbreviate. Imagery Avoid using cartoon like clip-art, use photo-art instead. Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots). Images must be acquired from a ‘ royalty-free to use ’ source such as: Microsoft or Lotus Symphony Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http://www.freedigitalphotos.net/ IBMers can use images from IBM approved image libraries: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?OpenDocument&ExpandSection=4#_Section2 Close each presentation with the mandatory “Rational ThankYou Slide” located in the back of this file.
Position the MBT Make comparison with development language
The needs are different compared to the dev Testing is made by some examples that helps to capture the behavior of the App
Smart testing tool should help me to build the right level of abstraction and factorization. Help me to build action word when I need reuse and factorization, not before, not after.
2 levels is good. 3 levels becomes hard to maintain
Optional slide. Graphic is available in English only.
Testing is made by some examples that helps to capture the behavior of the App
Testing is made by some examples that helps to capture the behavior of the App
Testing is made by some examples that helps to capture the behavior of the App
Author Notes: This template has been created in PowerPoint 2003 Depending on how the source file was formatted, some slides will not ideally reformat once the template is applied. Therefore, some reformatting will be necessary. Reapply slide layouts: Task Pane / Slide Layout Can be applied thru normal or slide sorter view May have to reapply the layouts more than once in order to take effect Limit altering slide layout attributes on your slide (fonts, positioning, text box anchoring, positioning, etc.), this will create less reformatting rework when switching templates in the future or repurposing this slide in other presentations. Use “shift returns” if text wraps are needed to wrap around imagery. If slide layout customization is needed, it ’s advised to break the customized text box from the slide layout by selecting the bounding box of the altered text box and cutting it from the slide, apply either the title slide layout or the blank layout, and then paste the text box back onto the slide. Your custom-formatting of the text layout will then be retained for future repurposing in other presentations. Recolor graphics if needed by using the embedded color palette swatches already in this template. Slide text: Don ’t create long sentences or paragraphs on slides. Use concise bulleted list format. Use speaker notes for supporting bulleted content to avoid slides that are too text heavy. Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. When referring to IBM products, use the correct full name, do not abbreviate. Imagery Avoid using cartoon like clip-art, use photo-art instead. Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots). Images must be acquired from a ‘ royalty-free to use ’ source such as: Microsoft or Lotus Symphony Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http://www.freedigitalphotos.net/ IBMers can use images from IBM approved image libraries: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?OpenDocument&ExpandSection=4#_Section2 Close each presentation with the mandatory “Rational ThankYou Slide” located in the back of this file.
In the middle of a revolution Even if we say testing is the last thing we do … when we have time, it is the place whete the biggest investment are done Inside testing market, segment that are growing very fast
ALM paas grows at 23% CAGR
These is my humble experience of test practitioner and as manager. The trends I strongly believes in, and that will go mainstream Beta tester Booth T19
Optional slide. Graphic is available in English only.
Giveaway Slide
Mandatory closing slide (2 of 2) Thank You Slide (available in English only).
Optional slide. Graphic is available in English only.
Author Notes: This template has been built in PowerPoint 2003. If you ’re using PowerPoint 2007 or above, you may experience different usability results than what is provided as guidance here. Depending on how the source file was formatted, some slides will not ideally reformat once the template is applied. Therefore, some reformatting will be necessary. Reapply slide layouts: Task Pane / Slide Layout Can be applied thru normal or slide sorter view May have to reapply the layouts more than once in order to take effect Limit altering slide layout attributes on your slide (fonts, positioning, text box anchoring, positioning, etc.), this will create less reformatting rework when switching templates in the future or repurposing this slide in other presentations. Use “shift returns” if text wraps are needed to wrap around imagery. If slide layout customization is needed, it ’s advised to break the customized text box from the slide layout by selecting the bounding box of the altered text box and cutting it from the slide, apply either the title slide layout or the blank layout, and then paste the text box back onto the slide. Your custom-formatting of the text layout will then be retained for future repurposing in other presentations. Slide numbers may be duplicated in the footer of your slides. You ’ll have to delete the page numbers on the left manually for each slide. Recolor graphics if needed by using the embedded color palette swatches already in this template. The color palette is also specified on the slide above. Slide text: Don ’t create long sentences or paragraphs on slides. Use concise bulleted list format. Use speaker notes for supporting bulleted content to avoid slides that are too text heavy. Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. When referring to IBM products, use the correct full name, do not abbreviate. Imagery guidelines: Avoid using cartoon like clip-art, use photo-art instead. Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots, and photos). Images must be acquired from a ‘ royalty-free to use ’ source such as: Microsoft or Lotus Symphony Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http://www.freedigitalphotos.net/ IBMers can use royalty-free images from the following repositories : IBM Brand Systems Center / Assets / Photography Login instructions: https://w3-connections.ibm.com/forums/html/topic?id=c1082624-e54c-4e04-bad1-ddb150ac7540 IBM Software Story Images https://w3-connections.ibm.com/files/app#/collection/b7570645-b2f8-4450-a27f-9269a163fc2d IBM Rational Presentation Image Library: https://w3-connections.ibm.com/wikis/home?lang=en_US#!/wiki/Rational%20Presentation%20Templates,%20Guidelines,%20and%20Resources/page/Presentation%20Image%20Library