An Overview of automated testing (1)
Download as PPTX, PDF0 likes223 views
This document discusses automated testing and different levels of testing. It explains that automated tests should be written to achieve good design, clarify how a system works, understand the system, and minimize risks. While automated tests require time to write, maintain, and execute, these efforts can be minimized by making tests easy to run and maintain with minimal dependencies. The document also discusses different perspectives on testing, including what developers and customers want. Developers are concerned with complexity and risk, while customers care about functionality and user scenarios. It notes that while unit tests have limitations, acceptance tests are also limited as they are slow, fragile, and not isolated. The "lost layer" of the testing pyramid is also mentioned - the presentation, service, and persistence
1 of 21
Download to read offline
Recommended
Type mock isolator
Type mock isolatorMaslowB
油
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.Real Life Unit Testing
Real Life Unit TestingDror Helper
油
Tools are not enough. If you want to succeed overtime, you need more ammunition. Some people call them best practices. We call them real life lessons.Why should every developer unit test his code, Unit testing tools,TDD & Unit testing best practices, How to avoid writing fragile tests and Testing special scenariosAdvanced unit testing real life examples and mistakes
Advanced unit testing real life examples and mistakesMilan Vukoje
油
This document discusses unit testing best practices and common mistakes. It provides examples from testing a core application called SCA. Key topics covered include goals of unit testing like improved quality, dangers like additional costs, test organization patterns like using a database sandbox or fake database, lessons learned like avoiding fragile tests, tips for Visual Studio and TFS, and common code smells to avoid like long test setup logic. The overall message is that unit tests provide benefits but also risks, and best practices and avoiding code smells can help maximize the upsides and minimize the downsides of unit testing.Mixing testing types to improve your testing results
Mixing testing types to improve your testing resultsPractiTest
油
How to mix different testing types to optimize your testing results.
Test type classifications and examples of "mix and match" practices.
Full webinar recording can be viewed here:
https://www.practitest.com/qa-learningcenter/webinars/mixing-testing-types-to-improve-your-work/
Lecture 11
Lecture 11Charles Palmer
油
This lecture discusses testing game mods during the implementation process. It emphasizes the importance of testing early and often to identify bugs and issues. Different types of testing are described, including functionality, compliance, compatibility, localization, soak, beta, regression, load, and multiplayer testing. The assignment is to build out a section of the student's Skyrim mod by adding a location, enemies, loot, dialogue, and a trap. Students are then instructed to conduct playtesting with 5 players and document any issues or feedback in a testing log to submit. The goal of playtesting is to improve the mod, not just show it off.Roy Osherove TDD From Scratch
Roy Osherove TDD From ScratchRoy Osherove
油
Roy Osherove provides training courses on test-driven development (TDD), behavior-driven development (BDD), and consulting/coaching services. He teaches TDD techniques for JavaScript, Ruby, Java, C#, and EpiServer/MVC frameworks. He also offers leadership training through 5whys.com. His focus is on using TDD to drive development, influence design decisions, and enable incremental delivery and early feedback. He advocates for TDD when code will need to be maintained long-term or for minimum viable products, but not for proofs of concept or short-lived code.Game Design 2: Expert Evaluation of User Interfaces
Game Design 2: Expert Evaluation of User InterfacesDavid Farrell
油
This document discusses expert evaluation methods for assessing game designs without end users. It describes cognitive walkthroughs where experts think like users to evaluate if goals and actions are clear. It also discusses heuristic evaluations where experts assess how a design conforms to predefined usability guidelines like Nielsen's heuristics. Both methods are alternatives to user testing that are quicker and cheaper. A minimum of three to five expert evaluators is typically recommended to find different usability issues.An Introduction to unit testing
An Introduction to unit testingSteven Casey
油
This document provides an introduction to unit testing. It discusses what should and should not be tested, how to structure tests using the Arrange Act Assert pattern, and tips for writing good tests. Some key points covered include testing complex code, edge cases, classes that change often, and avoiding testing globals, statics, and database interactions. The goal is to have tests that are independent, test single behaviors, and help find bugs when code changes.The problem with tdd
The problem with tddDror Helper
油
Dror Helper discusses the potential benefits and challenges of test-driven development (TDD). Some key points made include:
1) TDD involves writing tests before code to ensure functionality is tested and defined up front, though this approach seems counterintuitive to some.
2) Studies show TDD can increase development speed and lower defect rates compared to traditional development methods. However, TDD requires additional time spent writing tests initially.
3) Not all code is easily testable, such as user interfaces, but TDD can still be applied to test business logic. Overall, TDD aims to prevent defects and enable modular, maintainable code through iterative testing.
4) While TDD facesTDD - Designing with Expectations, not Implementations
TDD - Designing with Expectations, not ImplementationsHarshith Shetty
油
TDD approach made simple based on the experience and journey gone through learning and implementing it in a large scale android app, i.e. Shaadi.com.User Story vs. UseCase : Introductory Primer
User Story vs. UseCase : Introductory PrimerKristyn Greenwood
油
An example of typical training material provided to new employees. Even the most experienced designers can use a refresher and it helps to establish common references and understanding.Unit testing
Unit testingPiXeL16
油
Unit testing involves testing individual units or components of code, such as classes or methods, in isolation from the rest of the code base. A unit test asserts certain conditions or tests for specific behaviors and returns a pass/fail result. The purpose of unit testing is to validate that each piece of code works as intended, allowing code to be refactored with confidence and problems to be identified early. Best practices for unit testing include writing tests for new code, designing code for testability, and following an arrange-act-assert structure. Tests should be fast, isolated, and clearly named. Unit testing promotes code quality, documentation, and easier refactoring.Code Review
Code ReviewMikalai Alimenkou
油
Presentation from Agile Base Camp 2 conference (Kiev, May 2010) and AgileDays'11 (Moscow, March 2011) about one of the most useful engineering practices from XP world.Exploratory testing
Exploratory testingHarshani Wickramaarachchi
油
Exploratory testing is an approach to software testing that involves simultaneous learning, test design, and test execution. It seeks to understand how an application works and find bugs by forcing the software to exhibit its capabilities. Some advantages are that less preparation is needed and important bugs can be found fast, while disadvantages include that the exact tests performed may not be documented or repeated identically.JavaScript Unit Testing
JavaScript Unit TestingMihail Gaberov
油
This document discusses JS unit testing and provides guidance on how to implement it. It explains that unit tests isolate and test discrete functions to ensure they work as intended. This helps refactor code to be modular, scalable, and easier to understand. While unit tests add initial time, they speed up development in the long run. Common JS testing libraries include Mocha, Jasmine, and assertion libraries like Chai to validate results. The document also provides example unit test code and links to additional resources on JS testing.Is this how you hate unit testing?
Is this how you hate unit testing?Steven Mak
油
This document discusses unit testing and integration testing. It begins by stating that the author hates unit testing because it doesn't catch many bugs, integration tests are still needed, and it wastes time. It then asks if integration testing means testing at the integration level. Finally, it advocates writing good focused unit tests and using collaboration and contract tests, and notes that refactoring is important when writing unit tests.Test Driven Development
Test Driven DevelopmentSamnang Chhun
油
The document discusses test-driven development (TDD) and design-driven development (DDD). It advocates for writing tests before code using short iterative development cycles. TDD helps produce clean code that fulfills requirements by making developers think about required behavior, providing documentation, and improving quality. Common objections to TDD are addressed, noting that it forces understanding of code and tests, creates reusable modular code, and drives simplicity. Guidelines for effective TDD include writing small focused tests with descriptive intentions that are independent and repeatable.Unit testing (workshop)
Unit testing (workshop)Foyzul Karim
油
1. Create test classes for each item type (book, food, medical, imported, etc.) and calculate tax amounts
2. Write test methods that pass sample baskets of items to the calculation method and assert the expected tax and total amounts are returned
3. Include test cases that validate tax rounding is performed correctly for different tax rates and item prices
4. Write exception tests to ensure invalid item types or negative prices throw the expected exceptionsTest Driven Development
Test Driven DevelopmentMd. Hasan Basri (Angel)
油
This document discusses test-driven development (TDD) and its benefits. It advocates following a process of writing tests before code to ensure code quality and prevent bugs. TDD involves writing a test, seeing it fail, writing the minimum code to pass the test, and refactoring code as needed. While initially time-consuming, TDD can save time in the long run by producing well-designed, modular code that is documented by tests and catches errors early. The document provides examples of TDD and cautions that intelligence alone is not enough - following a disciplined process is important for success.Value of Unit Testing
Value of Unit TestingFerose Khan J
油
This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.Clean Code
Clean Codeswaraj Patil
油
Presentation on writing clean and maintainable good. I have present really simple steps to write high quality code and share many more benefit of writing clean code.Unit testing
Unit testingAdam Birr
油
This document discusses improving server-side unit testing methods. It identifies issues with current server unit tests such as dependencies between classes and lack of clear purpose or expectations. It recommends defining a "unit" as a single Java class and mocking dependencies. Tests should describe specifications, improve code quality, and reduce bugs. While DRY principles are best for production code, DAMP (Descriptive And Meaningful Phrases) is preferable for unit tests to prioritize readability over code duplication. Each test should focus on one thing, use plain language, and assert expected outcomes rather than null values.Clean code
Clean codeUday Pratap Singh
油
This ppt is based on the book "Clean Code" written by Robert C Martin. It's a wonderful book and cover all the mistakes that we do while writing bad code. I am sharing few good practices shared in the book, hope you will like itDelhi second draft 
Delhi second draft vaibhav lokhande
油
This document discusses how to deploy code confidently through test-driven development (TDD). It recommends using TDD, Storybook, and automated testing to reduce long QA cycles, bugs taking up sprints, and panic during production deployments. It provides examples of writing failing and passing tests in React using TDD principles before writing code. Testing libraries that can be used for React automation testing are also listed.Keeping business logic out of your UIs
Keeping business logic out of your UIsPetter Holmstr旦m
油
This document discusses keeping business logic out of user interfaces (UIs) by separating the UI layer from the business logic layer. It recommends:
- Placing the transaction boundary between the UI and backend to minimize backend calls.
- Ensuring service layers are highly cohesive and avoid general "god services".
- Separating reading data (queries) from writing data (commands) to allow for optimizations.
- Avoiding CRUD-style UIs and services that move business logic into the user's head, and base UIs and services on actual business processes instead.
- Considering introducing a command-based architecture where commands and queries model business operations to further separate business logic from the UI.Effective Unit Testing
Effective Unit TestingEyal Kenig
油
The document discusses best practices for effective unit testing. It covers the test pyramid, benefits of good tests, test schemas, tips and guidelines. The test pyramid emphasizes having more simple unit tests, fewer integration tests, and even fewer end-to-end tests. Good tests provide confidence, help design, document requirements and make code more robust. Tests should have clear names, single assertions, and arrange-act-assert structure. Edge cases, exceptions and return values should be prioritized. Tests should be readable and not rely on implementation details.Unit testing in PHP
Unit testing in PHPChonlasith Jucksriporn
油
This document discusses unit testing in PHP. It explains that unit testing helps find bugs early when new code is added and prevents existing code from breaking. Unit tests should test individual units of code in isolation and be fast, isolated, repeatable and self-verifying. The document recommends writing unit tests before coding using a test-driven development approach. It also provides an overview of PHPUnit and best practices for writing high-quality unit tests.Lessons Learned When Automating
Lessons Learned When AutomatingAlan Richardson
油
I attended the Tabara de Testare testing group on 3rd February 2015 to present "Lessons Learned When Automating. A live stream from UK to Romania.
http://compendiumdev.co.uk/page/tabaradetestare201602
I've been asked some very challenging questions about lessons learned, and how decisions are made during the process of automating and performing technical testing. In this webinar I'm going to answer them based on my experience. We'll discus how we know 'what to automate' which means we have to split our analysis into 'detection' and 'testing'. We'll cover lessons learned from solving problems, and making mistakes, and steps we can take during the problem solving process e.g. for intermittent failures, and possible tool bugs. We'll discuss abstraction levels and the different levels of the technology stack to automate: how to do it, and how we make the decisions. We'll discuss coding primarily the differences, and the overlap, between the needs for coding for testing and coding for production deployment. We'll also cover some WebDriver specific answers to some of these questions. I'm also going to describe books and techniques that have helped me over the years when trying to deal with these questions on production projects.
Why Automated Testing Matters To DevOps
Why Automated Testing Matters To DevOpsdpaulmerrill
油
Automated testing is a pain in my ear! Why cant QA get it right? Why do the tests keep breaking? And for Petes sake, stop blaming the infrastructure!
Ok, maybe you chose a different word than ear.
How often do you have thoughts like this? Daily?
Lets talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)Nacho Cougil
油
Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it?
Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests.
We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java.
At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code
===
Presentation (revisited & updated) shared at JDD 2022:
https://jdd.org.pl/lecture_2022/#id=78434More Related Content
What's hot (19)
The problem with tdd
The problem with tddDror Helper
油
Dror Helper discusses the potential benefits and challenges of test-driven development (TDD). Some key points made include:
1) TDD involves writing tests before code to ensure functionality is tested and defined up front, though this approach seems counterintuitive to some.
2) Studies show TDD can increase development speed and lower defect rates compared to traditional development methods. However, TDD requires additional time spent writing tests initially.
3) Not all code is easily testable, such as user interfaces, but TDD can still be applied to test business logic. Overall, TDD aims to prevent defects and enable modular, maintainable code through iterative testing.
4) While TDD facesTDD - Designing with Expectations, not Implementations
TDD - Designing with Expectations, not ImplementationsHarshith Shetty
油
TDD approach made simple based on the experience and journey gone through learning and implementing it in a large scale android app, i.e. Shaadi.com.User Story vs. UseCase : Introductory Primer
User Story vs. UseCase : Introductory PrimerKristyn Greenwood
油
An example of typical training material provided to new employees. Even the most experienced designers can use a refresher and it helps to establish common references and understanding.Unit testing
Unit testingPiXeL16
油
Unit testing involves testing individual units or components of code, such as classes or methods, in isolation from the rest of the code base. A unit test asserts certain conditions or tests for specific behaviors and returns a pass/fail result. The purpose of unit testing is to validate that each piece of code works as intended, allowing code to be refactored with confidence and problems to be identified early. Best practices for unit testing include writing tests for new code, designing code for testability, and following an arrange-act-assert structure. Tests should be fast, isolated, and clearly named. Unit testing promotes code quality, documentation, and easier refactoring.Code Review
Code ReviewMikalai Alimenkou
油
Presentation from Agile Base Camp 2 conference (Kiev, May 2010) and AgileDays'11 (Moscow, March 2011) about one of the most useful engineering practices from XP world.Exploratory testing
Exploratory testingHarshani Wickramaarachchi
油
Exploratory testing is an approach to software testing that involves simultaneous learning, test design, and test execution. It seeks to understand how an application works and find bugs by forcing the software to exhibit its capabilities. Some advantages are that less preparation is needed and important bugs can be found fast, while disadvantages include that the exact tests performed may not be documented or repeated identically.JavaScript Unit Testing
JavaScript Unit TestingMihail Gaberov
油
This document discusses JS unit testing and provides guidance on how to implement it. It explains that unit tests isolate and test discrete functions to ensure they work as intended. This helps refactor code to be modular, scalable, and easier to understand. While unit tests add initial time, they speed up development in the long run. Common JS testing libraries include Mocha, Jasmine, and assertion libraries like Chai to validate results. The document also provides example unit test code and links to additional resources on JS testing.Is this how you hate unit testing?
Is this how you hate unit testing?Steven Mak
油
This document discusses unit testing and integration testing. It begins by stating that the author hates unit testing because it doesn't catch many bugs, integration tests are still needed, and it wastes time. It then asks if integration testing means testing at the integration level. Finally, it advocates writing good focused unit tests and using collaboration and contract tests, and notes that refactoring is important when writing unit tests.Test Driven Development
Test Driven DevelopmentSamnang Chhun
油
The document discusses test-driven development (TDD) and design-driven development (DDD). It advocates for writing tests before code using short iterative development cycles. TDD helps produce clean code that fulfills requirements by making developers think about required behavior, providing documentation, and improving quality. Common objections to TDD are addressed, noting that it forces understanding of code and tests, creates reusable modular code, and drives simplicity. Guidelines for effective TDD include writing small focused tests with descriptive intentions that are independent and repeatable.Unit testing (workshop)
Unit testing (workshop)Foyzul Karim
油
1. Create test classes for each item type (book, food, medical, imported, etc.) and calculate tax amounts
2. Write test methods that pass sample baskets of items to the calculation method and assert the expected tax and total amounts are returned
3. Include test cases that validate tax rounding is performed correctly for different tax rates and item prices
4. Write exception tests to ensure invalid item types or negative prices throw the expected exceptionsTest Driven Development
Test Driven DevelopmentMd. Hasan Basri (Angel)
油
This document discusses test-driven development (TDD) and its benefits. It advocates following a process of writing tests before code to ensure code quality and prevent bugs. TDD involves writing a test, seeing it fail, writing the minimum code to pass the test, and refactoring code as needed. While initially time-consuming, TDD can save time in the long run by producing well-designed, modular code that is documented by tests and catches errors early. The document provides examples of TDD and cautions that intelligence alone is not enough - following a disciplined process is important for success.Value of Unit Testing
Value of Unit TestingFerose Khan J
油
This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.Clean Code
Clean Codeswaraj Patil
油
Presentation on writing clean and maintainable good. I have present really simple steps to write high quality code and share many more benefit of writing clean code.Unit testing
Unit testingAdam Birr
油
This document discusses improving server-side unit testing methods. It identifies issues with current server unit tests such as dependencies between classes and lack of clear purpose or expectations. It recommends defining a "unit" as a single Java class and mocking dependencies. Tests should describe specifications, improve code quality, and reduce bugs. While DRY principles are best for production code, DAMP (Descriptive And Meaningful Phrases) is preferable for unit tests to prioritize readability over code duplication. Each test should focus on one thing, use plain language, and assert expected outcomes rather than null values.Clean code
Clean codeUday Pratap Singh
油
This ppt is based on the book "Clean Code" written by Robert C Martin. It's a wonderful book and cover all the mistakes that we do while writing bad code. I am sharing few good practices shared in the book, hope you will like itDelhi second draft
Delhi second draft vaibhav lokhande
油
This document discusses how to deploy code confidently through test-driven development (TDD). It recommends using TDD, Storybook, and automated testing to reduce long QA cycles, bugs taking up sprints, and panic during production deployments. It provides examples of writing failing and passing tests in React using TDD principles before writing code. Testing libraries that can be used for React automation testing are also listed.Keeping business logic out of your UIs
Keeping business logic out of your UIsPetter Holmstr旦m
油
This document discusses keeping business logic out of user interfaces (UIs) by separating the UI layer from the business logic layer. It recommends:
- Placing the transaction boundary between the UI and backend to minimize backend calls.
- Ensuring service layers are highly cohesive and avoid general "god services".
- Separating reading data (queries) from writing data (commands) to allow for optimizations.
- Avoiding CRUD-style UIs and services that move business logic into the user's head, and base UIs and services on actual business processes instead.
- Considering introducing a command-based architecture where commands and queries model business operations to further separate business logic from the UI.Effective Unit Testing
Effective Unit TestingEyal Kenig
油
The document discusses best practices for effective unit testing. It covers the test pyramid, benefits of good tests, test schemas, tips and guidelines. The test pyramid emphasizes having more simple unit tests, fewer integration tests, and even fewer end-to-end tests. Good tests provide confidence, help design, document requirements and make code more robust. Tests should have clear names, single assertions, and arrange-act-assert structure. Edge cases, exceptions and return values should be prioritized. Tests should be readable and not rely on implementation details.Unit testing in PHP
Unit testing in PHPChonlasith Jucksriporn
油
This document discusses unit testing in PHP. It explains that unit testing helps find bugs early when new code is added and prevents existing code from breaking. Unit tests should test individual units of code in isolation and be fast, isolated, repeatable and self-verifying. The document recommends writing unit tests before coding using a test-driven development approach. It also provides an overview of PHPUnit and best practices for writing high-quality unit tests.Similar to An Overview of automated testing (1) (20)
Lessons Learned When Automating
Lessons Learned When AutomatingAlan Richardson
油
I attended the Tabara de Testare testing group on 3rd February 2015 to present "Lessons Learned When Automating. A live stream from UK to Romania.
http://compendiumdev.co.uk/page/tabaradetestare201602
I've been asked some very challenging questions about lessons learned, and how decisions are made during the process of automating and performing technical testing. In this webinar I'm going to answer them based on my experience. We'll discus how we know 'what to automate' which means we have to split our analysis into 'detection' and 'testing'. We'll cover lessons learned from solving problems, and making mistakes, and steps we can take during the problem solving process e.g. for intermittent failures, and possible tool bugs. We'll discuss abstraction levels and the different levels of the technology stack to automate: how to do it, and how we make the decisions. We'll discuss coding primarily the differences, and the overlap, between the needs for coding for testing and coding for production deployment. We'll also cover some WebDriver specific answers to some of these questions. I'm also going to describe books and techniques that have helped me over the years when trying to deal with these questions on production projects.
Why Automated Testing Matters To DevOps
Why Automated Testing Matters To DevOpsdpaulmerrill
油
Automated testing is a pain in my ear! Why cant QA get it right? Why do the tests keep breaking? And for Petes sake, stop blaming the infrastructure!
Ok, maybe you chose a different word than ear.
How often do you have thoughts like this? Daily?
Lets talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)Nacho Cougil
油
Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it?
Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests.
We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java.
At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code
===
Presentation (revisited & updated) shared at JDD 2022:
https://jdd.org.pl/lecture_2022/#id=78434Before Kaggle : from a business goal to a Machine Learning problem 
Before Kaggle : from a business goal to a Machine Learning problem Dataiku
油
Many think that a Data Science is like a Kaggle competition. There are, however big differences in the approach. This presentation is about designing carefully your evaluation scheme to avoid overfitting and unexpected production performances.
This is a presentation by Pierre Gutierrez (Dataikus data scientist).
Before Kaggle
Before KagglePierre Gutierrez
油
Many think that a Data Science is like a Kaggle competition. There are, however big differences in the approach. This presentation is about designing carefully your evaluation scheme to avoid overfitting and unexpected production performances. QA and scrum
QA and scrumclintonbosch
油
Recently I was asked to to a presentation presentation at University of Cape Town entitled QA and SCRUM. This made very little sense to me but it did substantiate my belief that the understanding of agile development is generally very superficial ...TDD - Seriously, try it! - Bucarest Tech Week
TDD - Seriously, try it! - Bucarest Tech WeekNacho Cougil
油
Join this session to see the benefits of Test-Driven Development (TDD), and understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests. We will go over some history about TDD and list the main advantages and disadvantages that most developers who practice it find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD by seeing how to do it step by step with an example of a "live" coding session with Java. At the end of the session, you will have a wider understanding of TDD and why it's interesting to master it. Also, you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code.
---
Presentation shared at Bucharest Tech Week '23TDD - Seriously, try it! - Tr坦jmiasto Java User Group (17th May '23)
TDD - Seriously, try it! - Tr坦jmiasto Java User Group (17th May '23)ssusercaf6c1
油
Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it?
Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests.
We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java.
At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code
---
Presentation shared at Tr坦jmiasto Java User Group
Public group 17th of May '23TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)Nacho Cougil
油
Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it?
Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests.
We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java.
At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code
---
Presentation shared at Tr坦jmiasto Java User Group (17th May '23)Introduzione allo Unit Testing
Introduzione allo Unit TestingStefano Ottaviani
油
La scrittura di test automatici nello sviluppo software 竪 ormai di fondamentale importanza, in quanto permette di:
1. Individuare e correggere molto prima, gi in fase di sviluppo, i bug.
2. Sviluppare e testare pi湛 velocemente il codice, riducendo di molto le volte in cui bisogna ricorrere al debugger.
3. Essere molto pi湛 confidenti che una modifica fatta ad un "vecchio" pezzo di codice non "rompa" tutto il resto e non funzioni pi湛 niente (ovviamente scoprendolo quando ormai si 竪 rilasciato in produzione!).
Questi sono "solo" 3 di una quindicina di benefici che sono riuscito ad elencare, ottenibili utilizzando una pratica durante lo sviluppo del codice: la scrittura di test automatici.
Con questo workshop vogliamo introdurre gli sviluppatori ai test automatici, una pratica purtroppo non ancora conosciuta e utilizzata quanto meriterebbe, che pu嘆 cambiare radicalmente il modo con cui scriviamo il codice, portandolo verso un approccio pi湛 "ingegneristico".
Faremo una panoramica sulle varie tipologie di test e sui benefici che possono portare, approfondendo in particolare i test unitari (unit test) e d'integrazione (integration test).
I test automatici sono un argomento trasversale ai linguaggi di programmazione, perci嘆 potrete seguire il workshop a prescindere da quale linguaggio utilizziate.Type mock isolator
Type mock isolatorMaslowB
油
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It notes the strengths and weaknesses of unit testing, as well as best practices for writing good unit tests. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements to make unit testing code without changes to design. Research on TDD is cited that found those using TDD wrote more tests and were more productive.An Introduction To Software Development - Final Review
An Introduction To Software Development - Final ReviewBlue Elephant Consulting
油
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: https://www.youtube.com/watch?v=c2CTDm19LpgTDD: seriously, try it! 
TDD: seriously, try it! Nacho Cougil
油
Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it?
In this presentation we will see the benefits of Test-Driven Development (TDD), understand how it works and what the benefits are of using it. We will see in a more detailed approach this way of developing software, where our software is always built guided by tests.
We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of "live" coding session with Java.
At the end of the session, we hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code Devday2016 real unittestingwithmockframework-phatvu
Devday2016 real unittestingwithmockframework-phatvuPhat VU
油
This document discusses real unit testing and the use of mock frameworks. It provides an introduction to unit testing and why it is important. It explains that real unit testing involves mocking dependencies so that units can be tested in isolation without concerning dependencies. The document then discusses mock objects and frameworks like Mockito that allow creating mock dependencies. It provides examples of how to use Mockito to mock dependencies and test units without their implementation. It also covers some Mockito features and limitations as well as best practices for unit testing.Exploratory Testing Explained
Exploratory Testing ExplainedTechWell
油
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. Jon Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. Jon focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.Tec314f
Tec314fJohn Art
油
Scott Love is a consultant, trainer, and author who specializes in FileMaker Pro solutions. He discusses the challenges of quality assurance (QA) for FileMaker projects, as they often have small budgets and tight timelines. He reviews the key elements of an effective QA process, including establishing requirements, developing test plans and cases, tracking bugs, and using tools like Analyzer and Brushfire. Love emphasizes that QA should start early in design and continue through development, testing, deployment, and user acceptance. The overall goal is to have a clear and communicative process to manage risks and meet the project's quality standards.Test driven development v1.0
Test driven development v1.0Ganesh Kondal
油
This document outlines an agenda for a presentation on Test Driven Development (TDD) best practices. The agenda includes sections on an overview and introduction to TDD, what TDD is and the process, challenges of TDD, learning and best practices for sustaining TDD, frameworks and variations of TDD, and a question and answer period. Some key best practices discussed are writing tests before code, focusing tests on functionality rather than code structure, and establishing governance and training to ensure proper adoption of TDD.Twelve practices of XP_Se lect5 btech
Twelve practices of XP_Se lect5 btechIIITA
油
The document describes the twelve core practices of extreme programming (XP). It discusses each practice in 1-2 paragraphs, covering pair programming, refactoring, simple design, collective code ownership, continuous integration, on-site customer, small releases, 40-hour work week, coding standards, system metaphor, planning game, and testing (including unit and acceptance testing). The advantages include customer focus, incremental releases, and continuous testing/integration improving quality. Disadvantages include being suited for a single co-located team and not working as well without customer involvement or for large scalable systems.User Stories from Scenarios
User Stories from ScenariosRavikanth-BA
油
In this advanced business analysis training session, you will learn User Stories from Scenarios. Topics covered in this session are:
What is a Use Case?
The Purpose of Use Case Analysis
Managing the Building of Product
The Basic Development Loop
Analysis paralysis how much is enough
Conceptual model development
Style Guide development
Usability testing during agile increments
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Automated testers agile evangelist
Automated testers agile evangelistArrows Group
油
The document discusses the role of automated testers in both waterfall and agile projects. It notes that while test automation was seen as essential in waterfall, the high costs of licenses, support, and maintenance often outweighed the benefits. In agile, test automation is more effective when developers implement and "pass" acceptance tests themselves rather than delegating testing to separate testers. Having dedicated automated testers risks silos, miscommunication, testers falling behind and an uncritical approach. The document argues developers should automate tests through BDD/ATDD to find defects early and refactor confidently. While testers can help pair and extend tests, developers don't need dedicated automated testers to write good automated tests.An Overview of automated testing (1)
- 1. An Overview of the automated testing And the forgotten level of the testing pyramid
- 2. Why is a programmer talking about tests?
- 3. Pros vs Cons Why? Is it worth it ?
- 4. Whyshould anyone write automated tests? One should write an automated test to achieve a good design. to clarify how the system works. to understand the system. to minimize risks. to test a system.
- 5. Is it worth it? Automatize tests require time to write. time to adjust, fix and maintain. time to setup/execute.
- 6. How to minimize the efforts? Writing tests that... ... are easy to run. are easy to write. require minimal maintenance.
- 7. Case scenario MD5? OCR? Don't overestimate assertion over output!!! Name: Hannah Date: 14th September Feature: Loves her cat Pebbles How to test?
- 8. Gathering information "Truth can only be found in one place: the code." Robert C. Martin, Clean Code Unit Test What the developer wants Acceptance Test What the customer wants Code What the program does
- 10. What developers want There are two main issues that concern the programmer: The complexity The risk
- 11. Dealing with complexity There is only one way to deal with complexity: avoiding it, usually by abstraction Separation of concerns High level of abstraction Wishful thinking: imagine there is a function that solves the problem
- 12. TDD and Abstraction Describe our intentions before we write how (single responsibility) Minimize the number of collaborators. Minimize the scope.
- 14. Unit Tests Limitations - if the units work well in isolation, we do not know if they work well together. - Unit tests rely on doubles (specially mocks and stubs). There is a sane level of usage for mocks!!!
- 15. What the customer wants What the customer wants Acceptance test Acceptance test definition of done + system documentation Practical scenarios helps to identify ambiguous and contradictory requirements. Acceptance tests focus on real user scenarios
- 16. Acceptance tests limitations They are slow They are fragile and sometimes not reliable. They are not isolated They are not very practical
- 17. Lost layer of Test pyramid Presentation Layer Test Service Layer Test Subcutaneous Test Persistence Layer Test
- 18. Layered testing
- 19. BONUS
- 20. Mocks overuse / pedantic unit test @Test public void testCreditCardIsCharged() { paymentProcessor = new PaymentProcessor(mockCreditCardServer); when(mockCreditCardServer.isServerAvailable()).thenReturn(true); when(mockCreditCardServer.beginTransaction()) .thenReturn(mockTransactionManager); when(mockTransactionManager.getTransaction()) .thenReturn(transaction); when(mockCreditCardServer.pay(transaction, creditCard, 500)) .thenReturn(mockPayment); when(mockPayment.isOverMaxBalance()).thenReturn(false); paymentProcessor .processPayment(creditCard, Money.ofMajor(CurrencyUnit.USD, 500)); verify(mockCreditCardServer).pay(transaction, creditCard, 500); }
- 21. Questions? Rodrigo di Lorenzo Lopes rdllopes@gmail.com