Test automation can provide benefits such as increased test speed and coverage, reduced costs, and more consistent testing. However, test automation also has pitfalls like being inflexible to changes and requiring significant maintenance. The document discusses different generations of test automation such as record and playback, scripting, data-driven, and keyword-driven approaches. Later generations generally have better maintainability and reusability than earlier record and playback approaches.
This is a draft of a presentation for a course on Visual Studio 2010 Unit Testing, I've uploaded mainly because I tried to create a Metro Style presentation, so if everyone like it, he can use as base for own presentation.
Creating automation scripts using a generic framework is useful. The framework should have recovery scenarios and it should also perform a quick check after test execution using customized logs. The test execution summary must provide accurate information on test case execution. This article on IBM® Rational® Functional Tester elaborates this process.
This document discusses test automation, including the purpose of test automation, the test automation process, and the test automation pyramid. The key points are:
1. Test automation aims to improve test efficiency, provide wider test coverage, reduce costs, and speed up testing.
2. The test automation process involves defining the test scope, designing tests, coding tests, setting up the test environment, running tests, and maintaining automation over time.
3. The test automation pyramid illustrates that unit tests should form the base, as they are quick to write and run, while user interface tests are at the top as they are more complex and time-consuming.
Today we need everything reliable and accelerated, so to attain prompt results we are using varied automation testing tools. An automation tool is a piece of software that is run by little human interaction. Different testing tools are used for automation/manual testing, unit testing, performance, web, mobile, etc., more to that we have some open source testing tools as well.
The document discusses automation testing basics, including that automation testing is done using automated tools to write and execute test cases. It explains that automation testing should be used for tasks that are time-consuming, repeated, tedious, or involve high risk test cases. The document also lists some popular free and commercial automation testing tools.
The document discusses programming skills needed for test automation. It outlines skills in areas like programming languages, scripting, test frameworks, databases, performance testing and more. Automated testing requires both testing expertise and strong programming abilities to build test suites that can validate software accurately and repeatedly. Successful test automation depends on having the right tools, process and blending of testing and coding skills on the test automation team.
This document discusses techniques for achieving continuous delivery of software. It describes building a pipeline with automated testing at each stage from commit through deployment. This includes continuous integration, automated acceptance tests, and treating releases as non-events through infrastructure as code and automated deployment. The goal is to deliver value to customers early and continuously through eliminating bottlenecks and waste in the development and release process.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides best practices for setting up a successful automation framework. Finally, it gives an introduction to the features and capabilities of IBM Rational Functional Tester, including the recording and playback process for automated tests.
This is a draft of a presentation for a course on Visual Studio 2010 Unit Testing, I've uploaded mainly because I tried to create a Metro Style presentation, so if everyone like it, he can use as base for own presentation.
Creating automation scripts using a generic framework is useful. The framework should have recovery scenarios and it should also perform a quick check after test execution using customized logs. The test execution summary must provide accurate information on test case execution. This article on IBM® Rational® Functional Tester elaborates this process.
This document discusses test automation, including the purpose of test automation, the test automation process, and the test automation pyramid. The key points are:
1. Test automation aims to improve test efficiency, provide wider test coverage, reduce costs, and speed up testing.
2. The test automation process involves defining the test scope, designing tests, coding tests, setting up the test environment, running tests, and maintaining automation over time.
3. The test automation pyramid illustrates that unit tests should form the base, as they are quick to write and run, while user interface tests are at the top as they are more complex and time-consuming.
Today we need everything reliable and accelerated, so to attain prompt results we are using varied automation testing tools. An automation tool is a piece of software that is run by little human interaction. Different testing tools are used for automation/manual testing, unit testing, performance, web, mobile, etc., more to that we have some open source testing tools as well.
The document discusses automation testing basics, including that automation testing is done using automated tools to write and execute test cases. It explains that automation testing should be used for tasks that are time-consuming, repeated, tedious, or involve high risk test cases. The document also lists some popular free and commercial automation testing tools.
The document discusses programming skills needed for test automation. It outlines skills in areas like programming languages, scripting, test frameworks, databases, performance testing and more. Automated testing requires both testing expertise and strong programming abilities to build test suites that can validate software accurately and repeatedly. Successful test automation depends on having the right tools, process and blending of testing and coding skills on the test automation team.
This document discusses techniques for achieving continuous delivery of software. It describes building a pipeline with automated testing at each stage from commit through deployment. This includes continuous integration, automated acceptance tests, and treating releases as non-events through infrastructure as code and automated deployment. The goal is to deliver value to customers early and continuously through eliminating bottlenecks and waste in the development and release process.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides best practices for setting up a successful automation framework. Finally, it gives an introduction to the features and capabilities of IBM Rational Functional Tester, including the recording and playback process for automated tests.
Kanoah Tests is a test management tool that integrates seamlessly with JIRA. It allows coordinating all test management activities like planning, authoring, execution, and reporting from within JIRA. Users praise Kanoah Tests for its simple and elegant solution compared to other plugins, and for the responsive customer service. The tool provides features like test case authoring at the story level, test planning and execution, test importing, and a REST API for test automation. It offers benefits like centralized test management, end-to-end traceability, and real-time insights into testing progress through built-in reports.
The document discusses key aspects of successful test automation including:
1. Applying a software development process to automation to improve reliability and maintainability.
2. Improving testing processes with robust manual testing and defect management before automating.
3. Clearly defining requirements for what to automate and goals of the automation effort.
Agile testing - Principles and best practicesDr Ganesh Iyer
The document provides an overview of agile testing principles and best practices presented by three QA engineers from Progress Software in Hyderabad, India. It discusses how application development has evolved from command-line/GUI to cloud and mobile. It identifies seven key factors for agile testing success: having a whole team approach, automation, agile practices, a mindset change towards testing, providing timely feedback, collaborating with customers, and maintaining a big picture view. It also discusses challenges with agile methodology like frequently changing requirements and frequent releases. It promotes practices like continuous integration, automation, same sprint automation, GoLive testing automation, 24x7 testing, and emphasizing automation in agile testing.
This document provides an overview of test automation from the perspective of a test automation engineer. It discusses key topics like the test automation pyramid, reporting, design considerations, and deployment. The test automation pyramid emphasizes unit testing, integration testing, and end-to-end testing from the bottom to top. Reporting and metrics are important for understanding test results and efficiency. Design focuses on aspects like data-driven testing, robustness, and repeatability. Deployment involves piloting automation, maintaining scripts, and supporting evolving environments. The goal is to improve testing in areas like coverage, speed, and cost while maintaining quality.
ALM Summit 3 - Setting up a Continuous Delivery Deployment Pipeline with TFSJose Luis Soria
The document discusses setting up a deployment pipeline with Team Foundation Server (TFS). It begins by defining what a pipeline is and providing examples of different types of pipelines like automated, manual, and continuous deployment styles. It then discusses why pipelines are useful, including benefits like getting early feedback, transparency, flexibility, and empowering teams. The document outlines criteria for success like shorter cycle times, greater test coverage, and improved velocity. It also lists potential warning signs and concludes with discussing how TFS can be used to implement an effective pipeline including practices for building, testing, deploying and managing environments.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides tips for successful automation. Finally, it covers features of IBM Rational Functional Tester, including how to set up a test environment and record scripts to automate testing.
Automation testing material by Durgasoft,hyderabadDurga Prasad
The document discusses automation testing tools QuickTest Professional (QTP) and Unified Functional Testing (UFT). It provides an overview of QTP, describing its features such as scripting language, supported applications and browsers. The document also covers QTP concepts like object repository, object spy, standard classes and object methods.
This talk aims to summarize the typical challenges one encounters in testing mobile applications. At the ThoughtWorks Pune office we have developed multiple mobile applications across various platforms (mobile web, hybrid apps, native apps, apps for tablets etc.). In this talk we will bring together lessons learnt around mobile testing. This talk was done by Vikrant Chauhan and Dubinsky De Soares
Automation Testing Project and Framework DetailsAkash Tyagi
The document provides details about the automation testing framework and process used for an ecommerce application. It describes the team structure, sprint timeline, automation test pack details, and the Cucumber BDD framework used for automation. Key points include:
- The team consists of testers, developers, a scrum master, and business analyst.
- Sprints are 2 weeks with testing in the second week. Retrospectives are held at the end.
- The automation test pack includes over 1200 UI and 400 API tests executed daily.
- Cucumber is used with Page Object Model. Tests are written in Gherkin and executed via Maven.
- Logs, reports and configuration are handled through Extent Reports,
The document discusses software testing practices and levels of testing. It provides observations that testing finds bugs but not their absence, and good test cases have a high probability of finding defects. It outlines practices like avoiding non-reproducible testing and assigning experienced people to testing. The document also describes levels of testing from unit to acceptance testing and integration techniques like top-down and bottom-up. It discusses validation, alpha/beta, and acceptance testing as well as test planning, estimation, and formal validation exit criteria.
This document discusses keyword-driven testing (KDT), a method for automating tests without programming. KDT allows manual testers and subject matter experts to design and execute automated test scripts. The document outlines the benefits of KDT, such as increased test coverage and faster return on investment. It also describes some challenges, such as maintenance issues. Overall, KDT is presented as the next generation of test automation that can empower users and drive organizational adoption of automated testing tools.
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.
The document outlines an upcoming programming workshop that will cover various JetBrains IDEs like PyCharm, IntelliJ IDEA, and PhpStorm. It then discusses Test Driven Development (TDD), including what TDD is, the development cycle used in TDD, and benefits like encouraging simple designs and confidence. Different types of software tests are also listed like unit tests, integration tests, acceptance tests, and others. Specific testing techniques like unit testing, integration testing using bottom-up and top-down approaches, and acceptance testing are then explained at a high level. Finally, some important notes on testing like trusting tests and prioritizing maintainability are provided.
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the types of tests that can be automated, including functional and non-functional tests. Finally, it addresses the advantages of automation including time savings and repeatability, as well as challenges such as maintenance efforts and tool limitations.
This document provides guidance on planning and setting up load testing scenarios in LoadRunner. It discusses defining load testing objectives, analyzing the system under test, and planning the LoadRunner implementation. Key steps include determining the test environment setup, defining the types and numbers of virtual users to create, and identifying the required hardware resources. The document also covers creating a LoadRunner scenario by defining hosts, connecting hosts, adding virtual user scripts and users, and setting the rendezvous policy if needed. It emphasizes properly running the scenario by checking the Remote Command Launcher, specifying the results directory, initializing virtual users, and running the virtual users.
Automation Framework - gFast: generic Framework for Automated Software Testing - QTP Framework
The Most sophisticated frameworks in Automation Testing is Designed with highly experienced Automation Consultants of Heyday Software Solution for all the areas. This makes us to make the impossible things to make possible very fast with our proprietary framework "gFAST".This is a QTP Framework
About gFAST: generic Framework for Automated Software Testing
****************
Developed on Quick Test Professional supporting all Platforms(addin's) with KeyWord Driven Framework.
Key Features
****************
* Better ROI
* Internationalization Support
* Supports Multiple Projects/TestSuites/TestCases
* 24/7 Automatic Regression Tests Running Facility
* Generates Email Reports
* Generates Test Logs
* Simple way to Create Test Cases(without any new QTP Scripts development)
* Easy to Create Test Cases with Test Cases Generator
* Easy way to Create Tests With Excel/Text files facility)
* Easy to Maintain.(Whole Framework will Have 3 QTP script Files -Driver and Two
Controllers and Libraries.)
* Screen Capturing on Error for Each of the Test Cases
* Global Configuration Files
* Multiple Browser windows support
* Easy to build automation for the Projects
Our Frameworks:
Selenium Framework
WATIR RUBY Framework
Silk Framework
Winrunner Framework
QTP Framework
Generic Automation Framework
Perl Automation Framework
Selenium RC, Selenium WebDriver and HP LoadRunnerMurageppa-QA
In this Quality Assurance Training session, you will learn about Selenium- Remote Control (RC). Topic covered in this session are:
• Introduction to Selenium RC
• Installing Selenium RC
• Installing Eclipse
• Configuring Selenium RC
• Selenium RC Scripting
For more information, about this quality assurance training, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-training-with-hands-on-project-on-e-commerce-application/
Automated Software Testing Framework Training by Quontra SolutionsQuontra Solutions
Learn through Experience -- We differentiate our training and development program by delivering Role-Based training instead of Product-based training. Ultimately, our goal is to deliver the best IT Training to our clients.
In this training, attendees learn:
Introduction to Automation
• What is automation
• Advantages of automation & Disadvantages of automation
• Different types of Automation Tools
• What to automate in projects
• When to start automation. Scope for automation testing in projects
• About open-source automation tools
Introduction to Selenium
• What is selenium
• Why selenium
• Advantage and Disadvantages of selenium
Selenium components
• Selenium IDE
• Selenium RC
• Selenium WebDriver
• Selenium Grid
Selenium IDE
• Introduction to IDE
• IDE Installation
• Installation and uses of Firepath, Firebug & Debug bar
• Property & value of elements
• Selenium commands
• Assertions & Verification
• Running, pausing and debugging script
• Disadvantages of selenium IDE
• How to convert selenium IDE Scripts into other languages
Locators
• Tools to identify elements/objects
• Firebug
• IE Developer tools
• Google Chrome Developer tools
• Locating elements by ID
• Finding elements by name
• Finding elements by link text
• Finding elements by XPath
• Finding Elements by using CSS
• Summary
Selenium RC
• What is selenium RC
• Advantages of RC, Architecture
• What is Eclipse/IntelliJ, Selenium RC configure with Eclipse/IntelliJ
• Creating, running & debugging RC scripts
Java Concepts
• Introduction to OOPs concepts and Java
• Installation: Java, Eclipse/IntelliJ, selenium, TestNg/JUnit
• operators in java
• Data types in java
• Conditional statements in java
• Looping statements in java
• Output statements in java
• Classes & Objects
• Collection Framework
• Regular Expressions
• Exception Handling
• Packages, Access Specifiers /Modifiers
• String handling
• Log4J for logging
Selenium Web Driver with Java
• Introduction to WebDriver
• Advantages
• Different between RC and WebDriver
• Selenium WebDriver- commands
• Generate scripts in Eclipse/IntelliJ. Run Test Scripts.
• Debugging Test Script
• Database Connections
• Assertions, validations
• Working with Excel
• Pass the data from Excel
• Working with multiple browser
• Window Handling, Alert/confirm & Popup Handling
• Mouse events
• Wait mechanism
• Rich Web Handling: Calendar handing, Auto suggest, Ajax, browser forward/back navigation, keyboard events, certificate handling, event listeners
TestNg/JUnit Framework
• What is TestNg/JUnit
• Integrate the Selenium Scripts and Run from TestNg/JUnit
• Reporting Results and Analysis
• Run Scripts from multiple programs
• Parallel running using TestNg/JUnit
Automation Framework development in Agile testing
• Introduction to Frame W
In a device-frangmented world like ours today, it has become impossible to test all software, let alone mobile applications, manually. That's why automated testing is so important!
Find out about the top benefits of automated testing in this slideshow!
This document discusses designing an effective test automation strategy. It notes that current testing processes often lack sufficient test coverage and ROI turns negative. It emphasizes defining the proper scope and selecting an automation solution that can cover that scope. The document then introduces iLeap 2.0, an automation platform from Impetus Technologies that integrates open-source frameworks and tools to automate functional, API/web service, and security testing according to best practices. iLeap 2.0 is said to improve test coverage and maximize ROI.
Kanoah Tests is a test management tool that integrates seamlessly with JIRA. It allows coordinating all test management activities like planning, authoring, execution, and reporting from within JIRA. Users praise Kanoah Tests for its simple and elegant solution compared to other plugins, and for the responsive customer service. The tool provides features like test case authoring at the story level, test planning and execution, test importing, and a REST API for test automation. It offers benefits like centralized test management, end-to-end traceability, and real-time insights into testing progress through built-in reports.
The document discusses key aspects of successful test automation including:
1. Applying a software development process to automation to improve reliability and maintainability.
2. Improving testing processes with robust manual testing and defect management before automating.
3. Clearly defining requirements for what to automate and goals of the automation effort.
Agile testing - Principles and best practicesDr Ganesh Iyer
The document provides an overview of agile testing principles and best practices presented by three QA engineers from Progress Software in Hyderabad, India. It discusses how application development has evolved from command-line/GUI to cloud and mobile. It identifies seven key factors for agile testing success: having a whole team approach, automation, agile practices, a mindset change towards testing, providing timely feedback, collaborating with customers, and maintaining a big picture view. It also discusses challenges with agile methodology like frequently changing requirements and frequent releases. It promotes practices like continuous integration, automation, same sprint automation, GoLive testing automation, 24x7 testing, and emphasizing automation in agile testing.
This document provides an overview of test automation from the perspective of a test automation engineer. It discusses key topics like the test automation pyramid, reporting, design considerations, and deployment. The test automation pyramid emphasizes unit testing, integration testing, and end-to-end testing from the bottom to top. Reporting and metrics are important for understanding test results and efficiency. Design focuses on aspects like data-driven testing, robustness, and repeatability. Deployment involves piloting automation, maintaining scripts, and supporting evolving environments. The goal is to improve testing in areas like coverage, speed, and cost while maintaining quality.
ALM Summit 3 - Setting up a Continuous Delivery Deployment Pipeline with TFSJose Luis Soria
The document discusses setting up a deployment pipeline with Team Foundation Server (TFS). It begins by defining what a pipeline is and providing examples of different types of pipelines like automated, manual, and continuous deployment styles. It then discusses why pipelines are useful, including benefits like getting early feedback, transparency, flexibility, and empowering teams. The document outlines criteria for success like shorter cycle times, greater test coverage, and improved velocity. It also lists potential warning signs and concludes with discussing how TFS can be used to implement an effective pipeline including practices for building, testing, deploying and managing environments.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides tips for successful automation. Finally, it covers features of IBM Rational Functional Tester, including how to set up a test environment and record scripts to automate testing.
Automation testing material by Durgasoft,hyderabadDurga Prasad
The document discusses automation testing tools QuickTest Professional (QTP) and Unified Functional Testing (UFT). It provides an overview of QTP, describing its features such as scripting language, supported applications and browsers. The document also covers QTP concepts like object repository, object spy, standard classes and object methods.
This talk aims to summarize the typical challenges one encounters in testing mobile applications. At the ThoughtWorks Pune office we have developed multiple mobile applications across various platforms (mobile web, hybrid apps, native apps, apps for tablets etc.). In this talk we will bring together lessons learnt around mobile testing. This talk was done by Vikrant Chauhan and Dubinsky De Soares
Automation Testing Project and Framework DetailsAkash Tyagi
The document provides details about the automation testing framework and process used for an ecommerce application. It describes the team structure, sprint timeline, automation test pack details, and the Cucumber BDD framework used for automation. Key points include:
- The team consists of testers, developers, a scrum master, and business analyst.
- Sprints are 2 weeks with testing in the second week. Retrospectives are held at the end.
- The automation test pack includes over 1200 UI and 400 API tests executed daily.
- Cucumber is used with Page Object Model. Tests are written in Gherkin and executed via Maven.
- Logs, reports and configuration are handled through Extent Reports,
The document discusses software testing practices and levels of testing. It provides observations that testing finds bugs but not their absence, and good test cases have a high probability of finding defects. It outlines practices like avoiding non-reproducible testing and assigning experienced people to testing. The document also describes levels of testing from unit to acceptance testing and integration techniques like top-down and bottom-up. It discusses validation, alpha/beta, and acceptance testing as well as test planning, estimation, and formal validation exit criteria.
This document discusses keyword-driven testing (KDT), a method for automating tests without programming. KDT allows manual testers and subject matter experts to design and execute automated test scripts. The document outlines the benefits of KDT, such as increased test coverage and faster return on investment. It also describes some challenges, such as maintenance issues. Overall, KDT is presented as the next generation of test automation that can empower users and drive organizational adoption of automated testing tools.
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.
The document outlines an upcoming programming workshop that will cover various JetBrains IDEs like PyCharm, IntelliJ IDEA, and PhpStorm. It then discusses Test Driven Development (TDD), including what TDD is, the development cycle used in TDD, and benefits like encouraging simple designs and confidence. Different types of software tests are also listed like unit tests, integration tests, acceptance tests, and others. Specific testing techniques like unit testing, integration testing using bottom-up and top-down approaches, and acceptance testing are then explained at a high level. Finally, some important notes on testing like trusting tests and prioritizing maintainability are provided.
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the types of tests that can be automated, including functional and non-functional tests. Finally, it addresses the advantages of automation including time savings and repeatability, as well as challenges such as maintenance efforts and tool limitations.
This document provides guidance on planning and setting up load testing scenarios in LoadRunner. It discusses defining load testing objectives, analyzing the system under test, and planning the LoadRunner implementation. Key steps include determining the test environment setup, defining the types and numbers of virtual users to create, and identifying the required hardware resources. The document also covers creating a LoadRunner scenario by defining hosts, connecting hosts, adding virtual user scripts and users, and setting the rendezvous policy if needed. It emphasizes properly running the scenario by checking the Remote Command Launcher, specifying the results directory, initializing virtual users, and running the virtual users.
Automation Framework - gFast: generic Framework for Automated Software Testing - QTP Framework
The Most sophisticated frameworks in Automation Testing is Designed with highly experienced Automation Consultants of Heyday Software Solution for all the areas. This makes us to make the impossible things to make possible very fast with our proprietary framework "gFAST".This is a QTP Framework
About gFAST: generic Framework for Automated Software Testing
****************
Developed on Quick Test Professional supporting all Platforms(addin's) with KeyWord Driven Framework.
Key Features
****************
* Better ROI
* Internationalization Support
* Supports Multiple Projects/TestSuites/TestCases
* 24/7 Automatic Regression Tests Running Facility
* Generates Email Reports
* Generates Test Logs
* Simple way to Create Test Cases(without any new QTP Scripts development)
* Easy to Create Test Cases with Test Cases Generator
* Easy way to Create Tests With Excel/Text files facility)
* Easy to Maintain.(Whole Framework will Have 3 QTP script Files -Driver and Two
Controllers and Libraries.)
* Screen Capturing on Error for Each of the Test Cases
* Global Configuration Files
* Multiple Browser windows support
* Easy to build automation for the Projects
Our Frameworks:
Selenium Framework
WATIR RUBY Framework
Silk Framework
Winrunner Framework
QTP Framework
Generic Automation Framework
Perl Automation Framework
Selenium RC, Selenium WebDriver and HP LoadRunnerMurageppa-QA
In this Quality Assurance Training session, you will learn about Selenium- Remote Control (RC). Topic covered in this session are:
• Introduction to Selenium RC
• Installing Selenium RC
• Installing Eclipse
• Configuring Selenium RC
• Selenium RC Scripting
For more information, about this quality assurance training, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-training-with-hands-on-project-on-e-commerce-application/
Automated Software Testing Framework Training by Quontra SolutionsQuontra Solutions
Learn through Experience -- We differentiate our training and development program by delivering Role-Based training instead of Product-based training. Ultimately, our goal is to deliver the best IT Training to our clients.
In this training, attendees learn:
Introduction to Automation
• What is automation
• Advantages of automation & Disadvantages of automation
• Different types of Automation Tools
• What to automate in projects
• When to start automation. Scope for automation testing in projects
• About open-source automation tools
Introduction to Selenium
• What is selenium
• Why selenium
• Advantage and Disadvantages of selenium
Selenium components
• Selenium IDE
• Selenium RC
• Selenium WebDriver
• Selenium Grid
Selenium IDE
• Introduction to IDE
• IDE Installation
• Installation and uses of Firepath, Firebug & Debug bar
• Property & value of elements
• Selenium commands
• Assertions & Verification
• Running, pausing and debugging script
• Disadvantages of selenium IDE
• How to convert selenium IDE Scripts into other languages
Locators
• Tools to identify elements/objects
• Firebug
• IE Developer tools
• Google Chrome Developer tools
• Locating elements by ID
• Finding elements by name
• Finding elements by link text
• Finding elements by XPath
• Finding Elements by using CSS
• Summary
Selenium RC
• What is selenium RC
• Advantages of RC, Architecture
• What is Eclipse/IntelliJ, Selenium RC configure with Eclipse/IntelliJ
• Creating, running & debugging RC scripts
Java Concepts
• Introduction to OOPs concepts and Java
• Installation: Java, Eclipse/IntelliJ, selenium, TestNg/JUnit
• operators in java
• Data types in java
• Conditional statements in java
• Looping statements in java
• Output statements in java
• Classes & Objects
• Collection Framework
• Regular Expressions
• Exception Handling
• Packages, Access Specifiers /Modifiers
• String handling
• Log4J for logging
Selenium Web Driver with Java
• Introduction to WebDriver
• Advantages
• Different between RC and WebDriver
• Selenium WebDriver- commands
• Generate scripts in Eclipse/IntelliJ. Run Test Scripts.
• Debugging Test Script
• Database Connections
• Assertions, validations
• Working with Excel
• Pass the data from Excel
• Working with multiple browser
• Window Handling, Alert/confirm & Popup Handling
• Mouse events
• Wait mechanism
• Rich Web Handling: Calendar handing, Auto suggest, Ajax, browser forward/back navigation, keyboard events, certificate handling, event listeners
TestNg/JUnit Framework
• What is TestNg/JUnit
• Integrate the Selenium Scripts and Run from TestNg/JUnit
• Reporting Results and Analysis
• Run Scripts from multiple programs
• Parallel running using TestNg/JUnit
Automation Framework development in Agile testing
• Introduction to Frame W
In a device-frangmented world like ours today, it has become impossible to test all software, let alone mobile applications, manually. That's why automated testing is so important!
Find out about the top benefits of automated testing in this slideshow!
This document discusses designing an effective test automation strategy. It notes that current testing processes often lack sufficient test coverage and ROI turns negative. It emphasizes defining the proper scope and selecting an automation solution that can cover that scope. The document then introduces iLeap 2.0, an automation platform from Impetus Technologies that integrates open-source frameworks and tools to automate functional, API/web service, and security testing according to best practices. iLeap 2.0 is said to improve test coverage and maximize ROI.
The document provides guidelines for designing a robust test automation framework. It discusses that a well-designed framework increases testing efficiency and reduces costs. The key aspects of framework design include defining objectives, selecting the appropriate framework type, managing data, ensuring reusability, integrating with other tools, and flexible execution and reporting. Idexcel's test automation framework was created following these best practices to provide a maintainable and reusable framework.
A brief introduction to test automation covering different automation approaches, when to automate and by whom, commercial vs. open source tools, testability, and so on.
Introduction to Test Automation - Technology and ToolsKMS Technology
This document discusses test automation, including what it is, why it's used, different levels and approaches. It summarizes the benefits of automation over manual testing, and outlines common code-driven and GUI-driven automation techniques. It also provides an overview of popular automation tools, frameworks, and the future of automation testing as a career.
Agile Testing Framework - The Art of Automated TestingDimitri Ponomareff
Once your organization has successfully implemented Agile methodologies, there are two major areas that will require improvements: Continuous Integration and Automated Testing.
This presentation illustrates why it's important to invest in an Automated Testing Framework (ATF) to reduce technical debt, increase quality and accelerate time to market.
Learn more at www.agiletestingframework.com.
What are the Key drivers for automation? What are the Challenges in Agile automation and How to deal with them? How to automate? Who will automate? Which tool to select? Commercial or open source? What to automate? Which features? Here is what our experience says
The document discusses different types of automated software testing including unit testing, functional testing, load testing, requirements testing, and test coverage. It provides examples of unit tests written in JUnit and describes how unit testing can help design better code and prevent regressions. It also lists several popular open source testing tools and frameworks for different testing types. The document advocates starting with unit testing on new code and working towards automating testing and achieving full code coverage.
This document provides an overview and agenda for a QTP training session. It discusses the advantages of automation testing over manual testing, introduces QTP and its purpose as a functional and regression test automation tool. It outlines the key elements of the QTP tool window and describes the testing process which involves analyzing the application, preparing test infrastructure, building tests, enhancing tests with checkpoints and logic, debugging and running tests, and reporting defects. The document also covers the basics of recording tests in QTP and the different recording types (normal, analogue, low level), and provides an overview of playback.
Randy Rice of http://www.riceconsulting.com presents 14 questions you can ask to know if a software application or function is ripe for automation. Also presented are metrics for test automation ROI.
Automation testing involves developing and executing tests that can run unattended, comparing actual and expected results. The major objectives of automation testing are to speed up testing, reduce costs and time, and increase quality. Automation testing is faster than manual testing and can test more scenarios. However, high upfront investment is required for tools and training. Both manual and automation testing are needed as automation does not cover all test cases. Popular automation testing tools include Selenium, QTP, and TestComplete.
Automated testing involves using special software to control test execution and compare actual and expected outcomes without human intervention. It allows tests to run automatically, increasing speed and coverage while reducing costs compared to manual testing. High risk, repetitive, tedious, and time-consuming tests are best candidates for automation. Proper planning, tool selection, scope definition, and maintenance are required for effective automated testing in agile environments. Automation should start small and be added incrementally with each new implementation.
Why we need software testing?
- Find / prevent bug
- No more nightmare when you deploy to production
- Preserve product quality
End to End Test
- Testing the complete functionality of some application
- Real application
When is software test automation worth it?Claudia Baur
When should be automated?
Handling the increasing test effort with software test automation,
return on investment (ROI) of testing, phases of the test process with high influence on the ROI, Test automation with QF-Test: The Java & Web GUI testing tool.
The document discusses test automation, including defining it as using special software to control test execution and compare results. It lists major objectives like time and cost savings, improved productivity, accuracy, and coverage. It recommends automating repetitive, tedious, time-consuming, or high-risk tests. A typical automation process includes planning, design, tool development, deployment, and review. Choosing an automation tool requires considering ease of use, supported test types, and maintenance. Automated testing reduces long-term costs while manual testing has shorter-term benefits like more bugs found through hands-on testing.
This document contains commonly asked automation testing interview questions and their answers to help prepare for an interview. It discusses reasons for automation testing, factors in deciding what to automate, benefits of tools like Quick Test Pro and Selenium, the automation testing process, and challenges like maintaining automated tests. Specific questions cover topics like test frameworks, best practices, and when not to automate. The goal is to help interviewees have answers on their fingertips for a wide range of potential automation testing questions.
Organisations turn to Agile and DevOps to improve customer experience by maximising the speed of delivery without sacrificing quality. As the champions of quality, testers achieve this goal through continuous testing. Test Automation plays a major role in continuous testing; it is the backbone of the continuous test process. To achieve continuous testing, automation must be applied at every stage of the development process. Developing a smart automation strategy and using the right tools is critical in achieving continuous testing since test scripts must be scalable and easy to maintain.
Diving into the World of Test Automation The Approach and the TechnologiesQASymphony
This presentation was originally given at Quality Jam London. Elise covered test automation and the progression for test automation that you might encounter. The session agenda included:
The stages of the test team
Why are we automating?
What are we automating?
How are we automating?
What languages should we use?
What frameworks and libraries should we use?
Open source or proprietary?
Learn more at www.qualityjam.com
Automation testing involves using software tools to execute pre-scripted tests on an application before its release. It aims to simplify and automate as much testing effort as possible. Automation testing tools can execute tests, report outcomes, and compare results across test runs. Manual testing of multilingual sites is time-consuming and prone to errors, while automation testing can run unattended and is faster. Risky, time-consuming, repetitive, and difficult tests are best candidates for automation. Test tool selection depends on the application's technology. The scope of automation should be defined and include important, reused, and complex features. Automation brings benefits like repeatability, reusability, reliability, speed, comprehensiveness, and cost
Use Jenkins For Continuous Load Testing And Mobile Test AutomationClever Moe
The document discusses using Jenkins for continuous load testing and mobile test automation. It describes how Jenkins can be used to automate testing across sprints in an agile methodology. Specifically, it outlines how to leverage Jenkins to run functional tests continuously and repurpose those tests for performance and load testing. This helps ensure applications are thoroughly tested before each release.
This document discusses automation testing, including what it is, why it is used, the automation testing process, and how to select an automation tool. Automation testing is done to test repeatable cases across browsers at high speed while reducing human effort and costs. The process involves selecting a tool, defining scope, planning tests, executing scripts, and maintaining the automation code. Selenium is recommended as it is open source, supports many languages and browsers, and has a large community.
This document discusses test automation and continuous integration in agile development. It notes that early automation, continuously integrated and testable software, and fast feedback help ensure faster delivery and optimize business value. The main challenges are short testing time frames per story and multiple deployments per sprint. Building a test suite with unit, service, and UI tests provides faster feedback and easier refactoring. Collaboration between testers and developers and striking a balance between test levels is important. Continuous integration runs automated tests on every code check-in to test feature integration within sprints. Best practices include early QA involvement, defining test scenarios during backlog refinement, estimating automation effort, and creating automation tests in parallel with development. Benefits include faster test cycles within
[webinar] Cutting-edge Functional UI Testing Techniques - w/ Adam CarmiApplitools
** Full webinar recording: **
It is no secret that many teams struggle with automated functional UI testing - some to the point where it is completely abandoned - even though the UI is the most significant interface of the system.
In this session, Adam Carmi -- Applitools CTO and Co-founder -- reviewed the main weaknesses of traditional approaches to UI testing, and how they negatively affect test stability, maintainability, coverage, execution speed, and overall ROI. He also discussed how these weaknesses become even more severe when running tests across multiple devices and browsers.
Adam demonstrated how Visual AI -- the innovative technology powering Applitools' testing engine -- can be applied on your existing pipeline to efficiently implement functional UI tests with a fraction of the effort while drastically increasing test coverage and reducing test execution time.
Adam also showed a live coding session, where he converted a traditional UI test into a Visual AI-based test in minutes, and executed it across dozens of devices and browsers in seconds using the Applitools Ultrafast Grid.
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the process for automating tests. While automation testing provides benefits like time savings, it also has limitations such as the need for programming skills and maintenance of test code. Key challenges of automation testing include unrealistic expectations of tools and dependency on third party integrations.
This document provides an introduction to unit testing using the NUnit framework. It defines unit testing as developer tests that validate code works as expected. Unit tests are part of the construction cycle and sit between technical design and QA testing in the software development lifecycle. Benefits of unit testing include early defect detection, better code design, regression protection, and learning new APIs. The document then describes NUnit attributes that mark test fixtures and methods. It also covers NUnit assertions for verification. Examples are provided of test-driven development and using NUnit for continuous integration.
Ten steps to test automation success are outlined. The key steps are to improve testing processes, define requirements, prove automation concepts, design products for testability, create sustainable test designs, plan deployments, and address challenges. Test automation can significantly reduce testing effort and increase coverage, but requires careful test selection, design, and addressing common problems like lack of goals, experience, and understanding of new technologies.
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
SWOT analysis in the project Keeping the Memory @live.pptx
Chapter 10
1. CHAPTER 10
An Introduction to
Automated Software Testing
2. CHAPTER 10
OUTLINE
• What is Test Automation?
• The Benefits and Pitfalls of Test Automation
• When to Use Test Automation
• Test Automation Production Process
• The Evolution of Test Automation
3. CHAPTER 10
OBJECTIVES
• Present an overview of test automation engineering
• Understand the pros and cons of test automation
• Test automation strategies, tactics and implementation
4. An Introduction to
CHAPTER 10.1 Automated Testing
10.1 What is Test Automation?
10.2 The Benefits and Pitfalls of Test Automation
10.3 When to Use Test Automation
10.4 Test Automation Production Process
10.5 The Evolution of Test Automation
5. What is Test Automation?
CHAPTER 10.1
• Using computer time to execute of tests.
• Commonly, test automation involves automating existing and
sometimes, new tests that otherwise, will be executed by a
human tester
6. Why Automate Testing?
• People might say, “Automation will help us release a
higher quality product on time.”
– What does that mean?
• What’s the goal of instituting an Automation
program?
– What problem are we trying to solve?
7. Why Automate Testing?
– Not enough test time in schedule for repetitive tasks
– Very repetitive tasks
– Too many releases to test
– Better use of qualified in-house testing resources
– Reduce cost of testers
– Can’t test manually
– Optimize tester time because there is not enough time for
mundane tests
– Human tester can focus on testing that requires complex analysis
– Save money
– Save time
8. Why Automate Testing?
– If I automate testing, what manual testing will I lose? How
many bugs might I lose and when?
Remember: Bugs are more expensive to fix later.
9. Why Automate Testing?
– Often, if the manual test team also does automation, it is the best
or most technically talented testers who script.
– The early part of application testing is when the most talented testers are
needed.
• This is particularly true with script maintenance. Some talented
person on the main product team is often in charge of maintaining
the automation project.
– Will we lose finding good early bugs because of this?
– Testing cannot be an “on the side” job. You can’t write good
scripts while you wait to get a build or have spare time!
10. Goal of Automation
Sometimes, the goal of a test automation program can be
Good-Enough Automation. Just like with the products we sell,
quality is a combination of reliability, features and timeliness.
If your goal of automation is tightening the testing cycle. AND
you can also improve the test battery, you have done a good
job.
11. Manual vs.
CHAPTER 10.1 Automation Testing
Manual Testing Automation Testing
Test execution time Test execution time
Regression test coverage Regression test coverage
Responsive and flexible Relatively inflexible
Human variation Machine consistency
No maintenance needed High maintenance needed
Immediate dividend paid Long-term dividend
Not cost effective for high Not cost effective for low
volume regression volume regression
12. An Introduction to
CHAPTER 10.2 Automated Testing
10.1 What is Test Automation?
10.2 The Benefits and Pitfalls of Test Automation
10.3 When to Use Test Automation
10.4 Test Automation Production Process
10.5 The Evolution of Test Automation
13. Test Automation
CHAPTER 10.2 Benefits
• Run automated tests unattended (overnight)
• Reliable, consistent repetitive testing
• Increased speed in test execution
• Improves quality, increased test coverage
• Reduces costs and time for regression testing
• Optimize the use of test resources to focus on bug findings
• Reusable and scalable if architected effectively
• Execution of tests that can’t be done manually
• Performance testing to assess software stability, concurrency,
scalability….
14. Test Automation
CHAPTER 10.2 Pitfalls
• Uncertainty and lack of control.
• Poor scalability and maintainability.
– Too sensitive to changes
– Poor reusability
• Low test automation coverage
– Too much programming
• Poor methods and disappointing quality of tests
– Focus of tools instead production volume
– Focus of making the tests run instead of quality of the tests
• Technology vs. people issues
– Gaps in platform technology support
– Gaps in human resource equipped with test automation skills
15. An Introduction to
CHAPTER 10.3 Automated Testing
10.1 What is Test Automation?
10.2 The Benefits and Pitfalls of Test Automation
10.3 When to Use Test Automation
10.4 Test Automation Production Process
10.5 The Evolution of Test Automation
16. Which Test Cases
CHAPTER 10.3 Can’t be Automated?
• Usability testing
"How easy is the application to use?“
• One-time testing
• “ASAP” testing
“We need to test NOW!”
• Ad hoc/random testing
Based on intuition and knowledge of application
• Tests without predictable results
17. The Criteria to
CHAPTER 10.3 Apply Test Automation
• Customer requests
• Application should be stable
• Tests that need to be run for every build of the application (sanity
check, regression test)
• Tests that use multiple data values for the same actions (data driven
tests)
• Tests that require detailed information from application internals
(memory, CPU)
• Tests that require considerable amount of time to perform
manually
• Stress, load or performance testing
18. An Introduction to
CHAPTER 10.3 Automated Testing
10.1 What is Test Automation?
10.2 The Benefits and Pitfalls of Test Automation
10.3 When to Use Test Automation
10.4 Test Automation Production Process
10.5 The Evolution of Test Automation
19. Test Automation
CHAPTER 10.4 Production Process
Repeat steps
Wait for
Input user Check AUT until all to-be-
processing to
actions function outputs executed tests
complete
are completed
1 2 3 4
Manual
Synchronize
Generate script playback
Run tests or
automated to application Add checks
suites of tests
scripts output from
1 each step 2 3 4
Automated
20. An Introduction to
CHAPTER 10.5 Automated Testing
10.1 What is Test Automation?
10.2 The Benefits and Pitfalls of Test Automation
10.3 When to Use Test Automation
10.4 Test Automation Production Process
10.5 The Evolution of Test Automation
21. A Brief History
CHAPTER 10.5 of Test Automation
Software Test Automation has evolved through several generations,
with many improvements along the way:
1st Generation: Record and Playback
2nd Generation: Scripting
3rd Generation: Data-driven
4th Generation: Keyword-driven
22. Record & Playback
CHAPTER 10.6
The automation tool records the steps of the user executing a
test, and the tester configures some checks.
The automation tool generates a script based on the recorded
actions.
The automation tool performs a playback of the recorded test.
Even small changes to the application under test require manual
re-recording of the test.
→ This first generation is neither efficient nor scalable.
23. Record/Playback
Recorded test • Actions
• Checks
scripts
• One time recording of Playback
actions and checks
• Multiple time playback
Test Tool Log
(Invisible to the
target system)
Record Playback • Actions
• Checks
• Results
Test data entered by Target
testers or users System/AUT
24. EXAMPLE
A Recorded Script
select window "Logon"
enter text "username", "administrator"
enter text "password", "testonly"
push button "Ok"
select window "Main"
push button "New Customer"
expect window "Customer Information"
select field "Name"
type "Jones"
select field "First Name"
type "John"
select field "Address"
type "54321 Space Drive"
.
.
.
25. EXAMPLE
A Recorded Script
CHAPTER 10.6
• Dependent on screen coordinates
# Analog Recording
move_locator_track (1); mouse movement
mtype ("<T55> <kLeft>-<kLeft>+"); mouse click
type ("<t3>output14" );
move_locator_track (2);
mtype ("<T35><kLeft>-<kLeft>+");
output14
enter text pause before
from mouse click
keyboard
26. R/P Pros and Cons
• Pros
– A useful way to learn about the testing tool and
automation
• Cons
– High maintenance cost dealing with changes in the target
system of AUT
– Poor accessibility to test cases
– Greatly affected by the working system or environment
– Only suitable for GUI systems
27. Scripting Approach
• Automation is regarded as a programming activity
• Parameterize hard-coded values
• Separate data from code by moving variables to include files
• Create utility functions to be shared
• Produce and maintain like any other software
• Train black-box test engineers to run the scripts
28. Scripting Approach
• Pros
– Reusability of scripts for common tasks
– Improved maintainability
• Cons
– Poor accessibility to test cases because tests are
programmed or scripted
– Greatly affected by a working system or environment
– Test implementation must be done by programmers
– Translation of test cases—3000 tests mean 3000
automated scripts
– Manageability is still an issue due lack of visibility
29. EXAMPLE
Function EnterCustomerJones
Logon
Press "New Customer"
Enter Field "Name", "Jones"
Enter Field "First Name", "John"
Enter Field "Address", "54321 Space Drive"
...
Logoff
End Function
Function OrderProduct
Logon
Press "New Order"
Enter Field "Product", “OurProduct 1.0"
Enter Field "Amount", "35"
Enter Field "Delivery", "asap"
...
LogOff
End Function
...
30. Scripting –
Example Script
CHAPTER 10.6
Silk Test Script:
31. (Scripting) Data-Driven
Approach
• Take advantage of tester’s familiarity with test case design and
creation using tables and matrices
• Accommodate localization projects
• Recognize the importance of patterns in test cases
• Enable testers to catalog test cases with spreadsheets in
software such as Excel
• Enable testers to specify expected results in spreadsheets
32. EXAMPLE
GOODMORNING
goodmorning
GoodMorning
Input Data
33. EXAMPLE
• File with test data: • Text file used in the test:
nr case whole pattern matches
goodmorning
1 off off GOODMORNING 4
2 off on GOODMORNING 3
GOODMORNING
3 on off GOODMORNING 1 GoodMorning
4 on on GOODMORNING 1 GoodMorningVietnam
5 off off goodmorning 4
6 off on goodmorning 3 • Data driven script:
7 on off goodmorning 1 for each line in the file do
8 on on goodmorning 1 open the find dialog
9 off off GoodMorning 4 read a line from the file
10 off on GoodMorning 3 use the values to fill dialog
11 on off GoodMorning 2 press find button
12 on on GoodMorning 1 check amount of matches
close the dialog
34. (Scripting) Data-Driven
Approach
• Pros
– Separation of action and data enables tests to receive
combinations of test data
– Test data can be stored in a separate file or spreadsheet for better
maintainability
– Improved reusability and maintainability
• Cons
– Actions containing business logic are in automated scripts
– Maintainability of changes in business logics as well as interface is
still poor
– Poor visibility because accessibility to the tests is still poor
– Not scalable (e.g., reaching 95% of automation)
35. Test Automation
Challenges
• Too much programming
• Response to rate of changes (software)
• Low reusability/scalability
• Too many platforms/technologies
• Too expensive if the returned value is low
36. Keyword-driven
CHAPTER 10.6
Tests are broken down into a series of actions representing the
business processes of the SUT, such as ‘enter client’, ‘transfer’, and
‘check balance’.
Individual actions are automated, not the tests.
The tests are stored externally from the test scripts, typically in a
spreadsheet.
Keyword-based test automation’s elegant, structured approach
simplifies the work even further, reducing the time and expense of test
design, automation, and execution by allowing team members to focus
on their areas of individual expertise.
Non-technical testers and business analysts can develop executable
test automation from keywords representing recognizable end-user
actions.
37. How Does ABT
(Action-keyword) Work?
Test Cases are written or described through a series of Test Lines using
parameterized and reusable Action keywords
Action’s Parameters
Action keyword Number Name Description
Test Line add product 12345678 Hammer For pounding nails
Actions are created and communicate with target systems and software
applications including the application under test (AUT) through one or more
supported Interfaces to carry out intended tasks
Note:
For now, think of an Action as a verb or something that you do
Information about Interfaces such as Windows, Web or Java graphical user
interface (GUI) or command-line interface (CLM) are later defined to enable
actions to send inputs to and receive outputs from the target system and/or
AUT
38. Overcome Challenges w/ Action Based Testing
• Separation of action, interface, logic and data
• Test data can go in a separate file or spreadsheet
• Test logic can go in a separate file or spreadsheet
• Interface can go in a separate file or spreadsheet
• Action can also go in a separate file or spreadsheet
• Action can be reused
39. Automation Approach
Comparison
CHAPTER 10.6
Workload Allocation
Approach Test Data
Automation Test Case
Construction /
Engineering Production
Selection
Record &
N/A Test Engineer N/A
Playback
Automation Automation
Scripting Engineer Engineer
N/A
Automation Automation
Data-driven Engineer Engineer
Test Engineer
Automation
Keyword-driven Engineer
Test Engineer Test Engineer
Note: Programming skill is required for Automation Engineer
40. Examples of Test
CHAPTER 10.6 Automation Tools
LogiGear is the producer of TestArchitect™, a functional automated testing tool
designed to help achieve the most efficiency out of action-keyword test
automation. Examples of other commercial tool vendors include:
Automation HP IBM Others
Tool
Functional WinRunner Functional Tester SilkTest
QuickTestPro Rational Robot TestPartner
TestComplete
Performance LoadRunner Performance Tester SilkPerformer
AstraLoad Test WebLoad
OpenSTA
Management Test Director Rational TestManager SilkCentral Test
Quality Center Manager
Memory Purify JProbe Profiler
41. CHAPTER 10
SUMMARY
• Test Automation is a method that uses of software to control
the execution of tests.
• Commonly, test automation involves automating a manual
process currently in.
• Test Automation has benefits such as…However, it still has
some pitfalls such as…
• A effective strategy of test automation includes several steps…
• There are many popular automation tools. Depend on the
AUT, we choose the suitable automation testing tool.
42. CHAPTER 10
QUIZ
• What are the advantages and disadvantages of test
automation?
• What are the advantages and disadvantages of test
automation generations?
Editor's Notes
Theory of testing automation-
Help to release higher quality product: because more exactly: automation is more exactly than manual way. faster: test coverage is higher than human do On time?? computer execute quickly and inconsistently Sure … but you need have good plan & execution. Because when you start implementing your script, it means that you can face to solve many following automation problems goal of automation: + reduce cost when your AUT has new upgrade/version: just need to re-execute the script again to test + exact result- Problem which we try to solve in automation is how to implement your script become stable, reusable & effective
Better user of qualified in-house testing resourcesTedious happens at repetitive task and use most our resource so automation release tester for creative tasksCan’t test manuallyLoad test, performance test, stability testAutomation save time, money and release manual testing skillExplain reason- Load test, performance test,
Smoke, user acceptance, functional test need to retestAutomate testing only do paths I indicate but tester can work around the paths to discover more bugsHow many bugs might I lose and when
Follow the idea of slideThe talent tester do automation or maintenance scripts then there isn’t enough good person do the test => test productivity decreasesOn the side la song song hay congviecphu
Follow the idea of slideNeed explain moreWhat is good-enough automationTightening the testing cycle
Give explanation of this comparison
Run Automatic totally1. Run unit test; 2. Build new version; 3. Check new build; 4. Download; 5. Remove old build, install new build6. Run smoke test and email result to everyone related; 7. Run another test typeReusable and scalable if architected effectivelyArchitected effectively: Module, Action , Interface, …Scalable: when logic change we just modify at one position
This point can regard as the weak of automation, follow the idea of the slideUncertainty and lack of controlWhen program change much cause the application of automation difficultlyFocus on making the test run instead of quality of testWhat is quality of test?
Follow the slide, give example for this.Some reasons can become from the client – customer, they want us to test application as soon as possible, so we didn’t have time to implement script… just focus on manual test to report bugs as much as possible- usability: nice, fast, …
Follow the slideApplication should be stableis at phase system and user acceptanceTools for stress, load and performance testRobust script of IBMMS VS test team support unit, performance testBooksTesting computer software
Automation delivery summary reportTest scopeWhat completedWhat we seeTest case amountComplete percentTotal run time of automation per computerRegression on function coverRun result on each environment
Follow the slide & give example via any automation tool (such as: TA)
Explain the diagram, the way to work
example
Follow the slideRecord/playback bases on coordinate.You can give some questions to your class, also.
This is the generation 2
Follow the slide
Win runner application
Silk tool
This is the generation 3- There is no explain on this slide
Follow the slide- Not scalable: logic changed must be maintain script
Challenge of data driven (generation 3)Response slowly to rate of software changesLow reusability/scalability: logic in programming
Follow the slide ( try a demo via TA tool)
Follow the slideTest engineers are black-box testersAutomation engineers are programmers
Compare some testing tool. Can give question to learner: Have you ever used any testing tool in this list? Or have you ever heard about them?winRunner is previous one of QTPTest director is previous one of Quality Center
Give summary to your class to close this chapter.Some questions you can give: - How many testing generation? 4 - Could you please list out the name of them? Record & play back, scripting, data driven, action keyword - Which strong point / weak point of automation?…