How to write better tests with Test Driven Development
•Download as PPTX, PDF•
0 likes•20 views
The document discusses test-driven development (TDD) and how to use it to write better tests. TDD involves writing tests before production code to validate requirements in small iterations. Tests are written to initially fail, then production code is written to pass each test, ensuring all requirements are implemented. Following TDD principles helps developers think through code systematically and prevents unnecessary complexity.
Report
Share
Report
Share
Recommended
Aistė Stikliutė - Testing in continuous delivery
Continuous delivery makes it possible to develop and deploy software within hours instead of months or weeks or days. But what about testing? Testing is not fast. Which means you will have to cut corners, but add additional measures to compensate. Many companies market their continuous delivery practices, so others can see how cool they are, but also learn from their experiences. In this talk I will go through some highlights and things that work well and not so well in these example continuous delivery implementations, and then will concentrate on testing patterns, approaches and little hints that I have learnt both from these examples and from my own experience.
QA Automation testing online training
United Global Soft
We provide QTP/QA Automation Online training by real time experts.
Contact : +91 8099902123
+1-201-710-8393
Mail Id : info@unitedglobalsoft.com
Approval Tests in Action: A LEGO Exercise and an Experience Report
This document describes an exercise using LEGO pieces to demonstrate approval testing. It had participants build LEGO figures according to criteria in round 1. In round 2, they wrote tests to validate the criteria. In round 3, they validated a copy of their round 1 solution. The document then discusses approval testing and provides examples of how it can detect bugs and new features. It notes benefits like easier to understand tests and testing otherwise untestable code. It also discusses applicability and weaknesses like lack of isolation.
Introduction to Test Driven Development
Test driven development (TDD) involves writing tests before writing code to define requirements and ensure code meets those requirements. The presentation introduces TDD and related concepts like the red-green-refactor cycle, unit tests, integration tests, Gherkin for requirements gathering, and popular tools for TDD in different programming languages.
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.
Agile Testing in Enterprise: Way to transform - SQA Days 2014
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
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.
Recommended
Aistė Stikliutė - Testing in continuous delivery
Continuous delivery makes it possible to develop and deploy software within hours instead of months or weeks or days. But what about testing? Testing is not fast. Which means you will have to cut corners, but add additional measures to compensate. Many companies market their continuous delivery practices, so others can see how cool they are, but also learn from their experiences. In this talk I will go through some highlights and things that work well and not so well in these example continuous delivery implementations, and then will concentrate on testing patterns, approaches and little hints that I have learnt both from these examples and from my own experience.
QA Automation testing online training
United Global Soft
We provide QTP/QA Automation Online training by real time experts.
Contact : +91 8099902123
+1-201-710-8393
Mail Id : info@unitedglobalsoft.com
Approval Tests in Action: A LEGO Exercise and an Experience Report
This document describes an exercise using LEGO pieces to demonstrate approval testing. It had participants build LEGO figures according to criteria in round 1. In round 2, they wrote tests to validate the criteria. In round 3, they validated a copy of their round 1 solution. The document then discusses approval testing and provides examples of how it can detect bugs and new features. It notes benefits like easier to understand tests and testing otherwise untestable code. It also discusses applicability and weaknesses like lack of isolation.
Introduction to Test Driven Development
Test driven development (TDD) involves writing tests before writing code to define requirements and ensure code meets those requirements. The presentation introduces TDD and related concepts like the red-green-refactor cycle, unit tests, integration tests, Gherkin for requirements gathering, and popular tools for TDD in different programming languages.
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.
Agile Testing in Enterprise: Way to transform - SQA Days 2014
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
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.
Level Up Your Salesforce Unit Testing
Presentation for the Austin Salesforce Developers Users Group. Primarily covers the Apex code concerns with using the Apex Stub API.
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
Test Automation Canvas
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
How to get reviewers to block your changes
This document provides tips to decrease productivity by making changes that will cause code reviewers to block the changes. Some tips include adding spelling errors to commit messages, fixing bugs without linking to bug reports, making large changes without proper documentation, including few or no unit tests, and being unresponsive to reviewer comments. The overall goal of the tips is to submit low-quality changes that will frustrate and slow down the review process.
10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing
Shifting left means starting testing earlier in the development cycle by writing tests alongside code development within small teams. This eliminates surprises from late-discovered problems and ensures code meets expectations before being declared "done". To achieve superior test coverage, teams must test more by shifting left and testing as code is committed so developers get immediate feedback and bugs are fixed early. Shifting left embeds quality into every step of development and allows for continuous testing and integration to produce higher quality, shippable features faster.
Alm with tfs 2013
The document provides an overview of how to effectively use ALM with TFS 2013. It discusses how to set up iterations and areas, move work items between iterations, add work item types to the backlog, and create useful queries. It also offers tips on creating release notes, branching code, and things to automate in builds. Key points covered include using tags instead of iterations to track work, branching code to isolate releases or unfinished work, and creating a new workspace per branch.
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)
The document discusses how a company called Odobo improved their testing process by defining a unified testing framework using Groovy, Spock, and Geb. This allowed both developers and QA engineers to write automated tests in the same framework, eliminating duplicated efforts. Key aspects of the framework included using Gradle for building, Groovy as the programming language, Spock as the testing framework, and Geb for browser automation. It provided benefits like increased code reuse and happier testers across both dev and QA teams.
Agile Testing
Agile testing emphasizes:
- Collaborative, integrated teams that test early and often throughout development;
- Frequent deliveries of working software that is tested as part of being "done";
- The ability to adapt testing to changing business needs.
Some key principles of agile testing include shifting the focus of testing from the last phase to being integrated throughout development, having everybody on the team test rather than just designated testers, reducing the latency between implementing code and testing it, and treating bugs as issues to be fixed quickly rather than letting them linger.
Effective agile testing incorporates practices like automated unit and integration tests, test-driven development, automated system-level regression tests, acceptance test
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.
The Art of Giving and Receiving Code Reviews
Code reviews are one of the most effective tools we have, if we use them right. This talk discusses the technical, cultural and psychological factors that make for more productive code reviews and happier coworkers.
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?
Continuous delivery in practice (public)
Continuous delivery practices were implemented for an RTB project at Kenshoo to allow for faster development and delivery. This included having a single code branch, comprehensive testing at the unit, integration, behavioral, and staging levels, keeping builds stable, ensuring the master branch is always deployable, conducting rigorous code reviews, using real-time feedback, managing upgrades carefully, and A/B testing. It is important to constantly monitor builds and collect feedback to own the process.
Spec By Example or How to teach people talk to each other
This document introduces an approach called "Spec By Example" to improve communication between developers, QA analysts, and clients. It involves impact mapping to focus on user stories, QA and analyst pairing to create examples to describe requirements, and diverse and merge sessions for the team to collaboratively build out examples. The examples are then optimized by compressing tables and introducing parameters before being linked to automated tests through a behavior driven development approach. This unified process allows requirements, test cases, and code to have a single source of truth, makes it easy to trace work back to business needs, and improves estimation, demos, and reduces rework and issues.
Automated Acceptance Tests & Tool choice
The document discusses different layers of automated acceptance testing and compares different toolsets for each layer. The three layers are: 1) Acceptance Criteria Layer which defines test scenarios in a business-readable format, 2) Test Implementation Layer which implements tests against the system under test, and 3) Application Driver Layer which executes tests against the application. Popular tools like Cucumber, Concordion and FitNesse are compared across the layers in terms of their functionality and how each layer is addressed. The document also provides references and suggestions for further exploring related testing concepts.
Rails automatic test driven development
This document discusses test driven development (TDD) for Ruby on Rails applications. It introduces TDD principles like the three laws and red-green-refactor cycle. It then provides an overview of testing tools for Rails like RSpec and Capybara for writing unit and integration tests. Additional tools that help with the testing workflow are also covered, such as Spork and Guard. The document demonstrates how to run tests directly from Sublime Text and provides references for further reading on TDD and Rails testing.
TDD Basics with Angular.js and Jasmine
The document discusses Test-Driven Development (TDD). Some key points:
- TDD involves writing automated tests before writing code to ensure tests fail initially and then passing the tests by writing just enough code. This prevents writing extra code and helps design code structure.
- TDD provides benefits like confidence in code quality, catching errors early, and giving feedback on changes. Unit tests should initially fail, test individual components, and not be for finding bugs which is done through manual testing.
- The basic TDD process is to create a failing test, write just enough code to pass the test, refactor code, and repeat the process for each new feature or change. This helps integrate TDD into
Visual Studio LightSwitch (Beta 1) Overview
Visual Studio LightSwitch allows developers to quickly create professional, data-centric business applications. It provides pre-configured screen templates and pre-written code to build the basic application functionality faster. LightSwitch applications can access existing data sources like SQL Server and SharePoint. The applications are made up of projects containing data entities, screens, queries, and other resources. Developers can customize and extend LightSwitch applications through code. LightSwitch applications can be deployed to the desktop, browser, or cloud.
Episode 3 – Classes, Inheritance, Abstract Class, and Interfaces
This document provides an overview of key object-oriented programming concepts in Salesforce including classes, objects, inheritance, abstract classes, and interfaces. It discusses how classes define objects, how to instantiate objects, access specifiers, static methods, inheritance which allows extending existing classes, abstract classes which define common methods, and interfaces which enforce method signatures. Code examples are provided to demonstrate these concepts. The document also recommends books for learning Apex at different skill levels and includes an agenda and rules for the session.
Automated Testing of Web Applications
Testing is an important part of all software projects – and so is keeping sane. In order to not make the developers and testers lose their minds while verifying that a huge amount of features still work, the testing should be automated. What’s worse, the complexity of the underlying technologies often make it more challenging to test web applications than conventional software.
This talk will show you some tools and methodologies for automated testing of web apps and especially the user interface layer of web apps. It will discuss how to architect a web app for easy testing and what kind of tests should go where and in which situation. We’ll even have a look at how the customer requirements can be automatically tested and verified to work – exactly as specified by the ones paying the bills.
Writing clean and maintainable code
Writing code is easy but writing maintainable code is almost impossible. During this talk I will discuss some of the principles of coding that relates to WordPress but goes beyond that.
Android tdd
Test-driven development (TDD) is a software development process where test cases are written before code to define desired functionality, and then code is written to pass those tests. TDD results in simpler and more robust code, less debugging time, and greater confidence in refactoring. The TDD process involves adding a test, running all tests and seeing if the new test fails, writing code to pass the test, rerunning tests, and refactoring code before repeating. TDD helps avoid duplicated code and ensures requirements are met.
More Related Content
What's hot
Level Up Your Salesforce Unit Testing
Presentation for the Austin Salesforce Developers Users Group. Primarily covers the Apex code concerns with using the Apex Stub API.
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
Test Automation Canvas
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
How to get reviewers to block your changes
This document provides tips to decrease productivity by making changes that will cause code reviewers to block the changes. Some tips include adding spelling errors to commit messages, fixing bugs without linking to bug reports, making large changes without proper documentation, including few or no unit tests, and being unresponsive to reviewer comments. The overall goal of the tips is to submit low-quality changes that will frustrate and slow down the review process.
10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing
Shifting left means starting testing earlier in the development cycle by writing tests alongside code development within small teams. This eliminates surprises from late-discovered problems and ensures code meets expectations before being declared "done". To achieve superior test coverage, teams must test more by shifting left and testing as code is committed so developers get immediate feedback and bugs are fixed early. Shifting left embeds quality into every step of development and allows for continuous testing and integration to produce higher quality, shippable features faster.
Alm with tfs 2013
The document provides an overview of how to effectively use ALM with TFS 2013. It discusses how to set up iterations and areas, move work items between iterations, add work item types to the backlog, and create useful queries. It also offers tips on creating release notes, branching code, and things to automate in builds. Key points covered include using tags instead of iterations to track work, branching code to isolate releases or unfinished work, and creating a new workspace per branch.
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)
The document discusses how a company called Odobo improved their testing process by defining a unified testing framework using Groovy, Spock, and Geb. This allowed both developers and QA engineers to write automated tests in the same framework, eliminating duplicated efforts. Key aspects of the framework included using Gradle for building, Groovy as the programming language, Spock as the testing framework, and Geb for browser automation. It provided benefits like increased code reuse and happier testers across both dev and QA teams.
Agile Testing
Agile testing emphasizes:
- Collaborative, integrated teams that test early and often throughout development;
- Frequent deliveries of working software that is tested as part of being "done";
- The ability to adapt testing to changing business needs.
Some key principles of agile testing include shifting the focus of testing from the last phase to being integrated throughout development, having everybody on the team test rather than just designated testers, reducing the latency between implementing code and testing it, and treating bugs as issues to be fixed quickly rather than letting them linger.
Effective agile testing incorporates practices like automated unit and integration tests, test-driven development, automated system-level regression tests, acceptance test
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.
The Art of Giving and Receiving Code Reviews
Code reviews are one of the most effective tools we have, if we use them right. This talk discusses the technical, cultural and psychological factors that make for more productive code reviews and happier coworkers.
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?
Continuous delivery in practice (public)
Continuous delivery practices were implemented for an RTB project at Kenshoo to allow for faster development and delivery. This included having a single code branch, comprehensive testing at the unit, integration, behavioral, and staging levels, keeping builds stable, ensuring the master branch is always deployable, conducting rigorous code reviews, using real-time feedback, managing upgrades carefully, and A/B testing. It is important to constantly monitor builds and collect feedback to own the process.
Spec By Example or How to teach people talk to each other
This document introduces an approach called "Spec By Example" to improve communication between developers, QA analysts, and clients. It involves impact mapping to focus on user stories, QA and analyst pairing to create examples to describe requirements, and diverse and merge sessions for the team to collaboratively build out examples. The examples are then optimized by compressing tables and introducing parameters before being linked to automated tests through a behavior driven development approach. This unified process allows requirements, test cases, and code to have a single source of truth, makes it easy to trace work back to business needs, and improves estimation, demos, and reduces rework and issues.
Automated Acceptance Tests & Tool choice
The document discusses different layers of automated acceptance testing and compares different toolsets for each layer. The three layers are: 1) Acceptance Criteria Layer which defines test scenarios in a business-readable format, 2) Test Implementation Layer which implements tests against the system under test, and 3) Application Driver Layer which executes tests against the application. Popular tools like Cucumber, Concordion and FitNesse are compared across the layers in terms of their functionality and how each layer is addressed. The document also provides references and suggestions for further exploring related testing concepts.
Rails automatic test driven development
This document discusses test driven development (TDD) for Ruby on Rails applications. It introduces TDD principles like the three laws and red-green-refactor cycle. It then provides an overview of testing tools for Rails like RSpec and Capybara for writing unit and integration tests. Additional tools that help with the testing workflow are also covered, such as Spork and Guard. The document demonstrates how to run tests directly from Sublime Text and provides references for further reading on TDD and Rails testing.
TDD Basics with Angular.js and Jasmine
The document discusses Test-Driven Development (TDD). Some key points:
- TDD involves writing automated tests before writing code to ensure tests fail initially and then passing the tests by writing just enough code. This prevents writing extra code and helps design code structure.
- TDD provides benefits like confidence in code quality, catching errors early, and giving feedback on changes. Unit tests should initially fail, test individual components, and not be for finding bugs which is done through manual testing.
- The basic TDD process is to create a failing test, write just enough code to pass the test, refactor code, and repeat the process for each new feature or change. This helps integrate TDD into
Visual Studio LightSwitch (Beta 1) Overview
Visual Studio LightSwitch allows developers to quickly create professional, data-centric business applications. It provides pre-configured screen templates and pre-written code to build the basic application functionality faster. LightSwitch applications can access existing data sources like SQL Server and SharePoint. The applications are made up of projects containing data entities, screens, queries, and other resources. Developers can customize and extend LightSwitch applications through code. LightSwitch applications can be deployed to the desktop, browser, or cloud.
Episode 3 – Classes, Inheritance, Abstract Class, and Interfaces
This document provides an overview of key object-oriented programming concepts in Salesforce including classes, objects, inheritance, abstract classes, and interfaces. It discusses how classes define objects, how to instantiate objects, access specifiers, static methods, inheritance which allows extending existing classes, abstract classes which define common methods, and interfaces which enforce method signatures. Code examples are provided to demonstrate these concepts. The document also recommends books for learning Apex at different skill levels and includes an agenda and rules for the session.
Automated Testing of Web Applications
Testing is an important part of all software projects – and so is keeping sane. In order to not make the developers and testers lose their minds while verifying that a huge amount of features still work, the testing should be automated. What’s worse, the complexity of the underlying technologies often make it more challenging to test web applications than conventional software.
This talk will show you some tools and methodologies for automated testing of web apps and especially the user interface layer of web apps. It will discuss how to architect a web app for easy testing and what kind of tests should go where and in which situation. We’ll even have a look at how the customer requirements can be automatically tested and verified to work – exactly as specified by the ones paying the bills.
What's hot (20)
10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing
10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)
Spec By Example or How to teach people talk to each other
Spec By Example or How to teach people talk to each other
Episode 3 – Classes, Inheritance, Abstract Class, and Interfaces
Episode 3 – Classes, Inheritance, Abstract Class, and Interfaces
Similar to How to write better tests with Test Driven Development
Writing clean and maintainable code
Writing code is easy but writing maintainable code is almost impossible. During this talk I will discuss some of the principles of coding that relates to WordPress but goes beyond that.
Android tdd
Test-driven development (TDD) is a software development process where test cases are written before code to define desired functionality, and then code is written to pass those tests. TDD results in simpler and more robust code, less debugging time, and greater confidence in refactoring. The TDD process involves adding a test, running all tests and seeing if the new test fails, writing code to pass the test, rerunning tests, and refactoring code before repeating. TDD helps avoid duplicated code and ensures requirements are met.
Test Driven Development with Laravel
This document discusses test driven development (TDD) with Laravel. It begins with an introduction to the author and overview of TDD. The main benefits of TDD are described as code confidence, cleaner code, and fewer bugs. An example of building tests for a car wash management tool is provided to demonstrate the TDD cycle of red-green-refactor. Key points are made about what to test, including focusing on data transformations and keeping controllers skinny. Views are generally not tested, but using presenters allows views to be fully tested.
You cant be agile if your code sucks
What is "Agile"?
Why would someone like to be agile?
What are the 3 pillars for agile software development?
How can you achieve technical excellence in your software teams?
Are developer skills more important than languages, methods or frameworks?
Test Driven Development on Android (Kotlin Kenya)
This document discusses test-driven development (TDD) and its application to Android development. It begins with an introduction to TDD, outlining its core principles and benefits. It describes the "red, green, refactor" process and emphasizes writing tests before code. It addresses challenges with testing Android code, such as dependencies on framework classes, and recommends strategies like wrapping classes to isolate dependencies. Finally, it outlines the benefits of TDD such as reduced bugs, improved design, and increased productivity over the long run despite initial slower development.
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
The document discusses test-driven development (TDD). TDD is a software development process where test cases are created to specify requirements before code is written to pass those tests. This ensures code meets requirements. Benefits of TDD include fewer bugs due to comprehensive testing, and ability to refactor code without breaking functionality. The document provides examples of different types of tests and outlines best practices for getting started with TDD.
Adopting tdd in the workplace
Many developers know that they should be writing tests for their apps. However, it’s often hard to know how to get started or to convince your manager that you should be spending half of your time writing and maintaining test code. In this talk, you will learn how you can integrate testing into your day-to-day workflow and you’ll learn why a good test suite will not cost you a lot of time. Instead, it should end up saving you time. And as you know, the manager loves it when you manage to save time. You will understand how TDD works, how to integrate the important bits of TDD and how to build a high-quality test suite that is a pleasure to maintain. To round things out, you will also learn about Xcode 11’s new test plans feature and how you can use it to make your test suite even better!
Adopting tdd in the workplace
Learn how to gather requirements and translate them into tests. Doing this helps you adopt a TDD style of developing.
Understanding Why Testing is Importaint
The document discusses the importance of testing code through test-driven development (TDD) and behavior-driven development (BDD). It explains that TDD involves writing tests, watching them fail, making them pass, refactoring, and repeating. BDD is more complex and involves business analysts, developers, and stakeholders specifying desired behaviors as user stories. The document encourages writing unit tests because it allows for quick code changes with confidence, helps understand code design, and documents expected behavior, though it takes time initially.
Tdd
This document discusses test driven development (TDD). It begins by explaining the basic TDD process of writing a failing test, getting it to compile, making it pass without changing existing code, and then refactoring. It outlines some benefits of TDD like improved code quality and confidence in changes. It also notes some challenges like additional overhead and keeping test code clean. Overall, it argues that while TDD requires proper implementation, it can help produce higher quality code with fewer bugs.
Magento 2 Best Practice Workfow // David Lambauer // Meet Magento 2017 // Lei...
This Slidedeck was used for my talk at MMDE17 in Leipzig. The Talk is about a best practice workflow in Magento and targets developer who are used to write a lot of modules in their daily work.
Driving application development through behavior driven development
This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.
2015 msu-code-review
A brief presentation on scientific software development - "How to grow a sustainable software development process."
Sap inside track Munich 2017
Discuss Legacy Code and the different approaches to get it under control. Discuss different methods for testing, Unit Tests with ABAP Test Seams. Discuss Software Exploration Tools, Moose2Model, SAP2Moose
Tdd practices
This document discusses test-driven development (TDD) practices. It covers the characteristics of good tests, what TDD is and why it is used, the TDD development cycle of red-green-refactor, best practices for TDD, anti-patterns to avoid, and practices for writing testable code. The key aspects of TDD outlined are writing tests before code, running tests after each small code change, and refactoring code between test cycles.
Austin Elixir: Slack Bots With Hedwig
This document provides information about using the Hedwig Slack bot plugin for Elixir. It discusses self-promotion, getting started by following the Hedwig_slack README, generating a robot worker, configuring tokens, and using responders and macros to handle messages. Suggestions are given such as using "respond" style responders instead of "hear" to avoid loops, keeping app logic separate from responders, and getting separate dev and prod tokens to avoid rate limits.
Intro TDD Portuguese developers meetup London 16/04/2014
Test Driven Development (TDD) follows three main laws: only write production code to pass a failing test, only write enough test code to fail, and only write enough production code to pass the test. TDD brings benefits like improved debugging, courage to refactor, documentation, and design. Good unit tests are atomic, isolated, repeatable, revealing, and fast. The structure of a test is to arrange inputs, act on the system under test, and assert the expected outcomes. Strategies for TDD include using obvious implementations, faking dependencies, and triangulating tests. Practicing TDD involves code katas, communities, and conferences.
Bootstrapping Quality
A talk given to CS seniors at Seattle University, who are embarking on their final year capstone project.
An Introduction To Software Development - Test Driven Development, Part 1
This presentation is a part of the COP2271C college level course taught at the Florida Polytechnic University located in Lakeland Florida. The purpose of this course is to introduce Freshmen students to both the process of software development and to the Python language.
The course is one semester in length and meets for 2 hours twice a week. The Instructor is Dr. Jim Anderson.
A video of Dr. Anderson using these slides is available on YouTube at:
http://youtu.be/bCp1fbAd56k
That worked before
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.
Similar to How to write better tests with Test Driven Development (20)
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
Magento 2 Best Practice Workfow // David Lambauer // Meet Magento 2017 // Lei...
Magento 2 Best Practice Workfow // David Lambauer // Meet Magento 2017 // Lei...
Driving application development through behavior driven development
Driving application development through behavior driven development
Intro TDD Portuguese developers meetup London 16/04/2014
Intro TDD Portuguese developers meetup London 16/04/2014
An Introduction To Software Development - Test Driven Development, Part 1
An Introduction To Software Development - Test Driven Development, Part 1
Recently uploaded
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
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
Liberarsi dai framework con i Web Component.pptx
In Italian
Presentazione sulle feature e l'utilizzo dei Web Component nell sviluppo di pagine e applicazioni web. Racconto delle ragioni storiche dell'avvento dei Web Component. Evidenziazione dei vantaggi e delle sfide poste, indicazione delle best practices, con particolare accento sulla possibilità di usare web component per facilitare la migrazione delle proprie applicazioni verso nuovi stack tecnologici.
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.
How Can Hiring A Mobile App Development Company Help Your Business Grow?
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
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.
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
What next after learning python programming basics
What next after learning python programming basics
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.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
如何办理(hull学位证书)英国赫尔大学毕业证硕士文凭原版一模一样
原版定制【微信:bwp0011】《(hull学位证书)英国赫尔大学毕业证硕士文凭》【微信:bwp0011】成绩单 、雅思、外壳、留信学历认证永久存档查询，采用学校原版纸张、特殊工艺完全按照原版一比一制作（包括：隐形水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠，文字图案浮雕，激光镭射，紫外荧光，温感，复印防伪）行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备，十五年致力于帮助留学生解决难题，业务范围有加拿大、英国、澳洲、韩国、美国、新加坡，新西兰等学历材料，包您满意。
【业务选择办理准则】
一、工作未确定，回国需先给父母、亲戚朋友看下文凭的情况，办理一份就读学校的毕业证【微信bwp0011】文凭即可
二、回国进私企、外企、自己做生意的情况，这些单位是不查询毕业证真伪的，而且国内没有渠道去查询国外文凭的真假，也不需要提供真实教育部认证。鉴于此，办理一份毕业证【微信bwp0011】即可
三、进国企，银行，事业单位，考公务员等等，这些单位是必需要提供真实教育部认证的，办理教育部认证所需资料众多且烦琐，所有材料您都必须提供原件，我们凭借丰富的经验，快捷的绿色通道帮您快速整合材料，让您少走弯路。
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
【关于价格问题（保证一手价格）】
我们所定的价格是非常合理的，而且我们现在做得单子大多数都是代理和回头客户介绍的所以一般现在有新的单子 我给客户的都是第一手的代理价格，因为我想坦诚对待大家 不想跟大家在价格方面浪费时间
对于老客户或者被老客户介绍过来的朋友，我们都会适当给一些优惠。
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
All you need to know about Spring Boot and GraalVM
All you need to know about Spring Boot and GraalVM 🐰
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Presented at NLJUG's J-Spring 2024.
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
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
Mobile App Development Company In Noida | Drona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
Recently uploaded (20)
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers.pptx
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
How Can Hiring A Mobile App Development Company Help Your Business Grow?
How Can Hiring A Mobile App Development Company Help Your Business Grow?
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
YAML crash COURSE how to write yaml file for adding configuring details
YAML crash COURSE how to write yaml file for adding configuring details
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
What next after learning python programming basics
What next after learning python programming basics
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
All you need to know about Spring Boot and GraalVM
All you need to know about Spring Boot and GraalVM
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
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
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
How to write better tests with Test Driven Development
- 1. Write Better Tests With TDD Alex Hoffman
- 2. @alexhoffman617 • Test Driven Development • Writing tests to drive development in small feedback cycles
- 3. @alexhoffman617 • TDD rules as defined by Rob Martin (author of the Agile Manifesto) • You are not allowed to write any production code unless it is to make a failing unit test pass. • You are not allowed to write any more of a unit test than is sufficient to fail • You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
- 5. @alexhoffman617 • twitter: @alexhoffman617 • github: alexhoffman617
- 7. @alexhoffman617 Code:Tests: Requirements: • Take a number input • Output true if its Tuesday • Output false if its not Tuesday
- 8. @alexhoffman617 • Code follows requirements • Helps developers think about code on a more granular level • Makes code more readable • Prevents unnecessary code or complications
- 10. @alexhoffman617 • Lets Be Practical • Do it when you have branching logic • Complex situations • Low effort, high impact
- 12. @alexhoffman617 • Test Driven Development is using Red-Green refactor • By writing tests before coding, you’ll test your requirements • Will improve how you think about coding and testing, readability, and your chance of catching edge cases • Promotes world peace
Editor's Notes
- What is TDD
- Who thinks they do TDD on a regular bases Rob Martin Agile Manifesto 3 rules
- Red Green Refactoring Now who thinks they do tdd on a regular basis
- About Me: JavaScript Specialty Lead at Excella JavaScript and Angular Enthusiast Certified Scrum Master and Developer Angular DC Organizer Enjoys sports, good food, and losing at bar trivia
- Red Green Refactor Example
- Writing Tests to Code
- Why TDD
- Real World Example
- Lets Be Practical Not everyone will be in a situation to TDD all the time Pressure from your supervisor, client, etc. Lack of buy in from your team Do it when you can Even partial use can help you think about testing Identify scenarios where you may really benefit Complex code Lots of expected edge cases
- Too boring fell asleep
- Takeaways