Test your tests with PIT framework
•Download as PPTX, PDF•
0 likes•107 views
This document discusses PIT, a tool for mutation testing Java code. PIT works by making small changes to the code called mutants, running existing tests against these mutants, and seeing if any tests fail. If a test fails on a mutant, it means that test is effective at finding that type of error. PIT can help evaluate test coverage and quality by exposing weaknesses. It is fast and can test hundreds of thousands of mutants in under a second. PIT can be used for personal code quality or integrated into build/CI pipelines. Alternatives to PIT include Jester and Jumble.
Report
Share
Report
Share
Recommended
Unit testing
The practical test pyramid. Material from https://martinfowler.com/articles/practical-test-pyramid.html
Unit testing patterns for concurrent code
Getting started with unit testing is not hard, the only problem is that most programs are more than a simple calculator with two parameters and a returns value that is easy to verify.
Writing unit tests for multi-threaded code is harder still.
Over the years I discovered useful patterns that helped me to test multi-threaded and asynchronous code and enabled the creation of deterministic, simple and robust unit tests.
Come learn how to test code that uses concurrency and parallelism – so that the excuses of not writing unit tests for such code would become as obsolete as a single core processors.
Java Testing With Spock - Ken Sipe (Trexin Consulting)
The Spock unit testing framework is on the verge of a 1.0 release and has already proven itself to be the next generation thinking on how to test Java production code. One of the many ever present challenges to testing code is the ability to Mock classes which has simplified by Spock from a very early release. Recently added to Spock is the notion of Stubs and Spies. This sessions is designed to demonstrate proper unit testing technique showing off these new features along with a number of advanced Spock features.
Debugging tricks you wish you knew - Tamir Dresher
Tamir Dresher presents debugging tricks and techniques for software developers. The presentation covers setting breakpoints, comparing objects while debugging, handling exceptions, debugging multithreaded applications, post-mortem debugging using dumps, and debugging LINQ queries. Attendees are encouraged to try the open source OzCode debugger, which provides additional features to aid the debugging process. Contact information is provided for any questions.
Best practices unit testing
The document provides best practices for writing unit tests, including mocking external services, writing focused tests for individual code units, avoiding unnecessary assertions, using annotations to test exceptions, and refactoring code if tests become too complex. Good practices like giving tests descriptive names and adding new tests for each found bug are also recommended. The document emphasizes that tests should serve as documentation and prevent regressions.
Smarter Testing With Spock
by Dmitry Voloshko
What we’ll talk about
Spock?!
State Based Testing
Data Driven Testing
Interaction Based Testing
Spock Extensions
More Cool Stuff
Stopping the Rot - Putting Legacy C++ Under Test
The document discusses introducing unit testing to legacy C++ code. It covers choosing a testing framework, writing initial tests and mocks, and various refactoring techniques like wrapping dependencies, extracting components, and adding non-intrusive C seams to facilitate testing. The goal is to incrementally make the code more testable while maintaining functionality through practices like test-driven development.
Spock Framework
Spock is a Groovy-based testing framework that provides features for writing tests in a clear, expressive, and highly readable manner. Some key features highlighted in the document include:
- Spock tests are structured into blocks like "given", "when", "then" that give tests a clear structure and meaning.
- Spock includes powerful and easy to read assertion methods as well as the ability to display diffs when expectations are not met.
- Spock supports mocking and stubbing of dependencies in a simple way.
- Data-driven testing is first-class in Spock through features like the "where" block that allows input test data to be specified in a table.
Recommended
Unit testing
The practical test pyramid. Material from https://martinfowler.com/articles/practical-test-pyramid.html
Unit testing patterns for concurrent code
Getting started with unit testing is not hard, the only problem is that most programs are more than a simple calculator with two parameters and a returns value that is easy to verify.
Writing unit tests for multi-threaded code is harder still.
Over the years I discovered useful patterns that helped me to test multi-threaded and asynchronous code and enabled the creation of deterministic, simple and robust unit tests.
Come learn how to test code that uses concurrency and parallelism – so that the excuses of not writing unit tests for such code would become as obsolete as a single core processors.
Java Testing With Spock - Ken Sipe (Trexin Consulting)
The Spock unit testing framework is on the verge of a 1.0 release and has already proven itself to be the next generation thinking on how to test Java production code. One of the many ever present challenges to testing code is the ability to Mock classes which has simplified by Spock from a very early release. Recently added to Spock is the notion of Stubs and Spies. This sessions is designed to demonstrate proper unit testing technique showing off these new features along with a number of advanced Spock features.
Debugging tricks you wish you knew - Tamir Dresher
Tamir Dresher presents debugging tricks and techniques for software developers. The presentation covers setting breakpoints, comparing objects while debugging, handling exceptions, debugging multithreaded applications, post-mortem debugging using dumps, and debugging LINQ queries. Attendees are encouraged to try the open source OzCode debugger, which provides additional features to aid the debugging process. Contact information is provided for any questions.
Best practices unit testing
The document provides best practices for writing unit tests, including mocking external services, writing focused tests for individual code units, avoiding unnecessary assertions, using annotations to test exceptions, and refactoring code if tests become too complex. Good practices like giving tests descriptive names and adding new tests for each found bug are also recommended. The document emphasizes that tests should serve as documentation and prevent regressions.
Smarter Testing With Spock
by Dmitry Voloshko
What we’ll talk about
Spock?!
State Based Testing
Data Driven Testing
Interaction Based Testing
Spock Extensions
More Cool Stuff
Stopping the Rot - Putting Legacy C++ Under Test
The document discusses introducing unit testing to legacy C++ code. It covers choosing a testing framework, writing initial tests and mocks, and various refactoring techniques like wrapping dependencies, extracting components, and adding non-intrusive C seams to facilitate testing. The goal is to incrementally make the code more testable while maintaining functionality through practices like test-driven development.
Spock Framework
Spock is a Groovy-based testing framework that provides features for writing tests in a clear, expressive, and highly readable manner. Some key features highlighted in the document include:
- Spock tests are structured into blocks like "given", "when", "then" that give tests a clear structure and meaning.
- Spock includes powerful and easy to read assertion methods as well as the ability to display diffs when expectations are not met.
- Spock supports mocking and stubbing of dependencies in a simple way.
- Data-driven testing is first-class in Spock through features like the "where" block that allows input test data to be specified in a table.
20111018 boost and gtest
This document provides an overview and summary of Boost and Google Test (gtest). It discusses key Boost libraries like smart pointers, assign, foreach, and bind. It explains how Boost handles memory management and containers. It also covers the basics of gtest like writing assertions and test fixtures. The document recommends gtest as a lightweight unit testing framework compared to Cppunit.
Soaoui
This document discusses various ways to use variables and methods in Groovy scripts in soapUI to interact with and retrieve information from the test runner context, test cases, test steps, message exchanges, and XML responses and requests. It provides examples of using the log, context, testRunner, and messageExchange variables, as well as methods for retrieving test suites, test cases, test steps, and property values. It also demonstrates how to read and write XML using the GroovyUtils class, convert between strings and integers, and read the raw request and response contents.
JavaScript Conditional Statements
This document provides an overview of conditional statements and loops in JavaScript. It discusses the if, else, else if, and switch conditional statements and their syntax and usage. It also covers the for, for/in, while, and do/while loops in JavaScript, explaining what each one is used for and including examples of their syntax. The goal of the lesson is for students to understand how to use conditional logic and loops to control program flow in JavaScript.
Using Rhino Mocks for Effective Unit Testing
This document discusses using Rhino Mocks, an isolation and mocking framework, for effective unit testing. It defines different types of test doubles like stubs and mocks, and their purposes. It provides examples of using Rhino Mocks to generate stubs and mocks, set expectations, and verify interactions for more complex unit tests when simple tests are not sufficient. Constraints for matching arguments and properties in expectations are also covered in detail.
Applying TDD to Legacy Code
This document provides rules for applying test-driven development (TDD) to legacy code. It discusses:
- Using a bottom-up (inside-out) approach rather than top-down when working with legacy code.
- Only testing the modified code, not writing tests for all use cases of legacy code.
- Testing requirements of new code rather than all behaviors and use cases.
- Injecting new testable code into legacy code without changing it.
- Breaking hidden dependencies to decrease coupling and increase cohesion.
The document provides examples of applying each rule through code snippets from a sample e-commerce application. It aims to help structure new code for testability while minimizing changes to
Testing
2005 talk on testing: I know your code doesn't work, because I know my own is broken. Covers CruiseControl & Apache Gump
TDD and the Legacy Code Black Hole
You’re finally doing TDD, but your past mistakes are catching up with you. No matter what you do, you can’t get rid of the gaping black holes caused by your legacy code.
In this presentation, we learn about the causes of legacy code and the reasons it is so difficult to work with. Then we discuss various techniques to test untestable code, revive and simplify incomprehensible code, redesign stable yet untested code, and repair that rift we created in the time-space continuum.
28csharp
This document summarizes key concepts about polymorphism in C#, including method overloading, method overriding, and the base and sealed keywords. It explains that polymorphism allows the same method name to have different implementations. Method overloading uses the same name but different parameters at compile-time, while method overriding uses the same name and signature but different implementations at runtime through inheritance. The base keyword accesses members of the parent class, and sealed prevents a class or method from being overridden or inherited.
Writing good unit test
Agenda:
1. Auto-Testing Overview
2. Unit Test Terminology( Fake/Spy/Stub/Mock )
3. Good Practice for Unit Test
Introduzione al TDD
This document provides an introduction to Test Driven Development (TDD) in Italian. It defines key TDD concepts like "test first" and automating tests. It then provides examples of using TDD to develop a parser for the "df" command output and features for an astrology horoscope application. The examples demonstrate the TDD process of writing a failing test, then code to pass the test, and refactoring. Rules for TDD like keeping tests passing and writing tests for all features are also outlined.
Testing in Craft CMS
This document summarizes a presentation about testing in Craft CMS. The presentation covers:
1) The types of tests including unit, functional, and acceptance tests and how they help projects.
2) How to set up and run Codeception tests in Craft including installing Codeception, setting up directories and files, and adding tests.
3) Tips for successful testing like using fixtures, offloading tests to a queue, and different types of tests like email, Twig, performance and accessibility testing.
Presentation_C++UnitTest
This document discusses using GoogleTest as a C++ unit testing framework. It provides an overview of GoogleTest features such as assertion-rich testing, test fixtures, test result reporting, and parameterized/data-driven tests. It also demonstrates how to set up a sample project in Visual Studio to write and run tests using GoogleTest, including features like type assertions, death tests, and test filtering.
Template Method Design Pattern
Template method design pattern is quite useful for framework designers as it provides a mechanism for users of framework to extend the framework.
TDD - test doubles
Test doubles like stubs and mocks are used to isolate parts of a system under test. Stubs simulate inputs to the system under test, helping to define the "given" part of a test. Mocks are used to verify outputs of the system under test, helping to define the "then" part of a test by setting expectations and verifying interactions. Examples show using stubs to simulate a grades repository input and using mocks to verify that a domotic system closes windows and doors when activating security. It is recommended to test features rather than classes in isolation and to avoid using test doubles for value objects or types not owned.
Into The Box 2018 | Assert control over your legacy applications
This document discusses how to add tests to legacy code using the TestBox testing framework for ColdFusion applications. It defines unit testing and different types of tests like unit, integration, and end-to-end tests. TestBox allows writing automated tests for ColdFusion code and isolating dependencies using test doubles. The document outlines best practices for test-driven development including writing tests before code, using life cycle methods, and refactoring code without changing external behavior. Implementing a testing framework like TestBox helps assert control over legacy applications by adding tests and the ability to refactor code safely.
C++ ala
Exceptions are runtime errors or unusual program conditions. Common exceptions include division by zero, out of bounds array access, and running out of memory. Exception handling in C++ uses try, throw, and catch keywords. The try block detects exceptions, throw throws the exception, and catch catches and handles the exception. Exceptions are objects that provide information about the error. Exceptions propagate from inner blocks or function calls to the nearest matching catch block.
Pyconie 2012
This document summarizes lessons learned from building MongoDB and MongoEngine. Some key lessons include: dive in and start contributing to open source projects to help them progress; metclasses are an important tool that allow ORM functionality to be added to classes; not all new ideas are good and it's important to avoid straying too far from existing patterns that users expect; tracking changes at a granular level allows partial updates but adds complexity. Overall it encourages contributors to learn why certain approaches were taken and focus on improving existing designs rather than introducing radical changes.
Java Unit Test - JUnit
Unit tests test individual methods, integration tests test interactions between components, functional tests verify outputs without checking internals, and end-to-end tests perform complex scenarios like payments. Acceptance tests replicate user behaviors across the entire application. Performance tests evaluate behavior under load. Smoke tests check proper functioning after deployment. Frameworks like JUnit, TestNG, Cucumber, and Mockito support different test types.
Exception Handling in object oriented programming using C++
This document discusses exception handling in C++. It introduces exception handling mechanisms like try-catch-throw, multiple catch, catch-all, and rethrowing exceptions. Try-catch-throw handles exceptions by using a try block to detect and throw exceptions, which are then caught and handled in a catch block. Multiple catch allows one try block to have multiple catch blocks to handle different exception types. Catch-all can catch all exception types with a generic catch. Rethrowing exceptions rethrows the current exception to an outer try-catch block.
Java2 days 2013-j-treg
Jtreg is a test framework that supports Java test cases in the form of Java programs with a main method, applets, or shell scripts. It supports TestNG annotations and properties files to define tests. Tests should throw an exception if they fail or return normally if they pass. Jtreg provides options to select tests, set JVM options, specify the JDK, run tests concurrently, and generate reports.
#codemotion2016: Everything you should know about testing to go with @pedro_g...
The document discusses various topics related to software testing including:
- The different types of tests based on scope such as unit tests, integration tests, and system tests.
- Dependency injection and how it improves testability.
- Test doubles like fakes, stubs, spies, and mocks.
- Strategies for testing including static evaluation, dynamic evaluation, white box testing, and black box testing techniques like equivalence partitioning.
- How to structure tests in an automated way using frameworks like xUnit and spec.
- Best practices for designing testable code.
TDD Training
Test-driven development (TDD) is a software development process that relies on the repetition of short development cycles called the TDD cycle. The TDD cycle involves first writing a test case that defines a desired improvement or new function, then producing code to pass that test and finally refactoring the new code to acceptable standards. The document discusses TDD training which includes topics like fixtures, assertion patterns, test quality and a case study. It motivates TDD by explaining how it helps build quality code, improves maintainability and meets client needs by focusing on internal and external quality. Key aspects of TDD like the AAA test format and strategies for selecting the next test are also covered. Finally, the document reviews evidence from case
More Related Content
What's hot
20111018 boost and gtest
This document provides an overview and summary of Boost and Google Test (gtest). It discusses key Boost libraries like smart pointers, assign, foreach, and bind. It explains how Boost handles memory management and containers. It also covers the basics of gtest like writing assertions and test fixtures. The document recommends gtest as a lightweight unit testing framework compared to Cppunit.
Soaoui
This document discusses various ways to use variables and methods in Groovy scripts in soapUI to interact with and retrieve information from the test runner context, test cases, test steps, message exchanges, and XML responses and requests. It provides examples of using the log, context, testRunner, and messageExchange variables, as well as methods for retrieving test suites, test cases, test steps, and property values. It also demonstrates how to read and write XML using the GroovyUtils class, convert between strings and integers, and read the raw request and response contents.
JavaScript Conditional Statements
This document provides an overview of conditional statements and loops in JavaScript. It discusses the if, else, else if, and switch conditional statements and their syntax and usage. It also covers the for, for/in, while, and do/while loops in JavaScript, explaining what each one is used for and including examples of their syntax. The goal of the lesson is for students to understand how to use conditional logic and loops to control program flow in JavaScript.
Using Rhino Mocks for Effective Unit Testing
This document discusses using Rhino Mocks, an isolation and mocking framework, for effective unit testing. It defines different types of test doubles like stubs and mocks, and their purposes. It provides examples of using Rhino Mocks to generate stubs and mocks, set expectations, and verify interactions for more complex unit tests when simple tests are not sufficient. Constraints for matching arguments and properties in expectations are also covered in detail.
Applying TDD to Legacy Code
This document provides rules for applying test-driven development (TDD) to legacy code. It discusses:
- Using a bottom-up (inside-out) approach rather than top-down when working with legacy code.
- Only testing the modified code, not writing tests for all use cases of legacy code.
- Testing requirements of new code rather than all behaviors and use cases.
- Injecting new testable code into legacy code without changing it.
- Breaking hidden dependencies to decrease coupling and increase cohesion.
The document provides examples of applying each rule through code snippets from a sample e-commerce application. It aims to help structure new code for testability while minimizing changes to
Testing
2005 talk on testing: I know your code doesn't work, because I know my own is broken. Covers CruiseControl & Apache Gump
TDD and the Legacy Code Black Hole
You’re finally doing TDD, but your past mistakes are catching up with you. No matter what you do, you can’t get rid of the gaping black holes caused by your legacy code.
In this presentation, we learn about the causes of legacy code and the reasons it is so difficult to work with. Then we discuss various techniques to test untestable code, revive and simplify incomprehensible code, redesign stable yet untested code, and repair that rift we created in the time-space continuum.
28csharp
This document summarizes key concepts about polymorphism in C#, including method overloading, method overriding, and the base and sealed keywords. It explains that polymorphism allows the same method name to have different implementations. Method overloading uses the same name but different parameters at compile-time, while method overriding uses the same name and signature but different implementations at runtime through inheritance. The base keyword accesses members of the parent class, and sealed prevents a class or method from being overridden or inherited.
Writing good unit test
Agenda:
1. Auto-Testing Overview
2. Unit Test Terminology( Fake/Spy/Stub/Mock )
3. Good Practice for Unit Test
Introduzione al TDD
This document provides an introduction to Test Driven Development (TDD) in Italian. It defines key TDD concepts like "test first" and automating tests. It then provides examples of using TDD to develop a parser for the "df" command output and features for an astrology horoscope application. The examples demonstrate the TDD process of writing a failing test, then code to pass the test, and refactoring. Rules for TDD like keeping tests passing and writing tests for all features are also outlined.
Testing in Craft CMS
This document summarizes a presentation about testing in Craft CMS. The presentation covers:
1) The types of tests including unit, functional, and acceptance tests and how they help projects.
2) How to set up and run Codeception tests in Craft including installing Codeception, setting up directories and files, and adding tests.
3) Tips for successful testing like using fixtures, offloading tests to a queue, and different types of tests like email, Twig, performance and accessibility testing.
Presentation_C++UnitTest
This document discusses using GoogleTest as a C++ unit testing framework. It provides an overview of GoogleTest features such as assertion-rich testing, test fixtures, test result reporting, and parameterized/data-driven tests. It also demonstrates how to set up a sample project in Visual Studio to write and run tests using GoogleTest, including features like type assertions, death tests, and test filtering.
Template Method Design Pattern
Template method design pattern is quite useful for framework designers as it provides a mechanism for users of framework to extend the framework.
TDD - test doubles
Test doubles like stubs and mocks are used to isolate parts of a system under test. Stubs simulate inputs to the system under test, helping to define the "given" part of a test. Mocks are used to verify outputs of the system under test, helping to define the "then" part of a test by setting expectations and verifying interactions. Examples show using stubs to simulate a grades repository input and using mocks to verify that a domotic system closes windows and doors when activating security. It is recommended to test features rather than classes in isolation and to avoid using test doubles for value objects or types not owned.
Into The Box 2018 | Assert control over your legacy applications
This document discusses how to add tests to legacy code using the TestBox testing framework for ColdFusion applications. It defines unit testing and different types of tests like unit, integration, and end-to-end tests. TestBox allows writing automated tests for ColdFusion code and isolating dependencies using test doubles. The document outlines best practices for test-driven development including writing tests before code, using life cycle methods, and refactoring code without changing external behavior. Implementing a testing framework like TestBox helps assert control over legacy applications by adding tests and the ability to refactor code safely.
C++ ala
Exceptions are runtime errors or unusual program conditions. Common exceptions include division by zero, out of bounds array access, and running out of memory. Exception handling in C++ uses try, throw, and catch keywords. The try block detects exceptions, throw throws the exception, and catch catches and handles the exception. Exceptions are objects that provide information about the error. Exceptions propagate from inner blocks or function calls to the nearest matching catch block.
Pyconie 2012
This document summarizes lessons learned from building MongoDB and MongoEngine. Some key lessons include: dive in and start contributing to open source projects to help them progress; metclasses are an important tool that allow ORM functionality to be added to classes; not all new ideas are good and it's important to avoid straying too far from existing patterns that users expect; tracking changes at a granular level allows partial updates but adds complexity. Overall it encourages contributors to learn why certain approaches were taken and focus on improving existing designs rather than introducing radical changes.
Java Unit Test - JUnit
Unit tests test individual methods, integration tests test interactions between components, functional tests verify outputs without checking internals, and end-to-end tests perform complex scenarios like payments. Acceptance tests replicate user behaviors across the entire application. Performance tests evaluate behavior under load. Smoke tests check proper functioning after deployment. Frameworks like JUnit, TestNG, Cucumber, and Mockito support different test types.
Exception Handling in object oriented programming using C++
This document discusses exception handling in C++. It introduces exception handling mechanisms like try-catch-throw, multiple catch, catch-all, and rethrowing exceptions. Try-catch-throw handles exceptions by using a try block to detect and throw exceptions, which are then caught and handled in a catch block. Multiple catch allows one try block to have multiple catch blocks to handle different exception types. Catch-all can catch all exception types with a generic catch. Rethrowing exceptions rethrows the current exception to an outer try-catch block.
Java2 days 2013-j-treg
Jtreg is a test framework that supports Java test cases in the form of Java programs with a main method, applets, or shell scripts. It supports TestNG annotations and properties files to define tests. Tests should throw an exception if they fail or return normally if they pass. Jtreg provides options to select tests, set JVM options, specify the JDK, run tests concurrently, and generate reports.
What's hot (20)
Into The Box 2018 | Assert control over your legacy applications
Into The Box 2018 | Assert control over your legacy applications
Exception Handling in object oriented programming using C++
Exception Handling in object oriented programming using C++
Similar to Test your tests with PIT framework
#codemotion2016: Everything you should know about testing to go with @pedro_g...
The document discusses various topics related to software testing including:
- The different types of tests based on scope such as unit tests, integration tests, and system tests.
- Dependency injection and how it improves testability.
- Test doubles like fakes, stubs, spies, and mocks.
- Strategies for testing including static evaluation, dynamic evaluation, white box testing, and black box testing techniques like equivalence partitioning.
- How to structure tests in an automated way using frameworks like xUnit and spec.
- Best practices for designing testable code.
TDD Training
Test-driven development (TDD) is a software development process that relies on the repetition of short development cycles called the TDD cycle. The TDD cycle involves first writing a test case that defines a desired improvement or new function, then producing code to pass that test and finally refactoring the new code to acceptable standards. The document discusses TDD training which includes topics like fixtures, assertion patterns, test quality and a case study. It motivates TDD by explaining how it helps build quality code, improves maintainability and meets client needs by focusing on internal and external quality. Key aspects of TDD like the AAA test format and strategies for selecting the next test are also covered. Finally, the document reviews evidence from case
Not your father's tests
Advanced testing patterns in Java (with a look at Scala).
Software design principles applied to testing.
How to deal with untestable code.
TDD step patterns
There are different patterns that can be followed when taking steps in test-driven development (TDD). Some key step patterns include:
1. Defining application programming interfaces (APIs) by creating tests that define how classes will interact without implementations.
2. Introducing functionality incrementally by adding tests that induce small changes to functionality.
3. Testing exceptions by adding scenarios that cause exceptions to be thrown and validating expected behavior.
4. Consolidating features by combining tests of different functionalities to ensure integrated behavior.
Unit testing - A&BP CC
This workshop is about testing the right way. Get a clear view on how to test your code in an efficient and useful way!
This first testing-related workshop is about all aspects of unit testing. Integration testing and TDD will have their own dedicated workshops.
Getting Started With Testing
This document provides an overview of testing concepts and best practices. It discusses different types of bugs, the benefits of writing unit tests, test types like unit tests and integration tests, testability factors, isolation techniques using test doubles, common mistakes to avoid, and Microsoft Fakes for improving testability. The key points covered are:
- The importance of writing tests to prevent bugs and allow safe refactoring.
- Techniques like dependency injection, interfaces, and seams to make code more testable and allow isolation using stubs, fakes, mocks, and shims.
- Common mistakes for test code like testing multiple features in one test, long test runs without maintenance, lack of negative testing, and unclear
Unit testing 101
This document provides an introduction to unit testing, including what it is, why it's important, and how to implement it. It defines a unit as a class or function, and says unit tests should test these individual components in isolation. Key reasons for unit testing include enabling refactoring, maintaining code, and testing functionality before bugs or features are introduced. The document outlines guidelines for writing unit tests, such as having one test per scenario/assertion, and explains how to isolate dependencies using techniques like dependency injection, mocks, and stubs. It also discusses tools for automating testing and measuring code coverage.
Test Driven
Want to know the case for Test-Driven Development? Want to know style tips and gotchas for Testing and TDD? Let Alex Chaffee, former Mad Scientist at Pivotal Labs, tell you everything you didn't know you didn't know about testing.
Some testing - Everything you should know about testing to go with @pedro_g_s...
I usually attend to several talks about testing. Everyone tells us how good, how important and valuable could be having a good test suite. But almost anybody tells us how hard is achieving this goal. With this talk, I wanted to provide an overview for people who is starting with software testing. Even for those who never tried it.
But this is not only an introduction. Though I start talking about the basics and principles and concepts, I also try to talk about my experience. What worked, where I failed and how I tried to solve the problems I found.
Just Do It! ColdBox Integration Testing
This document discusses integration testing of ColdBox applications using TestBox and MockBox. It defines integration testing as testing individual units combined as a group to expose faults in their interaction. The key benefits outlined are that integration tests allow testing of real use cases faster than end-to-end tests. The document recommends always integration testing as part of the development process and provides an overview of how to set up and run integration tests for a ColdBox application using TestBox.
DSR Testing (Part 1)
This document provides an overview of software testing concepts. It discusses different types of testing like unit testing, functional testing, error path testing, boundary value testing, and equivalence partitioning. It also covers test strategies like golden path testing, black box testing, and white box testing. The purpose of a tester is explained as quantifying risk to make decisions that improve confidence and quality.
Unit testing with PHPUnit - there's life outside of TDD
Basics of PHPUnit and why is it even more relevant in legacy code. Key points of the framework are explained, along with mocking objects, test organisation, creating documentations with tests and accessing non-public objects (where applicable).
Live version with additional notes available at: http://pawelmichalik.net/presentations/unit-testing-with-phpunit?showNotes=true
Prezentacja dostępna także w języku polskim: http://pawelmichalik.net/prezentacje/testy-jednostkowe-w-phpunit?showNotes=true
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
Roy Osherove provides training courses on topics like test-driven development (TDD), behavior-driven development (BDD), and consulting/coaching services. He discusses test reviews as an alternative to code reviews that can be quicker and help learning teams. The presentation focuses on creating tests that are trustworthy, maintainable, and readable through techniques like avoiding test logic, not repeating production logic, separating unit and integration tests, and using readable structures, naming, and avoiding magic values.
We Are All Testers Now: The Testing Pyramid and Front-End Development
The document provides an overview of test-driven development (TDD) principles and how to implement testing for front-end development. It discusses the benefits of TDD, such as avoiding bad designs and preventing regressions. It also addresses common challenges with TDD, like slowing initial velocity and ignored tests over time. The document then covers different levels of testing, including unit tests, integration tests, and functional/end-to-end tests using the testing pyramid as a framework. It provides examples of writing tests for pure and impure functions using the Jest testing framework. Finally, it discusses functional testing using Cucumber.js behavior-driven development.
Advances in Unit Testing: Theory and Practice
Here are the key steps to specify and test the IntSet class using Pex:
1. Define the IntSet class with the required methods like insert, member, remove.
2. Add the [PexClass] attribute to the class to enable Pex testing.
3. Add [PexMethod] attributes to the methods you want Pex to generate tests for, like insert and member.
4. Within the test methods, use PexAssume to specify preconditions and PexAssert to specify postconditions.
5. Run Pex by building the project. Pex will generate test inputs to cover different paths in the code and validate assumptions/assertions.
6. Ex
The relationship between test and production code quality (@ SIG)
The document discusses the relationship between test code and production code. It describes a study that analyzed code produced with and without test-driven development (TDD) and found no significant difference in class design quality. Interviews revealed that developer experience is more important than TDD alone. The document also discusses a tool called Metric Miner that facilitates mining software repositories to study patterns in test code and their implications for production code quality.
TDD CrashCourse Part5: Testing Techniques
The document discusses testing techniques and principles for writing tests. It advocates for tests that are FAST, ISOLATING, REPEATABLE, SELF-VALIDATING, and TIMELY (FIRST). It also discusses the Arrange-Act-Assert (AAA) structure for tests and how to achieve high code coverage while maintaining test quality. The document notes that while code coverage is a useful metric, it does not guarantee correctness on its own. It also covers the use of test doubles like stubs, spies, mocks and fakes to replace dependencies.
TDD reloaded - JUGTAA 24 Ottobre 2012
Seconda serata di introduzione al Test-Driven Development, tenuta in XPeppers a Trento il 24 Ottobre 2012.
Nelle slide c'è anche la descrizione del coding dojo sullo string calculator che abbiamo svolto assieme.
Testing And Mxunit In ColdFusion
MXUnit is a testing framework for ColdFusion that allows testing of CFC components. It is one tool in a tester's toolkit for test-driven development. MXUnit provides a framework for writing test cases with setup, teardown, and assertion methods. Tests can be run individually or as part of a test suite from a browser.
An Introduction to unit testing
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.
Similar to Test your tests with PIT framework (20)
#codemotion2016: Everything you should know about testing to go with @pedro_g...
#codemotion2016: Everything you should know about testing to go with @pedro_g...
Some testing - Everything you should know about testing to go with @pedro_g_s...
Some testing - Everything you should know about testing to go with @pedro_g_s...
Unit testing with PHPUnit - there's life outside of TDD
Unit testing with PHPUnit - there's life outside of TDD
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
We Are All Testers Now: The Testing Pyramid and Front-End Development
We Are All Testers Now: The Testing Pyramid and Front-End Development
The relationship between test and production code quality (@ SIG)
The relationship between test and production code quality (@ SIG)
Recently uploaded
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
UiPath Test Automation using UiPath Test Suite series, part 5
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Recently uploaded (20)
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Test your tests with PIT framework
- 1. TEST YOUR TESTS WITH PIT FRAMEWORK dspoljaric@croz.net @darko_spoljaric
- 2. Set up (given) Data, mocks, class under test, environment etc. Call method under test (when) Assert results (then)
- 4. public class SomeValidatorTest { @Test public void testValidateWithSuccesfullScenario() { } @Test public void testValidateWithAnotherSuccesfullScenario() { } @Test public void testValidateWithFailingScenario() { } }
- 5. COVERAGE – DOES IT COVER: All posible input variations? What the test returns? How you’ve written your flow control code? (ifs, switches, loops, exceptions, etc.) When you say your code is covered by tests you’re basically saying nothing of value.
- 7. TDD „Write the minimal amount of code to make the test pass” - yes, but how do you know you wrote the bare minimum? - One test per line? Per branch? Per catch block?
- 8. WELCOME PIT! Pit takes the class under test, makes multiple changes on it which result in many new classes. Then it runs existing tests on all of those new classes, to see if any of them fail. New class = Mutant Change = Mutation
- 9. If a test (suite) fails on changed code (mutant) then the test is well written. „the mutant is killed”
- 14. MUTANTS CAN Be killed by a test Survive tests Be uncovered by tests Cause infinite loops to appear thus leading to a timeout (think about for loops, iterators and MathMutator) Cause errors (pit tries to minimise number of such mutants)
- 15. HOW MANY MUTANTS ARE TIPICALY CREATED? Somewhere around the number of lines of code
- 16. HOW FAST IS IT? Bytecode manipulation = no compilation! (hundreds of thousands of mutants can be created in under a second!) Shorter tests run first Extremely paralelizable
- 18. WHERE AND WHEN TO USE IT? Personal hygiene? Build? (Should survived mutants cause a build to fail?)
- 19. TOOLS SUPPORT • Eclipse plugin • IDEA plugin • Maven plugin • Gradle plugin • Sonar plugin
- 20. ALTERNATIVES EXIST • Jester • Simple Jester • Jumble • µJava • javaLanche