Introduction to Automated Testing
1 like1,622 views
The document provides an introduction to automated testing, emphasizing the importance of writing tests to improve software development efficiency and design. It outlines various types of automated tests, including unit tests and system tests, and discusses best practices for integrating testing into the development process. The presentation highlights real-world examples and tools available for automated testing, advocating for a culture that prioritizes test-driven development.
1 of 15
Downloaded 46 times
Ad
Recommended
Extreme Programming - to the next-level
Extreme Programming - to the next-levelLars Thorup 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
Automated Performance TestingLars Thorup Lars Thorup is a software developer and founder of Zealake, focused on automated performance testing and agile methodologies. The document discusses strategies for measuring performance, including the use of automated tests with tools like TeamCity and Jenkins, and emphasizes the importance of trend analysis for identifying performance issues. It highlights the need for ongoing inspection to maintain performance metrics and describes the performance reporting processes.
Fast end-to-end-tests
Fast end-to-end-testsRikke Veng Petersen 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.
Put "fast" back in "fast feedback"
Put "fast" back in "fast feedback"Lars Thorup The document emphasizes the importance of fast feedback in software development to enhance productivity, reduce risk, and lower the cost of change. It contrasts slow and fast feedback systems through various real-life examples and outlines criteria for achieving fast feedback, such as maintaining high unit test coverage and frequent commits. It advocates for adopting practices like test-driven development and continuous integration to promote faster, more efficient software delivery.
QA Strategies for Testing Legacy Web Apps
QA Strategies for Testing Legacy Web AppsRainforest QA Paul Miles outlines QA strategies for testing legacy web apps, emphasizing the importance of introducing automated tests for applications lacking them. The document advises starting with key workflows, using suitable tools, and implementing a phased approach to testing, incorporating unit and service tests into the build process. It also highlights the significance of static quality analysis, early testing post-commit, and close collaboration within the team for effective testing infrastructure.
Using Crowdsourced Testing to Turbocharge your Development Team
Using Crowdsourced Testing to Turbocharge your Development TeamRainforest QA The document discusses the shift from traditional QA methods to crowdsourced testing to enhance development processes, emphasizing the need for ‘dev-owned QA’ to increase efficiency by catching bugs early. It outlines how crowdsourced testing works, utilizing an on-demand pool of testers and machine learning to verify results, ultimately integrating smoothly with existing development workflows. Benefits include reduced testing time, improved agility, and significant cost savings for companies using platforms like Rainforest.
UPC Plone Testing Talk
UPC Plone Testing TalkTimo Stollenwerk The document discusses the benefits of automated testing over manual testing for software development. It notes that manual testing is boring, inefficient, and error-prone, while automated testing makes development more effective and fun by finding errors early, allowing code to be refactored with confidence, and proving that code meets specifications. The document then provides examples of different types of automated tests, such as unit tests, integration tests, and acceptance tests, that can improve the development process.
Unit testing
Unit testingBrian Hu 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.
icebreakerwithdevops-150218112943-conversion-gate02
icebreakerwithdevops-150218112943-conversion-gate02Manohar Kumar This document provides an introduction to DevOps concepts for beginners. It recommends starting with source code version control using GitHub (Step 1). It emphasizes the need for change, learning new skills, and having an open mind (Step 2). Automating tasks is key to reduce human effort (Step 3). Fundamental concepts include version control, continuous integration, configuration management, monitoring and release management (Step 4). The document assigns building a basic CI/CD pipeline using GitHub, Travis CI, Ansible and Nexus as a learning project. It encourages learners to document their understanding and identify areas for improvement and further automation.
Why You Should Start Using Docker
Why You Should Start Using DockerAlexandru Bolboaca This document discusses why developers should use Docker containers. It notes that Docker can help solve problems with reproducibility across environments by packaging applications and dependencies into self-contained units. An example is provided of a Dockerfile for a Java Spark application that defines what is needed to build and run the application in a container. The document encourages asking questions and experimenting with Docker to take advantage of its benefits like ease of use, large community support, and speed.
Project management frameworks for software developing
Project management frameworks for software developingVicente Bolea This document discusses various project management frameworks that can help organize projects and deliver features on time. It outlines some common problems like failing to meet deadlines and difficulties estimating timelines. It then describes frameworks like the Waterfall model, Lean software development, Extreme Programming (XP), Scrum, Kanban, and DevOps. It notes limitations of the traditional Waterfall approach and proposes iterative models like cyclical Waterfall/Lean and XP to allow for refinement over multiple sprints. Scrum and Kanban are presented as lightweight frameworks suitable for smaller projects, emphasizing concepts like continuous integration, automation, and incremental improvements.
Develop 4 Developers
Develop 4 DevelopersChristian Güdemann The document discusses the development of the POI4XPages plugin, which allows exporting and importing data between XPages applications and Excel/Word documents. It began from a developer's request to more easily handle recurring tasks of exporting data to office formats. The creator designed the plugin to make these tasks simpler through an extensible plugin model. The document provides advice on open sourcing projects, leveraging existing code, understanding audiences, and making money through reducing complexity and production costs for customers.
QA Automation testing online training
QA Automation testing online trainingDivya Shree United Global Soft offers corporate training programs in automation testing, focusing on QTP and its related tools and techniques. Training sessions are conducted by industry experts and include practical exercises, project explanations, and personal attention for each trainee. Additional support such as resume preparation and interview tips is also provided to enhance career prospects in the IT industry.
testmon for Python
testmon for Pythontib0r The document outlines Tibor Arpáš's initiative to improve testing efficiency in Python development by addressing long wait times associated with running test suites. It introduces a prototype tool called Testmon that focuses on incremental test running and optimizing the test process, which will be open-sourced and supported by an Indiegogo campaign. The overarching goal is to enhance developer tools and promote open-source software crowdfunding.
Agile Software Development Techniques for Daily Use
Agile Software Development Techniques for Daily UseHristo Iliev This document discusses techniques for agile software development using test-driven development (TDD). It provides examples of writing tests first before developing code and refactoring legacy code without tests by adding new features using TDD. The benefits of TDD include fast test execution, controlled development process, and no regressions. Developing code using TDD for a set data structure is presented as an example. The document also provides contacts for further information.
OpenNTF Essentials
OpenNTF EssentialsChristian Güdemann The document discusses OpenNTF Essentials, a collection of open source projects that provide tools and extensions to improve developer productivity when working with IBM Domino and XPages. It highlights some of the projects included in OpenNTF Essentials like the OpenNTF Domino API, Workflow 4 XPages, Bootstrap 4 XPages, and more. It also discusses tools in the OpenNTF Essentials toolbox for debugging, testing, and educating developers. The goal is to grow OpenNTF Essentials into a rock solid, industry-accepted solution for developing on the Domino platform.
Introduction to DevOps. Continuous Integration by Myroslav Dmytrus
Introduction to DevOps. Continuous Integration by Myroslav Dmytrus Binary Studio Continuous integration is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Every change is built and tested on an integration machine. The goal is to detect problems early to minimize integration issues. Continuous integration uses automated builds that are triggered on every code commit to provide rapid feedback. It helps teams integrate code and build quality in from the start.
Putting the pro in programmer
Putting the pro in programmerSwitch Systems Ltd This document provides tips for improving development processes and becoming a pro programmer. It recommends using version control like Git and hosting code online or yourself. It also suggests using Vagrant to create consistent development environments across platforms. Other tips include using bug trackers integrated with version control, enforcing adding ticket IDs to commits, writing tests for bug fixes, setting up continuous integration with Jenkins, and monitoring systems for alerts. The overall message is that these practices can help programmers write better code and work more efficiently.
Игорь Бондаренко (Neklo) - Организация процесса разработки модулей для Magento
Игорь Бондаренко (Neklo) - Организация процесса разработки модулей для Magentomeet_magento Igor Bondarenko discusses best practices for organizing the development process of Magento modules. He recommends choosing ideas based on business analysis, using specialized development tools, and forming teams of narrowly skilled professionals. Bondarenko also stresses the importance of testing, including testing compatibility with other extensions and automation using tools like Selenium IDE. The key to success is performing thorough business analysis, using high-quality tools, skilled teams, and comprehensive testing.
That worked before
That worked beforeChristian Güdemann This document discusses the benefits of JUnit testing and test-driven development (TDD) for XPages applications. It encourages testing from both a user and developer perspective to ensure functionality and catch errors. The TDD mantra of writing a test first, making it fail, then fixing the code to pass the test is explained. An example of a test for currency conversion is provided. OpenNTF's JUnit plugin for XPages is recommended to allow testing. Benefits of TDD like catching errors quickly, understanding requirements, and relaxing because code is tested are outlined. The talk concludes by recommending a book on TDD by example.
The art of being an agile programmer
The art of being an agile programmerClaudia Rosu The document discusses the principles and practices of agile programming, emphasizing the importance of feedback throughout the software development process. It highlights techniques such as early testing, automation, and refactoring, along with the necessity of acceptance and unit tests for validating code. The author encourages consistent communication and collaboration to foster a productive development environment.
SeleniumCamp 2015 Andrii Soldatenko
SeleniumCamp 2015 Andrii SoldatenkoAndrii Soldatenko This document discusses high performance functional testing based on Selenium. It begins with an introduction of the speaker and outlines a testing pyramid with unit, integration and functional/UI tests. It then demonstrates how to automate functional tests for web applications using Selenium and discusses techniques for decreasing test execution time, including using Selenium Grid, PhantomJS, HTTP requests instead of Selenium, and parallel test execution. The document emphasizes that faster tests allow for faster development and provides approaches and tools to reduce test bottlenecks and optimize test execution time.
Improve the deployment process step by step
Improve the deployment process step by stepDaniel Fahlke 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.
Survival of the Continuist
Survival of the ContinuistPaul Blundell The document outlines practices and tools used at Novoda for continuous integration (CI), including features like unit and acceptance testing, automated releases, and team communication. It emphasizes the importance of code quality, effective team collaboration, and management of CI resources through practical strategies and plugins. Additionally, it addresses common challenges and best practices for maintaining a smooth CI process.
User story workflow (eng)
User story workflow (eng)Anatoliy Okhotnikov This document outlines Softjourn Inc.'s user story workflow process. It discusses the differences between releases and versions, and the stages a user story goes through: start, progress, and end. Releases group together versions, which contain user stories. User stories go through analysis, development, and testing stages. Test cases are created and stored in the company's Redmine wiki to validate user stories.
Андрей Солдатенко. Разработка высокопроизводительныx функциональных тестов д...
Андрей Солдатенко. Разработка высокопроизводительныx функциональных тестов д...Alina Dolgikh The document discusses high-performance functional testing, emphasizing the importance of test automation in software development. It covers strategies for decreasing test execution time, including the use of tools like Selenium Grid and parallel execution. Key recommendations include avoiding redundant tests, collaborating on step definitions in BDD, and utilizing continuous integration to boost productivity.
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and Delivery
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett The document discusses continuous integration (CI) and continuous delivery (CD), emphasizing the importance of automated builds, testing, and maintaining a single source repository for software development. It highlights essential practices outlined by Martin Fowler, such as committing to a mainline daily and ensuring broken builds are fixed immediately. Tools for CI and CD are mentioned, including TeamCity, Jenkins, and Octopus Deploy, while stressing a change in mindset towards deployment readiness.
Selenium done right
Selenium done rightTal Landa 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
Agile Testing Pasadena JUG Aug2009
Agile Testing Pasadena JUG Aug2009Grig Gheorghiu Automated and agile testing techniques and tools can help teams get software to a "DONE" state. Key aspects include:
- Writing automated unit, integration, and other tests to validate functionality and catch bugs early. This includes techniques like test-driven development.
- Leveraging continuous integration to run tests automatically on each code change to prevent regressions and catch issues quickly.
- Maintaining a balance of test types from unit to acceptance level while focusing on automation to make testing efficient and free up humans for more investigative tasks.
Test and Behaviour Driven Development (TDD/BDD)
Test and Behaviour Driven Development (TDD/BDD)Lars Thorup The document outlines the principles and workflows of Test-Driven Development (TDD) and Behavior-Driven Development (BDD), emphasizing their benefits in improving software design and bug detection. It discusses various types of automated tests, strategies for writing and maintaining tests, and the importance of integrating testing in the development process. Additionally, it addresses practical examples, including real-world applications and considerations for legacy code management.
More Related Content
What's hot (20)
icebreakerwithdevops-150218112943-conversion-gate02
icebreakerwithdevops-150218112943-conversion-gate02Manohar Kumar This document provides an introduction to DevOps concepts for beginners. It recommends starting with source code version control using GitHub (Step 1). It emphasizes the need for change, learning new skills, and having an open mind (Step 2). Automating tasks is key to reduce human effort (Step 3). Fundamental concepts include version control, continuous integration, configuration management, monitoring and release management (Step 4). The document assigns building a basic CI/CD pipeline using GitHub, Travis CI, Ansible and Nexus as a learning project. It encourages learners to document their understanding and identify areas for improvement and further automation.
Why You Should Start Using Docker
Why You Should Start Using DockerAlexandru Bolboaca This document discusses why developers should use Docker containers. It notes that Docker can help solve problems with reproducibility across environments by packaging applications and dependencies into self-contained units. An example is provided of a Dockerfile for a Java Spark application that defines what is needed to build and run the application in a container. The document encourages asking questions and experimenting with Docker to take advantage of its benefits like ease of use, large community support, and speed.
Project management frameworks for software developing
Project management frameworks for software developingVicente Bolea This document discusses various project management frameworks that can help organize projects and deliver features on time. It outlines some common problems like failing to meet deadlines and difficulties estimating timelines. It then describes frameworks like the Waterfall model, Lean software development, Extreme Programming (XP), Scrum, Kanban, and DevOps. It notes limitations of the traditional Waterfall approach and proposes iterative models like cyclical Waterfall/Lean and XP to allow for refinement over multiple sprints. Scrum and Kanban are presented as lightweight frameworks suitable for smaller projects, emphasizing concepts like continuous integration, automation, and incremental improvements.
Develop 4 Developers
Develop 4 DevelopersChristian Güdemann The document discusses the development of the POI4XPages plugin, which allows exporting and importing data between XPages applications and Excel/Word documents. It began from a developer's request to more easily handle recurring tasks of exporting data to office formats. The creator designed the plugin to make these tasks simpler through an extensible plugin model. The document provides advice on open sourcing projects, leveraging existing code, understanding audiences, and making money through reducing complexity and production costs for customers.
QA Automation testing online training
QA Automation testing online trainingDivya Shree United Global Soft offers corporate training programs in automation testing, focusing on QTP and its related tools and techniques. Training sessions are conducted by industry experts and include practical exercises, project explanations, and personal attention for each trainee. Additional support such as resume preparation and interview tips is also provided to enhance career prospects in the IT industry.
testmon for Python
testmon for Pythontib0r The document outlines Tibor Arpáš's initiative to improve testing efficiency in Python development by addressing long wait times associated with running test suites. It introduces a prototype tool called Testmon that focuses on incremental test running and optimizing the test process, which will be open-sourced and supported by an Indiegogo campaign. The overarching goal is to enhance developer tools and promote open-source software crowdfunding.
Agile Software Development Techniques for Daily Use
Agile Software Development Techniques for Daily UseHristo Iliev This document discusses techniques for agile software development using test-driven development (TDD). It provides examples of writing tests first before developing code and refactoring legacy code without tests by adding new features using TDD. The benefits of TDD include fast test execution, controlled development process, and no regressions. Developing code using TDD for a set data structure is presented as an example. The document also provides contacts for further information.
OpenNTF Essentials
OpenNTF EssentialsChristian Güdemann The document discusses OpenNTF Essentials, a collection of open source projects that provide tools and extensions to improve developer productivity when working with IBM Domino and XPages. It highlights some of the projects included in OpenNTF Essentials like the OpenNTF Domino API, Workflow 4 XPages, Bootstrap 4 XPages, and more. It also discusses tools in the OpenNTF Essentials toolbox for debugging, testing, and educating developers. The goal is to grow OpenNTF Essentials into a rock solid, industry-accepted solution for developing on the Domino platform.
Introduction to DevOps. Continuous Integration by Myroslav Dmytrus
Introduction to DevOps. Continuous Integration by Myroslav Dmytrus Binary Studio Continuous integration is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Every change is built and tested on an integration machine. The goal is to detect problems early to minimize integration issues. Continuous integration uses automated builds that are triggered on every code commit to provide rapid feedback. It helps teams integrate code and build quality in from the start.
Putting the pro in programmer
Putting the pro in programmerSwitch Systems Ltd This document provides tips for improving development processes and becoming a pro programmer. It recommends using version control like Git and hosting code online or yourself. It also suggests using Vagrant to create consistent development environments across platforms. Other tips include using bug trackers integrated with version control, enforcing adding ticket IDs to commits, writing tests for bug fixes, setting up continuous integration with Jenkins, and monitoring systems for alerts. The overall message is that these practices can help programmers write better code and work more efficiently.
Игорь Бондаренко (Neklo) - Организация процесса разработки модулей для Magento
Игорь Бондаренко (Neklo) - Организация процесса разработки модулей для Magentomeet_magento Igor Bondarenko discusses best practices for organizing the development process of Magento modules. He recommends choosing ideas based on business analysis, using specialized development tools, and forming teams of narrowly skilled professionals. Bondarenko also stresses the importance of testing, including testing compatibility with other extensions and automation using tools like Selenium IDE. The key to success is performing thorough business analysis, using high-quality tools, skilled teams, and comprehensive testing.
That worked before
That worked beforeChristian Güdemann This document discusses the benefits of JUnit testing and test-driven development (TDD) for XPages applications. It encourages testing from both a user and developer perspective to ensure functionality and catch errors. The TDD mantra of writing a test first, making it fail, then fixing the code to pass the test is explained. An example of a test for currency conversion is provided. OpenNTF's JUnit plugin for XPages is recommended to allow testing. Benefits of TDD like catching errors quickly, understanding requirements, and relaxing because code is tested are outlined. The talk concludes by recommending a book on TDD by example.
The art of being an agile programmer
The art of being an agile programmerClaudia Rosu The document discusses the principles and practices of agile programming, emphasizing the importance of feedback throughout the software development process. It highlights techniques such as early testing, automation, and refactoring, along with the necessity of acceptance and unit tests for validating code. The author encourages consistent communication and collaboration to foster a productive development environment.
SeleniumCamp 2015 Andrii Soldatenko
SeleniumCamp 2015 Andrii SoldatenkoAndrii Soldatenko This document discusses high performance functional testing based on Selenium. It begins with an introduction of the speaker and outlines a testing pyramid with unit, integration and functional/UI tests. It then demonstrates how to automate functional tests for web applications using Selenium and discusses techniques for decreasing test execution time, including using Selenium Grid, PhantomJS, HTTP requests instead of Selenium, and parallel test execution. The document emphasizes that faster tests allow for faster development and provides approaches and tools to reduce test bottlenecks and optimize test execution time.
Improve the deployment process step by step
Improve the deployment process step by stepDaniel Fahlke 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.
Survival of the Continuist
Survival of the ContinuistPaul Blundell The document outlines practices and tools used at Novoda for continuous integration (CI), including features like unit and acceptance testing, automated releases, and team communication. It emphasizes the importance of code quality, effective team collaboration, and management of CI resources through practical strategies and plugins. Additionally, it addresses common challenges and best practices for maintaining a smooth CI process.
User story workflow (eng)
User story workflow (eng)Anatoliy Okhotnikov This document outlines Softjourn Inc.'s user story workflow process. It discusses the differences between releases and versions, and the stages a user story goes through: start, progress, and end. Releases group together versions, which contain user stories. User stories go through analysis, development, and testing stages. Test cases are created and stored in the company's Redmine wiki to validate user stories.
Андрей Солдатенко. Разработка высокопроизводительныx функциональных тестов д...
Андрей Солдатенко. Разработка высокопроизводительныx функциональных тестов д...Alina Dolgikh The document discusses high-performance functional testing, emphasizing the importance of test automation in software development. It covers strategies for decreasing test execution time, including the use of tools like Selenium Grid and parallel execution. Key recommendations include avoiding redundant tests, collaborating on step definitions in BDD, and utilizing continuous integration to boost productivity.
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and Delivery
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett The document discusses continuous integration (CI) and continuous delivery (CD), emphasizing the importance of automated builds, testing, and maintaining a single source repository for software development. It highlights essential practices outlined by Martin Fowler, such as committing to a mainline daily and ensuring broken builds are fixed immediately. Tools for CI and CD are mentioned, including TeamCity, Jenkins, and Octopus Deploy, while stressing a change in mindset towards deployment readiness.
Selenium done right
Selenium done rightTal Landa 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
Similar to Introduction to Automated Testing (20)
Agile Testing Pasadena JUG Aug2009
Agile Testing Pasadena JUG Aug2009Grig Gheorghiu Automated and agile testing techniques and tools can help teams get software to a "DONE" state. Key aspects include:
- Writing automated unit, integration, and other tests to validate functionality and catch bugs early. This includes techniques like test-driven development.
- Leveraging continuous integration to run tests automatically on each code change to prevent regressions and catch issues quickly.
- Maintaining a balance of test types from unit to acceptance level while focusing on automation to make testing efficient and free up humans for more investigative tasks.
Test and Behaviour Driven Development (TDD/BDD)
Test and Behaviour Driven Development (TDD/BDD)Lars Thorup The document outlines the principles and workflows of Test-Driven Development (TDD) and Behavior-Driven Development (BDD), emphasizing their benefits in improving software design and bug detection. It discusses various types of automated tests, strategies for writing and maintaining tests, and the importance of integrating testing in the development process. Additionally, it addresses practical examples, including real-world applications and considerations for legacy code management.
Automated testing overview
Automated testing overviewAlex Pop Automated testing overview discusses the importance of software testing and automated testing. It defines software testing as verifying that software meets requirements and works as expected. The document covers different types of testing and why automated testing is needed to reduce costs, protect reputation, and address difficulties in testing. It provides examples of unit testing simple objects, objects with dependencies, and user interfaces to illustrate how to implement automated tests.
Agile Acceptance testing with Fitnesse
Agile Acceptance testing with FitnesseClareMcLennan The document discusses the implementation of Agile acceptance testing and FitNesse to improve software quality and testability. It details the challenges faced in achieving a 99.99% uptime and the evolution of testing processes over 12 months, highlighting the roles of testers and developers in creating a collaborative testing environment. Key outcomes include reduced testing time, positive shifts in programmer attitudes towards testing, and the establishment of a self-improving QA process.
Automated testing vs manual testing
Automated testing vs manual testingNeha Polke 1. Automated testing requires less effort and cost than manual testing due to its reusability and ability to run tests quickly through automation.
2. Manual testing is more boring and prone to human error than automated testing, which can catch regressions through continuous integration and provide global visibility of test results.
3. Automated tests drive better design, provide a safety net for refactoring, act as documentation, and reduce code clutter compared to manual tests.
Making the Unstable Stable - An Intro To Testing
Making the Unstable Stable - An Intro To TestingCameron Presley The document discusses the importance of testing in software development, highlighting personal experiences from three companies with different testing approaches and their resulting outcomes. It emphasizes the need for automated testing, outlines various testing types, and provides insights into unit and integration testing strategies. Additionally, it offers practical next steps for implementing testing practices and resources for further learning.
High Performance Software Engineering Teams
High Performance Software Engineering TeamsLars Thorup The document details best practices for creating high-performance engineering teams in software development, emphasizing the importance of automation, continuous integration, and collaboration between engineering and QA. Key strategies include reducing non-productive activities, enhancing testing frequency and quality, and prioritizing bug fixes. It also highlights the significance of using frameworks for automated unit and acceptance testing, as well as encouraging a culture of continuous improvement and transparency.
Testing 101
Testing 101Noam Barkai This document provides an introduction to automated testing. It discusses the motivations for automated testing such as improving quality and catching bugs early. It covers basic testing concepts like unit, integration, and system tests. It explains testing principles such as keeping tests independent and focusing on visible behavior. The document also discusses popular testing frameworks for different programming languages and provides examples of tests from a codebase.
Unit Testing and TDD 2017
Unit Testing and TDD 2017Xavi Hidalgo This document discusses the principles and benefits of Test-Driven Development (TDD) and unit testing, emphasizing the importance of writing automated tests to identify code errors early, improve code extensibility, and adapt to changing business requirements. It details the history and evolution of TDD, as well as common misconceptions and best practices for writing effective unit tests, highlighting how TDD enhances code quality and facilitates better software design. Additionally, it provides guidance on applying TDD in various coding situations, including legacy code management.
Engaging IV&V Testing Services for Agile Projects
Engaging IV&V Testing Services for Agile ProjectsRavi Kumar This document discusses agile testing and the role of testers in agile development. It covers topics like the value testers provide, Brian Marick's test categories, challenges with agile testing and strategies to address them, and the role of automation and continuous integration. Key points emphasized are that testers are not obsolete in agile and need to adapt to new ways of testing, defining acceptance criteria, collaborating with developers, automating tests, and providing frequent feedback to the team.
Continuous Integration testing based on Selenium and Hudson
Continuous Integration testing based on Selenium and HudsonZbyszek Mockun This article discusses the use of open-source tools for automating tests in continuous integration environments, emphasizing the need for efficient regression testing within agile methodologies. It outlines the benefits of integrating automated tests with tools like Hudson and Selenium, as well as strategies for optimizing testing processes to minimize time spent while maximizing functionality. The author shares insights from personal experience in QA and highlights the advantages of utilizing open-source solutions.
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...suwalki24.pl The document discusses the integration of automated testing into continuous integration (CI) environments using open-source tools like Hudson and Selenium. It highlights strategies to maintain high-quality releases while minimizing the regression testing time within agile methodologies. The article also emphasizes the necessity of running automated tests frequently after code commits to detect errors early and ensure efficient testing processes.
DSR Testing (Part 1)
DSR Testing (Part 1)Steve Upton This document provides an overview of software testing concepts. It discusses different types of testing like unit testing, functional testing, error path testing, boundary value testing, and equivalence partitioning. It also covers test strategies like golden path testing, black box testing, and white box testing. The purpose of a tester is explained as quantifying risk to make decisions that improve confidence and quality.
Automated testing-whitepaper
Automated testing-whitepaperimdurgesh The document discusses the transition from manual to automated testing in software development, highlighting the benefits of increased efficiency, reduced costs, and improved product quality. It covers various testing methodologies, including unit, integration, and end-to-end testing, while also addressing challenges and strategies for implementing automated testing effectively. An extended example of consumer-driven contract testing demonstrates how automated testing can be leveraged in microservices architecture.
TeDevelopment Testing in Software Engineering
TeDevelopment Testing in Software EngineeringKarthik Rohan Software Engineering Testing and its types
Testing Sap: Modern Methodology
Testing Sap: Modern MethodologyEthan Jewett The document discusses modern testing methodologies in software development, emphasizing the importance of quality assurance and automation through practices like Test Driven Development (TDD) and Behavior Driven Development (BDD). It explores the challenges of traditional software testing and proposes agile, open, and decentralized approaches to improve testing efficiency and effectiveness. Tools, techniques, and practices for integrating testing within the development process are highlighted to enable faster and higher-value project outcomes.
Testing In Agile
Testing In AgileAri Tanninen The document discusses testing in Agile development, focusing on various testing types, levels, and their purposes. It emphasizes the importance of automated testing, test-first approaches, and the evolving role of testers in Agile environments. Key aspects include collaboration, adapting to changing specifications, and ensuring 'potentially shippable' functionality at the end of each iteration.
Software testing
Software testingNico Heidtke The document discusses the importance of software testing, emphasizing that all software developers make mistakes and therefore require robust testing strategies. It outlines various types of tests, methodologies, and the significance of prioritizing tests based on project needs, highlighting the benefits of tests in documentation, project management, and reducing development time. Additionally, it explores the challenges and pitfalls of testing, advocating for effective test-driven development and behavioral tests to ensure product quality.
39.Testing-Part3.ppt
39.Testing-Part3.pptSapnaRastogi3 The document discusses various strategies for testing software documentation and systems. It describes writing formal test cases and test plans, with information to include in test cases like identification, instructions, expected results, and cleanup steps. It also summarizes strategies for testing large systems, including incremental and integration testing approaches. The roles of developers, independent testers, and end-users in testing are outlined.
Unit testing & TDD concepts with best practice guidelines.
Unit testing & TDD concepts with best practice guidelines.Mohamed Taman The document provides a comprehensive overview of unit testing and test-driven development (TDD), discussing various types of testing, techniques, and methodologies. It emphasizes the importance of unit testing for ensuring functional correctness, early bug detection, and better design, while also outlining best practices and guidelines for effective unit testing. The document highlights the significance of keeping tests small, maintaining independence, utilizing automation, and prioritizing execution coverage to enhance the testing process.
Ad
More from Lars Thorup (14)
100 tests per second - 40 releases per week
100 tests per second - 40 releases per weekLars Thorup Triggerz, a SaaS company founded in 2016, employs a continuous delivery model with 100 tests per second and 20-40 releases per week, enhancing developer feedback and user experience. The deployment strategy includes features like feature toggles and zero-downtime upgrades, allowing for rapid functionality updates and easier problem resolution. Overall, the approach requires significant initial investment in testing and automation but leads to more efficient and effective production management.
SQL or NoSQL - how to choose
SQL or NoSQL - how to chooseLars Thorup The document compares SQL and NoSQL database systems, discussing their history, differences, and use cases. It highlights key examples such as Redis, a NoSQL database known for its speed and versatility, and outlines the characteristics of typical SQL and NoSQL databases. The author emphasizes the importance of matching database systems to specific application needs and provides demos of various Redis functionalities.
Super fast end-to-end-tests
Super fast end-to-end-testsLars Thorup The document discusses the challenges of end-to-end testing, highlighting their slowness, lack of precision, complexity, and fragility compared to unit tests. It emphasizes that while unit tests are efficient and reliable, they can be misleading due to mocked dependencies. The author proposes a solution that integrates both testing methods to achieve faster, more accurate, and robust testing outcomes, demonstrated through a sample implementation using Node.js.
Advanced Javascript Unit Testing
Advanced Javascript Unit TestingLars Thorup This document summarizes best practices for JavaScript unit testing presented by Lars Thorup. It discusses how to test asynchronous code using callbacks and promises, fake timers to test delayed behavior, mock the DOM and AJAX requests, enable cross-browser testing using Karma, and detect memory leaks between tests. Lars Thorup is a software developer who focuses on JavaScript, TDD, and continuous integration.
Unit testing legacy code
Unit testing legacy codeLars Thorup Lars Thorup's document discusses strategies for managing and refactoring legacy code by implementing unit tests to regain control over the codebase. It emphasizes the importance of characterization tests, gradual refactoring, and developing sustainable practices to improve code quality while minimizing risks. The document details a step-by-step approach to transitioning from legacy systems to modern implementations through careful testing and incremental changes.
Advanced QUnit - Front-End JavaScript Unit Testing
Advanced QUnit - Front-End JavaScript Unit TestingLars Thorup The document provides an advanced overview of using QUnit for front-end JavaScript unit testing, focusing on techniques such as mocking, spying, and stubbing methods to enhance test reliability and speed. It discusses how to conduct isolation testing, avoid waiting for asynchronous processes, and efficiently handle global functions and AJAX requests within tests. Additionally, it touches upon memory leak detection and the importance of cleanup after tests to ensure accurate and performant unit tests.
Database Schema Evolution
Database Schema EvolutionLars Thorup The document discusses strategies for managing database schema evolution, focusing on version control, migration automation, and development practices. It emphasizes the importance of keeping the database and application in sync, avoiding shared development databases, and utilizing tools like Flyway and Liquibase for migration management. Additionally, it outlines solutions for common issues such as failed tests, upgrade conflicts, and the need for reliable test environments.
Advanced Jasmine - Front-End JavaScript Unit Testing
Advanced Jasmine - Front-End JavaScript Unit TestingLars Thorup This document discusses advanced techniques for front-end JavaScript unit testing using Jasmine, including mocking methods, constructors, timers, and AJX requests to test code in isolation without dependencies and speed up tests. It also covers spying on events, simulating CSS transitions, using custom matchers, structuring test code, and browser-specific testing. The presenter is Lars Thorup, a software developer and coach who founded ZeaLake and teaches agile and automated testing.
Javascript unit testing with QUnit and Sinon
Javascript unit testing with QUnit and SinonLars Thorup This document discusses JavaScript unit testing with QUnit and Sinon. It introduces Lars Thorup and his background in software development, testing, and coaching. It then provides an overview of unit testing, explaining why it is beneficial and how to implement it. Finally, it demonstrates various QUnit and Sinon techniques for writing tests, including assertions, spies, stubs, mocks, asynchronous code, the DOM, and advanced mocking.
Continuous Integration for front-end JavaScript
Continuous Integration for front-end JavaScriptLars Thorup The document discusses continuous integration for front-end JavaScript, highlighting tools such as Grunt, JSHint, and Jasmine for testing and analysis. It includes example code for functions, testing strategies, and how to set up configurations in a Grunt file. Additionally, it covers code coverage metrics and integrates with Jenkins for reporting.
Agile Contracts
Agile ContractsLars Thorup The document discusses Lars Thorup's expertise in agile software consulting and outlines a contract model that combines traditional payment structures with agile practices. It highlights three case studies showcasing the agile development process, emphasizing collaboration, flexible requirements, and incremental delivery to enhance project efficiency. The advantages of this model include cost savings, faster ROI, and shared risks and gains between clients and vendors, contingent on their respective maturity levels.
Elephant Carpaccio
Elephant CarpaccioLars Thorup Here are some tips for breaking down work in an agile way:
- Focus on delivering value to users. Each story and task should provide some value.
- Iterate frequently. Stories and tasks should be small enough that you can complete and release them within a sprint or two.
- Get early feedback. Small slices allow testing work sooner and adjusting based on feedback.
- Prioritize flexibility. Small slices give you options to reorder or drop work as priorities change.
- Estimate costs accurately. Tasks should take 1-5 days; if longer, may need refactoring. Consider spikes for technical challenges.
- Refactor when repetitive. If work is very similar, look for ways to simplify through ref
Automated Testing for Embedded Software in C or C++
Automated Testing for Embedded Software in C or C++Lars Thorup This document discusses automated testing for embedded C software. It introduces Lars Thorup and provides an agenda for the document. It then defines automated testing, describes the Unity testing framework for embedded C, and provides an example of how to handle dependencies in testing. It advocates for continuous integration, breaking dependencies through abstraction and injection, and explains how automated testing can improve software quality through faster development and preventing bugs.
Unit Testing in JavaScript with MVC and QUnit
Unit Testing in JavaScript with MVC and QUnitLars Thorup Lars Thorup presents on unit testing JavaScript applications with the MVC pattern and QUnit testing framework. He discusses testing views, controllers, models, and services. The document recommends setting up tests for each component in isolation by injecting stubs for their dependencies. Asynchronous testing is also covered, including techniques like stopping/starting to synchronize async calls in tests. The MVC pattern with dependency injection is advocated to make the code more modular and testable.
Ad
Recently uploaded (20)
OpenPOWER Foundation & Open-Source Core Innovations
OpenPOWER Foundation & Open-Source Core InnovationsIBM penPOWER offers a fully open, royalty-free CPU architecture for custom chip design.
It enables both lightweight FPGA cores (like Microwatt) and high-performance processors (like POWER10).
Developers have full access to source code, specs, and tools for end-to-end chip creation.
It supports AI, HPC, cloud, and embedded workloads with proven performance.
Backed by a global community, it fosters innovation, education, and collaboration.
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
Cracking the Code - Unveiling Synergies Between Open Source Security and AI.pdf
Cracking the Code - Unveiling Synergies Between Open Source Security and AI.pdfPriyanka Aash Cracking the Code - Unveiling Synergies Between Open Source Security and AI
AI Agents and FME: A How-to Guide on Generating Synthetic Metadata
AI Agents and FME: A How-to Guide on Generating Synthetic MetadataSafe Software In the world of AI agents, semantics is king. Good metadata is thus essential in an organization's AI readiness checklist. But how do we keep up with the massive influx of new data? In this talk we go over the tips and tricks in generating synthetic metadata for the consumption of human users and AI agents alike.
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante We live in an ever evolving landscape for cyber threats creating security risk for your production systems. Mitigating these risks requires participation throughout all stages from development through production delivery - and by every role including architects, developers QA and DevOps engineers, product owners and leadership. No one is excused! This session will cover examples of common mistakes or missed opportunities that can lead to vulnerabilities in production - and ways to do better throughout the development lifecycle.
Enhance GitHub Copilot using MCP - Enterprise version.pdf
Enhance GitHub Copilot using MCP - Enterprise version.pdfNilesh Gule Slide deck related to the GitHub Copilot Bootcamp in Melbourne on 17 June 2025
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance Securing Account Lifecycles in the Age of Deepfakes
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdf
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdfPriyanka Aash GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now
"How to survive Black Friday: preparing e-commerce for a peak season", Yurii ...
"How to survive Black Friday: preparing e-commerce for a peak season", Yurii ...Fwdays We will explore how e-commerce projects prepare for the busiest time of the year, which key aspects to focus on, and what to expect. We’ll share our experience in setting up auto-scaling, load balancing, and discuss the loads that Silpo handles, as well as the solutions that help us navigate this season without failures.
OpenACC and Open Hackathons Monthly Highlights June 2025
OpenACC and Open Hackathons Monthly Highlights June 2025OpenACC The OpenACC organization focuses on enhancing parallel computing skills and advancing interoperability in scientific applications through hackathons and training. The upcoming 2025 Open Accelerated Computing Summit (OACS) aims to explore the convergence of AI and HPC in scientific computing and foster knowledge sharing. This year's OACS welcomes talk submissions from a variety of topics, from Using Standard Language Parallelism to Computer Vision Applications. The document also highlights several open hackathons, a call to apply for NVIDIA Academic Grant Program and resources for optimizing scientific applications using OpenACC directives.
UserCon Belgium: Honey, VMware increased my bill
UserCon Belgium: Honey, VMware increased my billstijn40 VMware’s pricing changes have forced organizations to rethink their datacenter cost management strategies. While FinOps is commonly associated with cloud environments, the FinOps Foundation has recently expanded its framework to include Scopes—and Datacenter is now officially part of the equation. In this session, we’ll map the FinOps Framework to a VMware-based datacenter, focusing on cost visibility, optimization, and automation. You’ll learn how to track costs more effectively, rightsize workloads, optimize licensing, and drive efficiency—all without migrating to the cloud. We’ll also explore how to align IT teams, finance, and leadership around cost-aware decision-making for on-prem environments. If your VMware bill keeps increasing and you need a new approach to cost management, this session is for you!
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...Josef Weingand IBM LTO10
Raman Bhaumik - Passionate Tech Enthusiast
Raman Bhaumik - Passionate Tech EnthusiastRaman Bhaumik A Junior Software Developer with a flair for innovation, Raman Bhaumik excels in delivering scalable web solutions. With three years of experience and a solid foundation in Java, Python, JavaScript, and SQL, she has streamlined task tracking by 20% and improved application stability.
Lessons Learned from Developing Secure AI Workflows.pdf
Lessons Learned from Developing Secure AI Workflows.pdfPriyanka Aash Lessons Learned from Developing Secure AI Workflows
Smarter Aviation Data Management: Lessons from Swedavia Airports and Sweco
Smarter Aviation Data Management: Lessons from Swedavia Airports and SwecoSafe Software Managing airport and airspace data is no small task, especially when you’re expected to deliver it in AIXM format without spending a fortune on specialized tools. But what if there was a smarter, more affordable way?
Join us for a behind-the-scenes look at how Sweco partnered with Swedavia, the Swedish airport operator, to solve this challenge using FME and Esri.
Learn how they built automated workflows to manage periodic updates, merge airspace data, and support data extracts – all while meeting strict government reporting requirements to the Civil Aviation Administration of Sweden.
Even better? Swedavia built custom services and applications that use the FME Flow REST API to trigger jobs and retrieve results – streamlining tasks like securing the quality of new surveyor data, creating permdelta and baseline representations in the AIS schema, and generating AIXM extracts from their AIS data.
To conclude, FME expert Dean Hintz will walk through a GeoBorders reading workflow and highlight recent enhancements to FME’s AIXM (Aeronautical Information Exchange Model) processing and interpretation capabilities.
Discover how airports like Swedavia are harnessing the power of FME to simplify aviation data management, and how you can too.
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...Fwdays Let's talk about our history. How we started the project with a small vector database of less than 2 million records. Later, we received a request for +100 million records, then another +100... And so gradually we reached almost 1 billion. Standard tools were quickly running out of steam - we were running into performance, index size, and very limited resources. After a long series of trials and errors, we built our own low-cost cluster, which today stably processes thousands of queries to more than 1B vectors.
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
Introduction to Automated Testing
- 1. Introduction to Automated Testing by Lars Thorup, ZeaLake May 26th 2011
- 2. Who is Lars Thorup? • Software developer • Coach: Teaching TDD and automated testing • Advisor: Assesses software projects and companies • Founder and CEO of BestBrains and ZeaLake
- 3. Why are we here today? • How do we do automated testing? – Write test programs – Run the tests automatically • Why should we write tests? – Enjoy more efficient and predictable course of development – Find and fix bugs fast – Prevent bugs from reappearing – Improve the design of our software
- 4. Different kinds of automated tests • Unit tests – Tests individual pieces of code and the interaction between code blocks • System tests – Tests the entire system against the requirements • Performance tests – Tests non functional requirements
- 5. Unit tests or system tests? • Unit tests are efficient – Fast to run (a few seconds) – Robust and predictable – Easy to write – Is written together with the code it is testing • System tests are thorough – Tests all layers together – Most efficient way to create a set of tests for existing code
- 6. Can we automate performance tests? • Performance tests are brittle – Tip: create performance trend curves instead
- 7. So, how do we actually do this? • IsNumeric – C# – Ruby • TransferFunds – C++
- 8. How do we run the tests automatically? • From our programming environment (IDE) – Command line: make test – Right click | Run Tests • On every commit – Setup a build server • Hudson / Jenkins • TeamCity – Let the build server run all tests – Get build notifications – Keep the build green • Fixing a broken build has priority over any other development task
- 9. How can tests help improve our design? • The software design needs to evolve over time • A refactoring modifies the design without changing behavior • Tests ensure that behavior is not accidentally changed • Without tests, refactoring is scary – and with no refactoring, the design decays over time • With tests, we have the courage to refactor – so we continually keep our design healthy
- 10. What is good design? • One element of good design is loose dependencies – Use interfaces (for static languages) – Inject dependencies • Avoid this • Do this instead
- 11. Are we wasting valuable developer time writing tests? • No • The time spent writing tests is not taken from the time spent coding – It is taken from the time otherwise spent on manual testing and debugging • The cost of a bug keeps increasing until we fix it • Find bugs fast – Avoid losing customer confidence – Free QA to do exploratory testing so they find the hard-to-find bugs – Spend less time trying to figure out what is causing the bug and how to fix it • Avoid spending time testing again
- 12. How do we get started? • When we have a lot of existing code without tests – Create a set of system tests to get a safety net • When we are writing new code – Write unit tests in conjunction with the new code • Set up a standard test environment for our specific application – Test data • Automate the creation of standard testdata in a local database – External dependencies • Write stubs to use in the tests
- 13. What does a real-world project look like? • wizerize.com – Web application: C# and JavaScript – 3 years of production – 2-4 developers • 40% test code, 60% production code (in lines of code) • 71% code coverage of unit tests • 614 unit tests – run in 1 minute • 54 system tests – run in 20 minutes • No functional errors seen by end users in production (yet)
- 14. Where can I read more? • http://googletesting.blogspot.com/ • http://testdrivendeveloper.com/ • http://codesheriff.blogspot.com/
- 15. Which tools do we use? Environment Tool C# NUnit JavaScript qUnit HTML-based UI WatiN, Selenium C++ CppUnit, googletest Python unittest Ruby Test::Unit C check, cunit Java JUnit ... ...