Selenium done right
•Download as PPTX, PDF•
0 likes•50 views
This document summarizes the improvements made to an organization's Selenium test automation over the past year. Some key points: - Originally there were 1500 tests with a pass rate below 70% that took 3.5 hours to run. Now there are over 3000 tests with a pass rate above 99% that take less than 15 minutes to run. - A focus on short, stable test flows and improved visualization of test results helped drive these gains. Architectural changes like implementing the WWHB (What, Where, How, Browser) design pattern also contributed significantly. - Maintaining clean, well-architected code is important to ensure the reliability and sustainability of test automation. The document emphasizes treating automation tests as
Report
Share
Report
Share
Recommended
Fast end-to-end-tests
This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Extreme Programming - to the next-level
This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Automated Performance Testing
If you are like most test driven developers, you write automated tests for your software to get fast feedback about potential problems. Most of the tests you write will verify the functional behaviour of the software: When we call this function or press this button, the expected result is that value or that message.
But what about the non-functional behaviour, such as performance: When we perform this query the expected speed of getting results should be no more than that many milliseconds. It is important to be able to write automated performance tests as well, because they can give us early feedback about potential performance problems. But expected performance is not as clear-cut as expected results. Expected results are either correct or wrong. Expected performance is more like a threshold: If the performance is worse than this, we want the test to fail.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Unit testing
This document provides an overview of unit testing and guidelines for writing unit tests. It discusses why unit tests are important for catching errors, helping write code, speeding up development, and covering configurations and new team members' code. It defines what a unit test is and what they don't cover. Guidelines provided include automating tests, letting code just pass tests, testing boundaries and randomness, keeping tests at a unit level, and knowing passed tests don't guarantee correctness. It also mentions the XCTest framework and provides a tutorial project and instructions for writing sample unit tests for email and password validation.
Елена Панина - Drupal performance testing. Тестирование производительности, м...
Performance testing of a Drupal site can help identify issues, evaluate optimization effectiveness, and report results to clients. Tools like JMeter are used to test criteria such as response time, throughput, and hits per second by emulating user behavior under increasing load. For one project, response time dropped from 9,000ms to 330ms, throughput increased from 6.2 to 114 transactions/second, and hits per second rose from 4 to 100 after optimizing caching with Memcache, ESI, and Varnish configuration. Caching code, functions, views, databases requests, HTML, images, and static assets can improve performance.
testmon for Python
testmon for Python concepts and IndieGoGo campaign. Slides for presentation on a local Ruby and Python meet-up.
Sh00t - defcon presentation
Security Testing is not as simple as right click > Scan. It's messy, a tough game. What if you had missed to test just that one thing and had to regret later? Sh00t is a highly customizable, intelligent platform that understands the life of bug hunters and emphasizes on manual security testing.
Recommended
Fast end-to-end-tests
This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Extreme Programming - to the next-level
This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Automated Performance Testing
If you are like most test driven developers, you write automated tests for your software to get fast feedback about potential problems. Most of the tests you write will verify the functional behaviour of the software: When we call this function or press this button, the expected result is that value or that message.
But what about the non-functional behaviour, such as performance: When we perform this query the expected speed of getting results should be no more than that many milliseconds. It is important to be able to write automated performance tests as well, because they can give us early feedback about potential performance problems. But expected performance is not as clear-cut as expected results. Expected results are either correct or wrong. Expected performance is more like a threshold: If the performance is worse than this, we want the test to fail.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Unit testing
This document provides an overview of unit testing and guidelines for writing unit tests. It discusses why unit tests are important for catching errors, helping write code, speeding up development, and covering configurations and new team members' code. It defines what a unit test is and what they don't cover. Guidelines provided include automating tests, letting code just pass tests, testing boundaries and randomness, keeping tests at a unit level, and knowing passed tests don't guarantee correctness. It also mentions the XCTest framework and provides a tutorial project and instructions for writing sample unit tests for email and password validation.
Елена Панина - Drupal performance testing. Тестирование производительности, м...
Performance testing of a Drupal site can help identify issues, evaluate optimization effectiveness, and report results to clients. Tools like JMeter are used to test criteria such as response time, throughput, and hits per second by emulating user behavior under increasing load. For one project, response time dropped from 9,000ms to 330ms, throughput increased from 6.2 to 114 transactions/second, and hits per second rose from 4 to 100 after optimizing caching with Memcache, ESI, and Varnish configuration. Caching code, functions, views, databases requests, HTML, images, and static assets can improve performance.
testmon for Python
testmon for Python concepts and IndieGoGo campaign. Slides for presentation on a local Ruby and Python meet-up.
Sh00t - defcon presentation
Security Testing is not as simple as right click > Scan. It's messy, a tough game. What if you had missed to test just that one thing and had to regret later? Sh00t is a highly customizable, intelligent platform that understands the life of bug hunters and emphasizes on manual security testing.
Ruin your life using robot framework
This document discusses best practices and pitfalls when using the Robot Framework for test automation. It recommends starting with acceptance test-driven development (ATDD) and using source control and continuous integration. Other tips include giving tests and elements descriptive names, writing test cases as independent steps with single assertions, avoiding dependencies between tests, and focusing on behavior rather than implementation details. The document warns against not using these practices as they can lead to fragile and unreliable tests, wasted time and resources, and regressions going unnoticed.
Ui Testing with Ghost Inspector
Jay Luker will be presenting an introduction to Ghost Inspector, a cloud-based web UI testing service that takes some (some!) of the pain away from creating browser-based, web application tests. Think Selenium, but for projects that are short on the resources, infrastructure and/or coding expertise to confidently develop and manage a suite of fully automated, “good-enough” UI tests.
Jay is a Senior Software Engineer at Harvard DCE where he works on back-end applications and software for analytics data collection, deployment automation, and integration testing for the Extension School’s video processing and delivery system. Previously he has been an IT Specialist at the Smithsonian Astrophysics Data System, and a Software Developer at Ex Libris.
Gatling Performance Workshop
This document provides an overview of Gatling, an open-source load testing tool developed using Scala. It discusses Gatling's focus on web applications, simplicity, high performance, good reports, and easy integration with CI tools. It then covers setting up Gatling, including prerequisites, writing a sample test, and key concepts like scenarios, simulations, and reports.
Keeping up with the changes: Automating UAT - Damian Sweeney, Student and Aca...
A consistent user experience is key for providing certainty to staff and students using the LMS, and creates the foundational bedrock on which academic innovation and engagement can flourish. Blackboard service pack upgrades, cumulative updates, patching and system refreshes can introduce inadvertent modifications to privileges, tool settings, system configuration and user workflow over time. Detecting and managing these changes to the user experience is a critical task, but also very complex and time-consuming.
The University of Melbourne’s user acceptance testing (UAT) process traditionally included ~1,000 tests. A significant portion of these UAT activities have now been automated, allowing quick assessment of system configuration and basic functionality (often of several systems at once), leading to faster detection of system discrepancies. It has also reduced the time for UAT by ~50% – very welcome for those who perform the testing! The solution uses a combination of background scripting (Python and Selenium) and monitored automatic processes (Selenium IDE plugin for Firefox). This presentation will demonstrate the automated process, and the related team processes for dissemination of scripts and monitoring findings.
Delivered at Innovate and Educate: Teaching and Learning Conference by Blackboard. 24 -27 August 2015 in Adelaide, Australia.
Accomplishment report at QNAP
This document summarizes a QNAP intern's report on using the Robot Framework for automated regression testing. It discusses how the framework allows tests to be written once and run every time with each new build. Test cases are stored as text files for version control and can be executed from the command line. The intern demonstrated how automated regression testing found issues across multiple builds and shortened the regression cycle to improve software quality while relieving testers. In conclusion, experienced testers' knowledge was translated to Robot Framework scripts to continue benefiting future testing efforts.
Background threads, async communication and vaadin
Vaadin DevDay 2016 presentation about background threads, asynchronous communication, server push and Vaadin.
Introduction to K6
This document provides an overview and demonstration of K6, an open-source load testing tool. It discusses key aspects of K6 including what it is, why it should be used, and how to perform load testing with its various components. The document demonstrates K6's capabilities for load testing APIs, microservices, and websites using JavaScript scripts. It also shows how to integrate K6 with CI/CD pipelines using GitHub Actions.
Keeping business logic out of your UIs
This document discusses keeping business logic out of user interfaces (UIs) by separating the UI layer from the business logic layer. It recommends:
- Placing the transaction boundary between the UI and backend to minimize backend calls.
- Ensuring service layers are highly cohesive and avoid general "god services".
- Separating reading data (queries) from writing data (commands) to allow for optimizations.
- Avoiding CRUD-style UIs and services that move business logic into the user's head, and base UIs and services on actual business processes instead.
- Considering introducing a command-based architecture where commands and queries model business operations to further separate business logic from the UI.
JavaSkop - Automation Skopje
The document discusses the need for automated testing over manual testing. It introduces Selenium, an open source tool that automates testing of web applications across browsers. Key benefits of Selenium mentioned include higher test coverage, freeing up time for more creative testing, and testing across browsers and platforms. The document provides examples of advanced Selenium features like grids for distributed testing and generating different test reports. It ends by listing some useful tutorial links for learning more about automated testing frameworks and Selenium.
Value of Unit Testing
This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.
Picking the right architecture and sticking to it
The document provides guidance on choosing an architecture for a project, sticking to it, and evolving it over time. It emphasizes doing research upfront on project scope, requirements, and potential risks. The initial design should consider experimenting with new approaches but also prototyping risky features. Future changes should be considered but not overdesigned for. The architecture must be documented and explained to the team. Tests and code reviews help ensure the architecture is followed. While 90% of features can be implemented as designed, the architecture must be flexible to handle unexpected changes through open communication and potential compromises.
Meetup React Sanca - 29/11/18 - React Testing
Talk a respeito de testes automatizados no frontend (E2E, integração, unitários e visual), dando destaque a aplicações React. A talk foca na utilização da biblioteca react-testing-library desenvolvida por Kent C. Dodds em 2018. Nela, explico o porquê de optarmos por ela, em quais casos ela melhor se aplica e dou alguns exemplos de utilização.
Overview of Testing Talks at Pycon
These slides were presented at the April 2012 Django District meetup. More information & be found here: http://bit.ly/JRgpkf.
Mocking in python
Daniel Davis is a software developer with 8 years of experience who now focuses on Python development and DevOps. He discusses his journey learning about unit testing and how mocking strategies can make testing easier. Mocking eliminates dependencies, allows testing of methods without return values, and helps test error handling. Various Python mocking libraries are presented. Examples show how to use mocking to test a matching algorithm in a dating app and to test a JSON reader class. The key benefits of mocking are that it simplifies unit tests by handling dependencies and verifying method behavior.
My Test Automation Journey
This document summarizes the author's journey with test automation and lessons learned. It discusses using the driver pattern to clean up complicated test logic, abstract implementation from business logic, and make tests reusable. It also discusses using page object pattern for graphical user interface testing, similarly encapsulating selector logic. The author advocates for testers and programmers to work together, treating automation as a craft to develop over time, and ensuring quality by maintaining tests to avoid technical debt later on.
Akka Persistence
Akka persistence enables stateful actors to persist in their internal state so that it can be recovered when an actor is started, restarted after a JVM crash or by a supervisor, or migrated in a cluster. The key concept behind Akka persistence is that only changes to an actor’s internal state are persisted but never its current state directly (except for optional snapshots). These changes are only ever appended to storage, nothing is ever mutated, which allows for very high transaction rates and efficient replication. Stateful actors are recovered by replaying stored changes to these actors from which they can rebuild internal state. This can be either the full history of changes or starting from a snapshot which can dramatically reduce recovery times. Akka persistence also provides point-to-point communication with at-least-once message delivery semantics.
Test driving QML
How to test-drive your Qt QML code. Overview on how you do simple testing, UI level testing, synchronous testing, data-driven testing.
These are the slides used on the Tampere MeeGo meetup on March 15, 2011 and text may not be super clear for those who didn't attend the meetup. You can still download the example and examine it.
How to go about testing in React?
Presentation for my talk at the JavaScript Matters meetup organized by Skills Matter on 11/03/2019 in London, UK.
Improve the deployment process step by step
This document summarizes steps to improve the software deployment process. It recommends using Git for deployment to enable faster switching between versions. It also discusses techniques like blue/green deployments to prevent errors from file changes during requests and maintaining two identical environments that can be switched between. The document stresses the importance of making database migrations harmless and avoiding code that doesn't work without migrations. It provides tips for measuring deployment success and reducing fear of deployments.
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...MobileMonday Estonia
This document discusses different types of frontend testing, including manual vs automated testing. Manual testing has advantages like low costs and understanding user experience, but is repetitive and tests cannot be reused. Automated testing is more efficient long-term as tests can be run by anyone and retesting is easy, but requires upfront work. Unit testing tests individual functions separately, while end-to-end testing simulates user workflows in a browser. Popular frameworks for frontend testing include Jasmine for unit tests, Selenium for end-to-end tests, and Protractor for testing Angular apps.Automated testing
1) Automated testing can help accelerate time to market, improve productivity and efficiency, and provide reliable releases by continuously testing software as it is being developed.
2) There are different types of automated tests like unit tests, integration tests, and end-to-end tests that test the functionality of different parts of the software. Tests can be automated using tools like Selenium for user interface testing and SpecFlow with RestSharp for API testing.
3) It is important to run automated tests frequently, keep them in a passing state, include tests in definition of done, and automate bugfix tests to help catch regressions. Page object pattern and test-driven development approaches can help structure automated tests effectively.
Wso2con test-automation
The document discusses effective test automation practices in an agile environment. It outlines the benefits of automated testing such as early feedback, safety net for manual tests, and ability to run tests unattended. It presents success stories from companies like Google, Ebay, Facebook, and Amazon on their extensive use of automated testing. The document also covers test automation techniques like the test pyramid, WSO2's test automation framework, continuous integration, and continuous delivery. It emphasizes the importance of selecting the right tools, processes, and team for successful test automation.
More Related Content
What's hot
Ruin your life using robot framework
This document discusses best practices and pitfalls when using the Robot Framework for test automation. It recommends starting with acceptance test-driven development (ATDD) and using source control and continuous integration. Other tips include giving tests and elements descriptive names, writing test cases as independent steps with single assertions, avoiding dependencies between tests, and focusing on behavior rather than implementation details. The document warns against not using these practices as they can lead to fragile and unreliable tests, wasted time and resources, and regressions going unnoticed.
Ui Testing with Ghost Inspector
Jay Luker will be presenting an introduction to Ghost Inspector, a cloud-based web UI testing service that takes some (some!) of the pain away from creating browser-based, web application tests. Think Selenium, but for projects that are short on the resources, infrastructure and/or coding expertise to confidently develop and manage a suite of fully automated, “good-enough” UI tests.
Jay is a Senior Software Engineer at Harvard DCE where he works on back-end applications and software for analytics data collection, deployment automation, and integration testing for the Extension School’s video processing and delivery system. Previously he has been an IT Specialist at the Smithsonian Astrophysics Data System, and a Software Developer at Ex Libris.
Gatling Performance Workshop
This document provides an overview of Gatling, an open-source load testing tool developed using Scala. It discusses Gatling's focus on web applications, simplicity, high performance, good reports, and easy integration with CI tools. It then covers setting up Gatling, including prerequisites, writing a sample test, and key concepts like scenarios, simulations, and reports.
Keeping up with the changes: Automating UAT - Damian Sweeney, Student and Aca...
A consistent user experience is key for providing certainty to staff and students using the LMS, and creates the foundational bedrock on which academic innovation and engagement can flourish. Blackboard service pack upgrades, cumulative updates, patching and system refreshes can introduce inadvertent modifications to privileges, tool settings, system configuration and user workflow over time. Detecting and managing these changes to the user experience is a critical task, but also very complex and time-consuming.
The University of Melbourne’s user acceptance testing (UAT) process traditionally included ~1,000 tests. A significant portion of these UAT activities have now been automated, allowing quick assessment of system configuration and basic functionality (often of several systems at once), leading to faster detection of system discrepancies. It has also reduced the time for UAT by ~50% – very welcome for those who perform the testing! The solution uses a combination of background scripting (Python and Selenium) and monitored automatic processes (Selenium IDE plugin for Firefox). This presentation will demonstrate the automated process, and the related team processes for dissemination of scripts and monitoring findings.
Delivered at Innovate and Educate: Teaching and Learning Conference by Blackboard. 24 -27 August 2015 in Adelaide, Australia.
Accomplishment report at QNAP
This document summarizes a QNAP intern's report on using the Robot Framework for automated regression testing. It discusses how the framework allows tests to be written once and run every time with each new build. Test cases are stored as text files for version control and can be executed from the command line. The intern demonstrated how automated regression testing found issues across multiple builds and shortened the regression cycle to improve software quality while relieving testers. In conclusion, experienced testers' knowledge was translated to Robot Framework scripts to continue benefiting future testing efforts.
Background threads, async communication and vaadin
Vaadin DevDay 2016 presentation about background threads, asynchronous communication, server push and Vaadin.
Introduction to K6
This document provides an overview and demonstration of K6, an open-source load testing tool. It discusses key aspects of K6 including what it is, why it should be used, and how to perform load testing with its various components. The document demonstrates K6's capabilities for load testing APIs, microservices, and websites using JavaScript scripts. It also shows how to integrate K6 with CI/CD pipelines using GitHub Actions.
Keeping business logic out of your UIs
This document discusses keeping business logic out of user interfaces (UIs) by separating the UI layer from the business logic layer. It recommends:
- Placing the transaction boundary between the UI and backend to minimize backend calls.
- Ensuring service layers are highly cohesive and avoid general "god services".
- Separating reading data (queries) from writing data (commands) to allow for optimizations.
- Avoiding CRUD-style UIs and services that move business logic into the user's head, and base UIs and services on actual business processes instead.
- Considering introducing a command-based architecture where commands and queries model business operations to further separate business logic from the UI.
JavaSkop - Automation Skopje
The document discusses the need for automated testing over manual testing. It introduces Selenium, an open source tool that automates testing of web applications across browsers. Key benefits of Selenium mentioned include higher test coverage, freeing up time for more creative testing, and testing across browsers and platforms. The document provides examples of advanced Selenium features like grids for distributed testing and generating different test reports. It ends by listing some useful tutorial links for learning more about automated testing frameworks and Selenium.
Value of Unit Testing
This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.
Picking the right architecture and sticking to it
The document provides guidance on choosing an architecture for a project, sticking to it, and evolving it over time. It emphasizes doing research upfront on project scope, requirements, and potential risks. The initial design should consider experimenting with new approaches but also prototyping risky features. Future changes should be considered but not overdesigned for. The architecture must be documented and explained to the team. Tests and code reviews help ensure the architecture is followed. While 90% of features can be implemented as designed, the architecture must be flexible to handle unexpected changes through open communication and potential compromises.
Meetup React Sanca - 29/11/18 - React Testing
Talk a respeito de testes automatizados no frontend (E2E, integração, unitários e visual), dando destaque a aplicações React. A talk foca na utilização da biblioteca react-testing-library desenvolvida por Kent C. Dodds em 2018. Nela, explico o porquê de optarmos por ela, em quais casos ela melhor se aplica e dou alguns exemplos de utilização.
Overview of Testing Talks at Pycon
These slides were presented at the April 2012 Django District meetup. More information & be found here: http://bit.ly/JRgpkf.
Mocking in python
Daniel Davis is a software developer with 8 years of experience who now focuses on Python development and DevOps. He discusses his journey learning about unit testing and how mocking strategies can make testing easier. Mocking eliminates dependencies, allows testing of methods without return values, and helps test error handling. Various Python mocking libraries are presented. Examples show how to use mocking to test a matching algorithm in a dating app and to test a JSON reader class. The key benefits of mocking are that it simplifies unit tests by handling dependencies and verifying method behavior.
My Test Automation Journey
This document summarizes the author's journey with test automation and lessons learned. It discusses using the driver pattern to clean up complicated test logic, abstract implementation from business logic, and make tests reusable. It also discusses using page object pattern for graphical user interface testing, similarly encapsulating selector logic. The author advocates for testers and programmers to work together, treating automation as a craft to develop over time, and ensuring quality by maintaining tests to avoid technical debt later on.
Akka Persistence
Akka persistence enables stateful actors to persist in their internal state so that it can be recovered when an actor is started, restarted after a JVM crash or by a supervisor, or migrated in a cluster. The key concept behind Akka persistence is that only changes to an actor’s internal state are persisted but never its current state directly (except for optional snapshots). These changes are only ever appended to storage, nothing is ever mutated, which allows for very high transaction rates and efficient replication. Stateful actors are recovered by replaying stored changes to these actors from which they can rebuild internal state. This can be either the full history of changes or starting from a snapshot which can dramatically reduce recovery times. Akka persistence also provides point-to-point communication with at-least-once message delivery semantics.
Test driving QML
How to test-drive your Qt QML code. Overview on how you do simple testing, UI level testing, synchronous testing, data-driven testing.
These are the slides used on the Tampere MeeGo meetup on March 15, 2011 and text may not be super clear for those who didn't attend the meetup. You can still download the example and examine it.
How to go about testing in React?
Presentation for my talk at the JavaScript Matters meetup organized by Skills Matter on 11/03/2019 in London, UK.
Improve the deployment process step by step
This document summarizes steps to improve the software deployment process. It recommends using Git for deployment to enable faster switching between versions. It also discusses techniques like blue/green deployments to prevent errors from file changes during requests and maintaining two identical environments that can be switched between. The document stresses the importance of making database migrations harmless and avoiding code that doesn't work without migrations. It provides tips for measuring deployment success and reducing fear of deployments.
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...MobileMonday Estonia
This document discusses different types of frontend testing, including manual vs automated testing. Manual testing has advantages like low costs and understanding user experience, but is repetitive and tests cannot be reused. Automated testing is more efficient long-term as tests can be run by anyone and retesting is easy, but requires upfront work. Unit testing tests individual functions separately, while end-to-end testing simulates user workflows in a browser. Popular frameworks for frontend testing include Jasmine for unit tests, Selenium for end-to-end tests, and Protractor for testing Angular apps.What's hot (20)
Keeping up with the changes: Automating UAT - Damian Sweeney, Student and Aca...
Keeping up with the changes: Automating UAT - Damian Sweeney, Student and Aca...
Background threads, async communication and vaadin
Background threads, async communication and vaadin
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...
Front-end Testing (manual, automated, you name it) - Erich Jagomägis - Develo...
Similar to Selenium done right
Automated testing
1) Automated testing can help accelerate time to market, improve productivity and efficiency, and provide reliable releases by continuously testing software as it is being developed.
2) There are different types of automated tests like unit tests, integration tests, and end-to-end tests that test the functionality of different parts of the software. Tests can be automated using tools like Selenium for user interface testing and SpecFlow with RestSharp for API testing.
3) It is important to run automated tests frequently, keep them in a passing state, include tests in definition of done, and automate bugfix tests to help catch regressions. Page object pattern and test-driven development approaches can help structure automated tests effectively.
Wso2con test-automation
The document discusses effective test automation practices in an agile environment. It outlines the benefits of automated testing such as early feedback, safety net for manual tests, and ability to run tests unattended. It presents success stories from companies like Google, Ebay, Facebook, and Amazon on their extensive use of automated testing. The document also covers test automation techniques like the test pyramid, WSO2's test automation framework, continuous integration, and continuous delivery. It emphasizes the importance of selecting the right tools, processes, and team for successful test automation.
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
WSO2Con Asia 2014 - Effective Test Automation in an Agile Environment
The document discusses effective test automation strategies in an agile environment. It begins by defining automated testing and its goals of reducing manual testing while still providing coverage. Success stories from companies like Google, Facebook, and Amazon are provided that demonstrate how extensive automation allows for rapid deployment schedules. The test automation pyramid concept of testing at different levels from units to APIs to interfaces is introduced. The rest of the document covers the WSO2 test automation framework, lessons learned around maintaining automation, and the benefits of continuous integration/delivery.
Introduction to Test Automation
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.
Automation is Easy! (python version)
How to cover your web pages with easy tests in Python using easy wrapper over selenium of Selenide style. What are the styles of test coverage? How to start automation on your project? Which tool to choose?
This is a presentation to correspondent workshop (in russian) happened to have place in Kiev, during "Black Tea Testing #8" testing event, organized by Cogniance (cogniance.com) and IT Labs (itlabs.net.ua).
See video (in russian) at https://youtu.be/m1lopvj4nNg
See code src at https://github.com/yashaka/easy-web-tests-python/
How to establish ways of working that allows shifting-left of the automation ...
Why Automate?
Your application will grow, you will not have enough hands
You are blocked by development
Hidden factory costs of bug-fix cycle
Why Shift-Left?
More people to negate massive inspections
Define measurable success early, work on good parts.
Reduce occurrence of defects
What is this got to do with Ways of working?
Unlock capacity
Make people smile
Is not
a Department
extra cost
a final oversight or a massive inspection
someone else’s job
Is
Everyone’s responsibility
Build into the ways of working
Everyone’s job
Getting started with unit and functional testing
This document discusses the importance of testing code and different types of tests. It covers unit tests, integration tests, and end-to-end tests, explaining what each tests and providing examples. It also discusses best practices for writing good unit and integration tests, including testing behavior not implementation, avoiding dependencies, and using mocking and dependency injection. The goal is to establish a culture of testing code to ensure quality and prevent bugs.
High Performance Software Engineering Teams
Based on my experiences building high performance engineering teams, this presentation focuses on the technical practices required. These practices centers around automation (build, test and deployment) and increased collaboration between Engineering and QA (TDD, exploratory testing, prioritization, feedback cycles).
Unit Testing and TDD 2017
Conferencia realizada en pasado enero'17 en las jornadas organizadas por expoqa. También usada en el grupo de meetup Agile-Lleida.
OutSystems Tips and Tricks
When setting up a new project we have some tips and tricks to help you do this in the best way possible, incl. infrastructure, database, standard attributes, logging, code alignment, and service center.
Quality Assurance: An Overview
The document discusses quality assurance (QA), which aims to prevent defects by ensuring systems meet requirements, work as expected, and satisfy stakeholders. It defines verification as confirming correct development and validation as building the right product. Key QA activities include technical reviews of work products and software testing approaches like unit, integration, and regression testing. The goals of QA are to verify that software meets its design specifications and works as intended.
Test-Driven Development (TDD) in Swift
The document discusses test-driven development (TDD) in Swift. It explains that TDD involves writing tests before implementation to gain confidence and verify requirements are met. Automated tests allow for faster regression testing, easier refactoring, and continuous integration. The document recommends writing tests first to produce loosely coupled code aligned with requirements. It provides examples of TDD best practices and common pitfalls to avoid.
Tdd in swift
1. The document discusses test-driven development (TDD) in Swift, including why it is important to write tests before implementation. Automated tests provide confidence, verification of requirements, and help identify weak areas of code.
2. TDD involves writing tests first to define requirements before writing any code. This forces developers to think about design and creates loosely coupled, independent code modules.
3. Common pitfalls to avoid in TDD include not testing behaviors, having dependent tests, not refactoring code, and testing private methods or external libraries. Best practices include using a good architecture, protocols to isolate classes, and structured tests with arrange, act, assert format.
RandomTest - Random Software Integration Tests That Just Work for C/C++, Java...
This document describes RandomTest.net, a tool for generating random integration tests. It discusses some limitations of traditional unit and manual testing approaches. RandomTest.net aims to minimize QA effort through test automation using random inputs and assertions to verify results. Developers embed assertions in code and RandomTest.net randomly executes code sections to detect failures. Any failed assertions are collected in a central repository. The tool currently supports C/C++, Java and PHP with more languages to come. It is open source and additional documentation can be found at randomtest.net.
Making cross browser tests beautiful
How many times have your Selenium test suites run beautifully on one browser, only to fail when run in any other browser? This is an extremely common problem faced when incorporating cross-browser tests into your test runs. Not all browser drivers are created equally, but that doesn’t mean you can’t create a robust suite of cross-browser tests.
This presentation shares strategies for making cross-browser tests invincible. It focuses on topics such as using as choosing the best locators for all browsers, explicit vs. implicit waits and how to leverage cloud-based testing tools.
This presentation was given at SeleniumConf London in November 2016.
Release & Iterate Faster: Stop Manual Testing
The document discusses LinkedIn's "3x3" approach to software development, which aims to release code three times per day within three hours of a code commit. It outlines the challenges with their previous release process and describes how they implemented continuous integration, automated testing, and distribution methods to achieve much faster release cycles. Key aspects included static analysis, unit testing, automated UI testing across emulators in parallel, and distributing builds to alpha, beta, and production channels on Google Play. The approach enabled LinkedIn to release code over 130 times per year and get feedback from users much more quickly.
Demise of test scripts rise of test ideas
Tired of doing upfront test script creation in your testing efforts? Feeling bad for demotivating your testers? Want something to replace this sickening approach to software testing? This presentation outlines why test scripts are not useful, and how test ideas are the new way forward to better testing. Coverage, traceability, reporting, automation and skills are all covered. Take a quick look and see if you can see there is another way to do software testing that is actually pure common sense.
Best practices for JavaScript RIAs
This document discusses best practices for building JavaScript rich internet applications (RIAs). It covers topics like testing techniques, design patterns, testing tools, and approaches like test-driven development. Some of the key recommendations include writing code for humans rather than machines, keeping servers simple as an event bus between clients, and focusing on concepts rather than specific tools. Test-driven development is emphasized as important for code quality and maintainability.
Test automation - Building effective solutions
This presentation is answering the questions: how to build an effective test automation framework, select the right tools and organize to whole process?
Similar to Selenium done right (20)
WSO2Con Asia 2014 - Effective Test Automation in an Agile Environment
WSO2Con Asia 2014 - Effective Test Automation in an Agile Environment
How to establish ways of working that allows shifting-left of the automation ...
How to establish ways of working that allows shifting-left of the automation ...
RandomTest - Random Software Integration Tests That Just Work for C/C++, Java...
RandomTest - Random Software Integration Tests That Just Work for C/C++, Java...
Recently uploaded
Transform Your Communication with Cloud-Based IVR Solutions
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
What is Master Data Management by PiLog Group
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Graspan: A Big Data System for Big Code Analysis
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
原版定制美国纽约州立大学奥尔巴尼分校毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国纽约州立大学奥尔巴尼分校毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers. This video you can watch from my youtube channel at https://youtu.be/m-F-mZA3MkU
A Study of Variable-Role-based Feature Enrichment in Neural Models of Code
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
Recently uploaded (20)
Transform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR Solutions
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers.pptx
A Study of Variable-Role-based Feature Enrichment in Neural Models of Code
A Study of Variable-Role-based Feature Enrichment in Neural Models of Code
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
Selenium done right
- 1. Duda Selenium Automation MAIN ASPECTS Aug 2017
- 3. ● About 1500 Selenium tests ● pass rate < 70% ● 3.5 hours for the entire suite ● Once a day ● Maintenance ~ 30% ● No one really cares about automation apart from the QA team ● 2.5 automation developers One Year Ago Now ● Over 3000 Selenium tests ● pass rate > 99% ● Less than 15 minutes for the entire suite ● 30 times a day on different code branches ● Maintenance less than 5% ● Dev is fully committed to keep automation tests clean ● 2.5 automation developers
- 4. What Made The Difference Architecture Change Short Test Flows Stable Tests Only Visualization
- 5. ● Focus on very specific checkpoints: ○ Run faster ○ Easy to debug ○ The failure is clear ● Api or other shortcuts usage for peripheral functions: ○ Get to the required condition via fastest and safest way ● Avoid using complicated flows ○ Only if absolutely a must ○ Avoid test dependencies Atomic Test Flows
- 6. ● Testing the new tests: ○ All new tests shall run successfully on a sanbox 30 times in a row ○ All tests must pass ○ Runtime < 200 sec per class ● Code Review: ○ Code review meeting with automation team ● Only after sandbox and code review, new tests are added to “production” XML (Very) Stable Tests Only
- 7. Visualize – Jenkins Pipeline
- 8. Visualize – Automation Dashboard
- 9. ● Short Test Flows ● Stable Tests Only ● Visualization/Immediate Feedback Wrapping Up
- 10. Selenium Done Right WWHB Design pattern
- 11. About me
- 12. UI Testing Weakness Bad selectors Scattered UI flow Bad waits and sleeps Tests prioritized Obfuscated code in tests Bad log report The small things video Asynchronous Browser Opening video
- 13. ● Automation tests are not scripts - they’re software. ● A software project should have a good design and architecture to overcome future challenges. ● The software developing team should be devoted to maintain a high quality code standard. ● “The chain is strong as its weakest link” ● It’s not enough if it works Automation Is Software
- 14. Like a glove
- 15. ● Clean code should be simple and direct ● Clean code should read like well written prose ● Clean code is when each routine you read is pretty much what you’ve expected ● A function should do one thing, it should do it well and it should do it only ● Clean code always looks like it was written by someone who cares Clean Code Robert Cecil Martin a.k.a Uncle bob
- 16. ● Selector properties ○ Unique ○ Meaningful ○ Low chance of change ● Be the change Selectors & API’s
- 17. WWHB Design Pattern ● What to test ● Where to find the elements ● How to execute the test ● The Browser
- 18. ● What: @Test ● Best practices ○ Small atomic tests - no priority ○ Setups and teardowns in every @Test ○ Think small - every function should be well thought of. In Assert use contains, toLowerCase… ○ Minimal logic in tests, only well written prose ○ Minimal global variables ● Measure your code ○ Test score system: url ○ Old navigation test: url ○ New navigation test: url What
- 19. ● Where: Page Objects ● In test findBy() -> elementfinder class per test -> @FindBy -> enum - > public static class ● Best practice ○ Minimal logic in page objects - only simple actions ○ No cross page object function calls Where THIS IS HUGE!!
- 20. ● How: Logics ● Structure of logics and inheritance ● Obstacles solved as part of the infrastructure, not ad hoc per test (publishSite, setText, Hover, importTemplates) How
- 21. BROWSE R TOUCHER ● The browser is the enemy - no one is doing element.click() element.getCssValue() driver.get() driver.findElement(by) …… Browser THIS IS ALSO HUGE!!!! Test suit
- 22. ● The browser is the enemy - no one is doing element.click() element.getCssValue() driver.get() driver.findElement(by) …… Browser BROWSE R TOUCHER Test suit
- 24. ● Extra: ● Smart waits and ExpectedCondition + stopwatch ● Static functions - no side effects ● Testng-failed.xml for retry ● Sandbox with test randomizer ● FocusOnIframe - open close principle Extra topics
- 25. ● Automation is software ● Clean code ● WWHB design pattern Conclusion
- 26. Thank You!