Automated testing in Python and beyond
Download as ODP, PDF1 like1,722 views
The document discusses automated testing in Python and other languages. It covers unit testing, how unit tests work in Python using the unittest module, the benefits of testing like refactoring with confidence and faster debugging. It also briefly mentions test frameworks for other languages like Java, Perl, PHP and Erlang. The key themes are that testing finds bugs, helps refactor code safely, and that when frameworks have shortcomings the better approach is to help fix them rather than starting new ones.
1 of 20
Downloaded 36 times
Ad
Recommended
TDD in Python With Pytest
TDD in Python With PytestEddy Reyes This presentation walks the reader through implementing a simple web application and its tests using Python, Flask, and the Pytest testing framework. Emphasis is placed on following the process of test-driven development (TDD) in creating the application.
Python Testing Fundamentals
Python Testing Fundamentalscbcunc This document provides an overview of the Python unittest module for writing and running automated tests. It discusses how the unittest.TestCase class is used to define test classes with methods named "test_" that contain assertions. The unittest module then handles running the tests and provides features like test organization, discovery of test methods, and integration with other tools.
Testing in-python-and-pytest-framework
Testing in-python-and-pytest-frameworkArulalan T This document provides an introduction to unit testing in Python and the Pytest framework. It discusses writing unit test code using the unittest framework and Pytest, how to test functions and handle failures. It also covers features of Pytest like skipping and expected failures, fixture setup/teardown, and distributed testing using the xdist plugin.
Modern Python Testing
Modern Python TestingAlexander Loechel Modern Testing provides concise summaries of key points from the document in 3 sentences:
The document discusses modern testing practices and frameworks for Python projects, emphasizing the importance of writing tests to ensure high quality software and outlining different types of tests like unit, integration, and acceptance tests. It presents examples of using the unittest and pytest frameworks for writing tests in Python as well as the Robot Framework for acceptance testing. The document concludes by advocating for adopting best practices like using tox for local test invocation and continuous integration to enforce testing standards.
C++ Unit Test with Google Testing Framework
C++ Unit Test with Google Testing FrameworkHumberto Marchezi The slides describe basic features from google test framework and also describe some techniques to make C++ code more testable
Python unit testing
Python unit testingDarryl Sherman This document discusses unit testing in Python. It explains that unit tests should be written before code to automatically test inputs and outputs. The code is then written to pass the tests. Tests are implemented by creating test classes that inherit from unittest.TestCase and adding test methods with assert statements. The document provides an example test and steps for creating unit tests, including importing unittest and the code to test.
20111018 boost and gtest
20111018 boost and gtestWill Shen 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.
Unit Testing with Python
Unit Testing with PythonMicroPyramid . Introduction to basic unit testing in python.
Introduction to setUp() and tearDown() methods.
Doctests.
Google mock for dummies
Google mock for dummiesHarry Potter This document provides an overview of GoogleMock, a mocking framework for C++. It defines what a mock object is and why they are useful for testing. GoogleMock allows specifying expectations for mock method calls, including how many times a method will be called and what it will return. It provides matchers to check arguments and actions to define return values or behaviors. The document demonstrates how to write mock classes, set expectations, and use mocks in tests to verify code interactions and behavior.
Google C++ Testing Framework in Visual Studio 2008
Google C++ Testing Framework in Visual Studio 2008Andrea Francia The document summarizes how to set up and use the Google C++ Testing Framework (Google Test) for unit testing C++ code in Visual Studio 2008. It discusses why Google Test was selected over other testing frameworks, provides an overview of its features and how to set it up in a Visual Studio project. It also demonstrates defining tests with the TEST and ASSERT macros and different types of assertions and expectations that can be used within tests.
Software Engineering - RS3
Software Engineering - RS3AtakanAral This document provides an overview of test-driven development (TDD) techniques including unit testing with JUnit, behavior-driven development (BDD) with Cucumber, test automation, and using mock objects with Mockito. It defines TDD and its processes, describes tools like JUnit, Cucumber and Mockito, and provides references for further reading on testing practices.
Unit Test Your Database
Unit Test Your DatabaseDavid Wheeler Given that the database, as the canonical repository of data, is the most important part of many applications, why is it that we don't write database unit tests? This talk promotes the practice of implementing tests to directly test the schema, storage, and functionality of databases.
Test driven development and unit testing with examples in C++
Test driven development and unit testing with examples in C++Hong Le Van Test-driven development (TDD) relies on short development cycles of writing a failing test case, producing code to pass that test, and refactoring the code. Unit testing tests individual units of code by isolating each part and showing they work correctly. Boost.Test is a popular C++ unit testing framework that allows organizing tests into suites and fixtures, and provides assertions and output of results. A minimal Boost.Test example defines a test case using BOOST_AUTO_TEST_CASE that contains an assertion like BOOST_CHECK_EQUAL to test that 2+2 equals 4.
Cursus phpunit
Cursus phpunitNick Belhomme The document describes an introductory training course on PHPUnit testing. It discusses installing PHPUnit and getting started with writing tests. Specifically, it shows how to write a first test case to test a Game_Grid class by creating a GridTest.php file. It fails initially since the class doesn't exist yet. The test is then made to pass by creating the Grid class file. The document also discusses bootstrapping tests by creating a Bootstrap.php file to autoload classes so requires aren't needed in each test.
Stopping the Rot - Putting Legacy C++ Under Test
Stopping the Rot - Putting Legacy C++ Under TestSeb Rose 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.
Unit Testing RPG with JUnit
Unit Testing RPG with JUnitGreg.Helton This document discusses using JUnit to automate unit testing of RPG code on an IBM iSeries system. It provides an overview of the benefits of automated testing and outlines the steps to set up the infrastructure for testing, including creating Java and RPG modules, compiling the code, and running tests. Sample code is provided for a simple math module and test. The document recommends automating the testing process through a shell script to run compilation and tests.
Automated Unit Testing
Automated Unit TestingMike Lively This document provides an overview of automated unit testing in PHP. It discusses what unit testing is, why it is important, what should be tested, when to test, and how to set up and run tests using PHPUnit. Key points include:
- Unit testing validates individual units of source code. Each test should test a single function or class.
- Tests should be run early and often to catch bugs early in development.
- PHPUnit is a popular PHP testing framework that allows creating and running automated tests. It provides assertions, fixtures, and other features to test code.
- Tests can be organized into test suites and run via the command line or configured via an XML file. Groups allow filtering tests to
Unit testing legacy code
Unit testing legacy codeLars Thorup Unit testing and test-driven development are practices that makes it easy and efficient to create well-structured and well-working code. However, many software projects didn't create unit tests from the beginning.
In this presentation I will show a test automation strategy that works well for legacy code, and how to implement such a strategy on a project. The strategy focuses on characterization tests and refactoring, and the slides contain a detailed example of how to carry through a major refactoring in many tiny steps
Presentation_C++UnitTest
Presentation_C++UnitTestRaihan Masud 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.
TDD in Go with Ginkgo and Gomega
TDD in Go with Ginkgo and GomegaEddy Reyes An overview of TDD concepts, and an exploration of these concepts in Go using the Ginkgo and Gomega libraries.
Clean Unit Test Patterns
Clean Unit Test PatternsFrank Appel Slides of my talk at GDG DevFestKarlsruhe 2014 about the fundamentals of how to write clean unit tests.
Refactoring legacy code driven by tests - ENG
Refactoring legacy code driven by tests - ENGLuca Minudel re you working on code poorly designed or on legacy code that’s hard to test? And you cannot refactor it because there are no tests?
During this Coding Dojo you’ll be assigned a coding challenge in Java, C#, Ruby, JavaScript or Python. You will face the challenge of improving the design and refactoring existing code in order to make it testable and to write unit tests.
We will discuss SOLID principles, the relation between design and TDD, and how this applies to your solution.
Reading list:
Growing Object-Oriented Software, Guided by Tests; Steve Freeman, Nat Pryce
Test Driven Development: By Example; Kent Beck
Working Effectively with Legacy; Michael Feathers
Agile Software Development, Principles, Patterns, and Practices; Robert C. Martin (C++, Java)
Agile Principles, Patterns, and Practices in C#; Robert C. Martin (C#)
RPG Program for Unit Testing RPG 
RPG Program for Unit Testing RPG Greg.Helton This document discusses unit testing ILE procedures in IBM i. It introduces unit testing as a way to identify bugs early and test code as it is written. It outlines how to create a test script in RPG that calls the procedures being tested and produces a report of the inputs, expected outputs, and actual results. The document provides terminology for different types of testing and guidelines for compiling test scripts separately from production code. It emphasizes that unit testing should be integrated into the development process.
Unit testing, principles
Unit testing, principlesRenato Primavera Unit testing tests individual units of source code to determine if they are fit for use. It is different from integration testing, which combines modules, and validation testing, which checks that a system meets specifications. The goal of unit testing is to isolate and test each part of a program to show that individual parts are correct. Unit testing provides benefits such as finding problems early, facilitating automated testing and change, and improving software quality. Guidelines for effective unit testing include knowing the objective of each test, making tests self-sufficient, ensuring tests are deterministic, following naming conventions, duplicating code for readability, testing results not implementation, and using isolation frameworks.
How and what to unit test
How and what to unit testEugenio Lentini A brief introduction about the art of unit test, how to test a class, mock a collaborator and use a fake database. TDD is introduced. Code for exercises is available on github along with a detailed explanation. Examples and exercises are written in Java.
Writing good unit test
Writing good unit testLucy Lu Agenda:
1. Auto-Testing Overview
2. Unit Test Terminology( Fake/Spy/Stub/Mock )
3. Good Practice for Unit Test
Interpreter RPG to Java
Interpreter RPG to Javafarerobe The document discusses migrating RPG code from an existing platform called JeniuX to Java. It will involve copying the structure and functions from the RPG code to Java classes and methods. The migration process will include initial parsing and interpretation of the RPG code, followed by conversion to pseudo code and then Java code. Graphics will be excluded from the migration. An initial test of the process achieved a 95.2% conversion of JeniuX files to Java and 83% for backend files. Next steps include improving the pseudo code generation and developing a graphical analysis tool.
Testacular
TestacularJames Ford Unit testing JavaScript code allows developers to make changes quickly and confidently by verifying code works as expected through automated tests. Testacular is a Node.js-based testing framework that runs tests using various browsers and frameworks like Jasmine. It provides features like live reloading, code coverage reports, and integration with continuous integration servers. Writing tests in Jasmine involves describing test suites and individual specs using expectations and matchers to validate code behavior.
Why Unit Testingl
Why Unit Testinglpriya_trivedi The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Why Unit Testingl
Why Unit Testinglpriya_trivedi The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Ad
More Related Content
What's hot (19)
Google mock for dummies
Google mock for dummiesHarry Potter This document provides an overview of GoogleMock, a mocking framework for C++. It defines what a mock object is and why they are useful for testing. GoogleMock allows specifying expectations for mock method calls, including how many times a method will be called and what it will return. It provides matchers to check arguments and actions to define return values or behaviors. The document demonstrates how to write mock classes, set expectations, and use mocks in tests to verify code interactions and behavior.
Google C++ Testing Framework in Visual Studio 2008
Google C++ Testing Framework in Visual Studio 2008Andrea Francia The document summarizes how to set up and use the Google C++ Testing Framework (Google Test) for unit testing C++ code in Visual Studio 2008. It discusses why Google Test was selected over other testing frameworks, provides an overview of its features and how to set it up in a Visual Studio project. It also demonstrates defining tests with the TEST and ASSERT macros and different types of assertions and expectations that can be used within tests.
Software Engineering - RS3
Software Engineering - RS3AtakanAral This document provides an overview of test-driven development (TDD) techniques including unit testing with JUnit, behavior-driven development (BDD) with Cucumber, test automation, and using mock objects with Mockito. It defines TDD and its processes, describes tools like JUnit, Cucumber and Mockito, and provides references for further reading on testing practices.
Unit Test Your Database
Unit Test Your DatabaseDavid Wheeler Given that the database, as the canonical repository of data, is the most important part of many applications, why is it that we don't write database unit tests? This talk promotes the practice of implementing tests to directly test the schema, storage, and functionality of databases.
Test driven development and unit testing with examples in C++
Test driven development and unit testing with examples in C++Hong Le Van Test-driven development (TDD) relies on short development cycles of writing a failing test case, producing code to pass that test, and refactoring the code. Unit testing tests individual units of code by isolating each part and showing they work correctly. Boost.Test is a popular C++ unit testing framework that allows organizing tests into suites and fixtures, and provides assertions and output of results. A minimal Boost.Test example defines a test case using BOOST_AUTO_TEST_CASE that contains an assertion like BOOST_CHECK_EQUAL to test that 2+2 equals 4.
Cursus phpunit
Cursus phpunitNick Belhomme The document describes an introductory training course on PHPUnit testing. It discusses installing PHPUnit and getting started with writing tests. Specifically, it shows how to write a first test case to test a Game_Grid class by creating a GridTest.php file. It fails initially since the class doesn't exist yet. The test is then made to pass by creating the Grid class file. The document also discusses bootstrapping tests by creating a Bootstrap.php file to autoload classes so requires aren't needed in each test.
Stopping the Rot - Putting Legacy C++ Under Test
Stopping the Rot - Putting Legacy C++ Under TestSeb Rose 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.
Unit Testing RPG with JUnit
Unit Testing RPG with JUnitGreg.Helton This document discusses using JUnit to automate unit testing of RPG code on an IBM iSeries system. It provides an overview of the benefits of automated testing and outlines the steps to set up the infrastructure for testing, including creating Java and RPG modules, compiling the code, and running tests. Sample code is provided for a simple math module and test. The document recommends automating the testing process through a shell script to run compilation and tests.
Automated Unit Testing
Automated Unit TestingMike Lively This document provides an overview of automated unit testing in PHP. It discusses what unit testing is, why it is important, what should be tested, when to test, and how to set up and run tests using PHPUnit. Key points include:
- Unit testing validates individual units of source code. Each test should test a single function or class.
- Tests should be run early and often to catch bugs early in development.
- PHPUnit is a popular PHP testing framework that allows creating and running automated tests. It provides assertions, fixtures, and other features to test code.
- Tests can be organized into test suites and run via the command line or configured via an XML file. Groups allow filtering tests to
Unit testing legacy code
Unit testing legacy codeLars Thorup Unit testing and test-driven development are practices that makes it easy and efficient to create well-structured and well-working code. However, many software projects didn't create unit tests from the beginning.
In this presentation I will show a test automation strategy that works well for legacy code, and how to implement such a strategy on a project. The strategy focuses on characterization tests and refactoring, and the slides contain a detailed example of how to carry through a major refactoring in many tiny steps
Presentation_C++UnitTest
Presentation_C++UnitTestRaihan Masud 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.
TDD in Go with Ginkgo and Gomega
TDD in Go with Ginkgo and GomegaEddy Reyes An overview of TDD concepts, and an exploration of these concepts in Go using the Ginkgo and Gomega libraries.
Clean Unit Test Patterns
Clean Unit Test PatternsFrank Appel Slides of my talk at GDG DevFestKarlsruhe 2014 about the fundamentals of how to write clean unit tests.
Refactoring legacy code driven by tests - ENG
Refactoring legacy code driven by tests - ENGLuca Minudel re you working on code poorly designed or on legacy code that’s hard to test? And you cannot refactor it because there are no tests?
During this Coding Dojo you’ll be assigned a coding challenge in Java, C#, Ruby, JavaScript or Python. You will face the challenge of improving the design and refactoring existing code in order to make it testable and to write unit tests.
We will discuss SOLID principles, the relation between design and TDD, and how this applies to your solution.
Reading list:
Growing Object-Oriented Software, Guided by Tests; Steve Freeman, Nat Pryce
Test Driven Development: By Example; Kent Beck
Working Effectively with Legacy; Michael Feathers
Agile Software Development, Principles, Patterns, and Practices; Robert C. Martin (C++, Java)
Agile Principles, Patterns, and Practices in C#; Robert C. Martin (C#)
RPG Program for Unit Testing RPG
RPG Program for Unit Testing RPG Greg.Helton This document discusses unit testing ILE procedures in IBM i. It introduces unit testing as a way to identify bugs early and test code as it is written. It outlines how to create a test script in RPG that calls the procedures being tested and produces a report of the inputs, expected outputs, and actual results. The document provides terminology for different types of testing and guidelines for compiling test scripts separately from production code. It emphasizes that unit testing should be integrated into the development process.
Unit testing, principles
Unit testing, principlesRenato Primavera Unit testing tests individual units of source code to determine if they are fit for use. It is different from integration testing, which combines modules, and validation testing, which checks that a system meets specifications. The goal of unit testing is to isolate and test each part of a program to show that individual parts are correct. Unit testing provides benefits such as finding problems early, facilitating automated testing and change, and improving software quality. Guidelines for effective unit testing include knowing the objective of each test, making tests self-sufficient, ensuring tests are deterministic, following naming conventions, duplicating code for readability, testing results not implementation, and using isolation frameworks.
How and what to unit test
How and what to unit testEugenio Lentini A brief introduction about the art of unit test, how to test a class, mock a collaborator and use a fake database. TDD is introduced. Code for exercises is available on github along with a detailed explanation. Examples and exercises are written in Java.
Writing good unit test
Writing good unit testLucy Lu Agenda:
1. Auto-Testing Overview
2. Unit Test Terminology( Fake/Spy/Stub/Mock )
3. Good Practice for Unit Test
Interpreter RPG to Java
Interpreter RPG to Javafarerobe The document discusses migrating RPG code from an existing platform called JeniuX to Java. It will involve copying the structure and functions from the RPG code to Java classes and methods. The migration process will include initial parsing and interpretation of the RPG code, followed by conversion to pseudo code and then Java code. Graphics will be excluded from the migration. An initial test of the process achieved a 95.2% conversion of JeniuX files to Java and 83% for backend files. Next steps include improving the pseudo code generation and developing a graphical analysis tool.
Similar to Automated testing in Python and beyond (20)
Testacular
TestacularJames Ford Unit testing JavaScript code allows developers to make changes quickly and confidently by verifying code works as expected through automated tests. Testacular is a Node.js-based testing framework that runs tests using various browsers and frameworks like Jasmine. It provides features like live reloading, code coverage reports, and integration with continuous integration servers. Writing tests in Jasmine involves describing test suites and individual specs using expectations and matchers to validate code behavior.
Why Unit Testingl
Why Unit Testinglpriya_trivedi The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Why Unit Testingl
Why Unit Testinglpriya_trivedi The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Why unit testingl
Why unit testinglPriya Sharma The document discusses unit testing and provides guidance on effective unit testing practices. It defines key terms like error, defect, and failure. It outlines the benefits of unit testing like finding defects earlier and maintaining stable code. It discusses naming conventions and frameworks for unit tests. It provides examples of different types of unit tests and guidelines for writing good unit tests that are independent, fast, and test all functionality. The document emphasizes testing boundary conditions and errors as well as documenting test cases.
Testing smells
Testing smellsSidu Ponnappa The document discusses unit testing anti-patterns. It describes implementation anti-patterns like long tests with many assertions, long test files, tests with complex logic, slow tests, and tests that cannot fail. It also describes workflow anti-patterns like writing tests last, only testing for regression, testing elsewhere than in unit tests, only running tests from the command line, and not using continuous integration. It suggests approaches like writing independent tests, avoiding redundant tests, and testing frequently to avoid these anti-patterns.
I Smell A RAT- Rapid Application Testing
I Smell A RAT- Rapid Application TestingPeter Presnell This document discusses various techniques for rapid application testing (RAT) such as unit testing, integration testing, smoke testing, system testing, regression testing, performance testing, and test-driven development. It emphasizes automating test plans and test execution to allow tests to be run multiple times for little additional cost. The goal of testing is to balance cost and risk by reusing automated tests that are fast and good predictors of issues while throwing more tests at critical areas.
Unit Testing in iOS
Unit Testing in iOSLong Weekend LLC The document discusses unit testing frameworks for Objective-C and iOS development. It recommends the OCUnit framework for new Xcode projects with few test cases, and the GHUnit framework for projects needing more advanced testing capabilities. It provides an example of how to set up and write a basic unit test using the OCUnit framework.
TDD Best Practices
TDD Best PracticesAttila Bertók Ever tried doing Test First Test Driven Development? Ever failed? TDD is not easy to get right. Here's some practical advice on doing BDD and TDD correctly. This presentation attempts to explain to you why, what, and how you should test, tell you about the FIRST principles of tests, the connections of unit testing and the SOLID principles, writing testable code, test doubles, the AAA of unit testing, and some practical ideas about structuring tests.
Open source bridge testing antipatterns presentation
Open source bridge testing antipatterns presentationmmrobins These are the slides for the presentation I gave on antipatterns used in testing. This was at Open Source Bridge in June of 2011.
Test driven development - JUnit basics and best practices
Test driven development - JUnit basics and best practicesNarendra Pathai A presentation covering all the basics of Software Unit testing using JUnit framework. A lot of best practices, myths misconceptions are covered. Naming conventions for test methods and fundamental requirements for doing sustainable Junit testing.
Hack@macs 2014 test driven development & pair programing
Hack@macs 2014 test driven development & pair programingunihack გიორგი მამალაძე - Test Driven Development & Pair Programming
video: https://www.youtube.com/watch?v=yGg97JeyxWE
Unit Testing
Unit TestingAnuj Arora The document discusses unit testing and provides guidance on how to effectively implement unit testing. It defines unit testing as testing individual units or components of software code to verify they are functioning as intended. The document outlines best practices for unit testing such as writing test cases that cover valid, invalid, and boundary conditions. It also recommends testing frameworks like JUnit that can automate running test cases. Overall, the document advocates for developing a rigorous unit testing strategy and practicing habits like writing tests first and continuously running tests to improve code quality.
An Introduction to Test Driven Development 
An Introduction to Test Driven Development CodeOps Technologies LLP This document provides an overview of test-driven development (TDD). It defines TDD as a technique for building software where tests are written before code to guide development. The key aspects of TDD covered are:
- Writing tests first before code, which helps improve design and ensures tests are written.
- The TDD mantra of Red-Green-Refactor, where tests initially fail (Red), code is written to pass tests (Green), then code is refactored to improve design.
- An example case study of a large Java project developed using TDD that has over 20,000 lines of unit tests providing over 90% test coverage.
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flex
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flexmichael.labriola This document discusses automated testing in Flex. It begins by explaining why automated testing is important, such as reducing costs from software errors and allowing developers to change code without fear of breaking other parts of the project. It then covers topics like writing unit tests, using theories and data points to test over multiple values, and writing integration tests. The document emphasizes that writing testable code is key, and provides some principles for doing so, such as separating construction from application logic and using interfaces. It also discusses using fakes, stubs and mocks to isolate units for testing.
Test Driven
Test DrivenAlex Chaffee 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.
Google test training
Google test trainingThierry Gayet The document discusses Google Test, an open source unit testing framework for C++ that can also be used for testing C code, providing an overview of its features and how to implement unit tests using common patterns like test fixtures, assertions, and death tests to validate expected failures. It also covers best practices for writing effective unit tests, including keeping tests independent, focused, and fast-running.
Win at life with unit testing
Win at life with unit testingmarkstory This document discusses the benefits of unit testing and how to implement it. Some key points covered include:
- Unit testing helps ensure code works as intended, finds problems earlier, and increases developer confidence. It is especially useful for code involving money, code that has broken before, or code that is tedious to test manually.
- There are two main types of tests - unit tests that isolate small parts of an application and functional tests that ensure components work together. Mock objects are important for writing isolated unit tests.
- Benefits of testing include finding problems earlier, tests can be automated, and it ensures requirements are met. Challenges include the time needed to write tests initially.
- Continuous integration servers
SELJE_Database_Unit_Testing_Slides.pdf
SELJE_Database_Unit_Testing_Slides.pdfEric Selje This document discusses database unit testing fundamentals. It defines unit testing as code that exercises specific portions of code to return a pass/fail result. The goals of unit testing are to catch mistakes early, ensure code works as expected, and maintain tight code. The document reviews how to unit test databases, using tSQLt and SQL Test frameworks. It provides examples of unit testing stored procedures, functions, views and constraints. Overall, the document promotes unit testing databases to write testable code and help prevent errors.
TDD - Test Driven Dvelopment | Test First Design
TDD - Test Driven Dvelopment | Test First DesignQuang Nguyễn Bá Test Driven Development (TDD) is a software development process that relies on the repetition of short development cycles called "red-green-refactor" cycles. Each cycle begins with writing an automated test that defines a new function or improves an existing function. The test is then run to verify it fails ("red"). Code is then written to implement the new function or change ("green"). Finally, code is refactored to improve design and readability without changing functionality. TDD results in code that is well-tested, loosely coupled, and easy to maintain or modify. Popular TDD tools include JUnit, NUnit, and PHPUnit.
Power Of Zero
Power Of ZeroAndrew Forward A talk given at ElixirConf2017.
Automation is hard, but the benefits can be phenomenal. This can be especially challenging when working on your Elixir side project, as you want to see results quickly, so maybe a zero-click deploy and continuous delivery are not on your mind.
In this talk, I will help show you that even on a budget, even on a team of one you can streamline your software development to achieve some lofty goals including
Ad
More from dn (8)
Code quality; patch quality
Code quality; patch qualitydn Code quality; patch quality, Malcolm Tredinnick. Python user for 13 years. Linux user for even longer. Malcolm has worked with a wide variety of systems from banking and stock exchange interfaces, to multi-thousand server database-backed websites. These days, Malcolm's primary open source contributions are as a core developer for Django and advocate for Python.
All Open Source projects welcome patches from people willing to help fix bugs or implement feature requests. That's why we launch the source code into the wilds in the first place. If you are wanting to contribute, however, the process can seem a bit daunting, particularly when you are first starting out. Am I doing it properly? What will happen if I do it wrong? How can I do the best thing possible from the start? These are all typical worries. I've had them, others have had them and you're not alone if they cross your mind. In this talk, we will go over a few basic ideas for producing patch submissions that make things as easy as possible both for yourself and the code maintainers. How to help the maintainers help you. Malcolm has been a core maintainer for Django for over give years and has seen a few good and bad contributions in his time. These are the harmless and useful lessons that can be drawn from that experience.
How does this code work?
How does this code work?dn How does this code work? Jeff Rush, past Python Advocacy Coordinator, organizer of the Dallas/Ft. Worth Pythoneers usergroup as well as conference co-chair of PyCon 2006 and 2007 held in Dallas. He has been providing Python and embedded Linux/robotics consulting service since 1996, ported Python to OS/2 and created the initial RPMs for Zope used by Red Hat. He also serves as a director of the Python Software Foundation and the Zope Foundation.
Python worst practices
Python worst practicesdn Python Worst Practices, Daniel Greenfeld, co-founder of Development at Cartwheel Web, often consults for Revsys.com, and learned Python while at NASA. Working with Steve Holden, chairman of the Python Software Foundation he helps author a series of classes on Python 3 for the O'Reilly School of Technology. He is a co-creator of Django Packages, Packaginator, author of django-uni-form, has done a lot of work in the field of usability, and does his best to support diversity in the tech community.
Struggling to find an open source business model
Struggling to find an open source business modeldn The document discusses the challenges faced by the creator of an open source software called SOFA in developing a sustainable business model. After two years of trying various monetization strategies, total income was only $100. The creator is now reluctantly considering adopting a "pro version/open core" model where additional paid features would be offered while keeping the core open source. This approach is controversial as some feel it would make free users "second class citizens". The creator is seeking feedback on whether there is a more realistic alternative given the need to support himself and family.
Testing in those hard to reach places
Testing in those hard to reach placesdn This document discusses techniques for testing software in difficult environments, including:
1. Refactoring code into testable components and using mocking to replace dependencies that are hard to control, like network connections.
2. Setting up test databases in memory to isolate tests from the production database.
3. Using mocking frameworks to create fake objects, classes, and modules that replace real dependencies and allow tests to run independently.
4. An example shows mocking smtplib to test email sending without actually sending emails.
Behaviour Driven Development and Thinking About Testing
Behaviour Driven Development and Thinking About Testingdn KiwiPyCon2011, Wellington, Saturday, Track 2, Behaviour Driven Development and Thinking About Testing by Malcolm Tredinnick
Patterns in Python
Patterns in Pythondn This document discusses various design patterns in Python and how they compare to their implementations in other languages like C++. It provides examples of how common patterns from the Gang of Four book like Singleton, Observer, Strategy, and Decorator are simplified or invisible in Python due to features like first-class functions and duck typing. The document aims to illustrate Pythonic ways to implement these patterns without unnecessary complexity.
Spotlight on Python
Spotlight on Pythondn Kiwi PyCon 2011, Wellington, Spotlight on Python by Nick Cave-Lynch, Spotlight on Python.
Covers development and use of a Python-powered system designed for lighting bands in small venues. Covers (among other things): the problems of lighting bands; the development process; the results; lessons learned.
Ad
Recently uploaded (20)
Procurement Insights Cost To Value Guide.pptx
Procurement Insights Cost To Value Guide.pptxJon Hansen Procurement Insights integrated Historic Procurement Industry Archives, serves as a powerful complement — not a competitor — to other procurement industry firms. It fills critical gaps in depth, agility, and contextual insight that most traditional analyst and association models overlook.
Learn more about this value- driven proprietary service offering here.
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep Dive
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB Want to learn practical tips for designing systems that can scale efficiently without compromising speed?
Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development.
As you explore key principles of designing low-latency systems with Rust, you will learn how to:
- Create and compile a real-world app with Rust
- Connect the application to ScyllaDB (NoSQL data store)
- Negotiate tradeoffs related to data modeling and querying
- Manage and monitor the database for consistently low latencies
Special Meetup Edition - TDX Bengaluru Meetup #52.pptx
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55 We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...
AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025
https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/
Is AI just another technology, or does it fundamentally change the way we live and think?
Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater.
At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts.
At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.
Quantum Computing Quick Research Guide by Arthur Morgan
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager API
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts!
📕 Agenda
Welcome & Introductions
Orchestrator API Overview
Exploring the Swagger Interface
Test Manager API Highlights
Streamlining Automation & Testing with APIs (Demo)
Q&A and Open Discussion
Perfect for developers, testers, and automation enthusiasts!
👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/
This session streamed live on April 29, 2025, 18:00 CET.
Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.
Build Your Own Copilot & Agents For Devs
Build Your Own Copilot & Agents For DevsBrian McKeiver May 2nd, 2025 talk at StirTrek 2025 Conference.
Cyber Awareness overview for 2025 month of security
Cyber Awareness overview for 2025 month of securityriccardosl1 Cyber awareness training educates employees on risk associated with internet and malicious emails
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
Build 3D Animated Safety Induction - Tech EHS
Build 3D Animated Safety Induction - Tech EHSTECH EHS Solution Train Smarter, Not Harder – Let 3D Animation Lead the Way!
Discover how 3D animation makes inductions more engaging, effective, and cost-efficient.
Check out the slides to see how you can transform your safety training process!
Slide 1: Why 3D animation changes the game
Slide 2: Site-specific induction isn’t optional—it’s essential
Slide 3: Visitors are most at risk. Keep them safe
Slide 4: Videos beat text—especially when safety is on the line
Slide 5: TechEHS makes safety engaging and consistent
Slide 6: Better retention, lower costs, safer sites
Slide 7: Ready to elevate your induction process?
Can an animated video make a difference to your site's safety? Let's talk.
How analogue intelligence complements AI
How analogue intelligence complements AIPaul Rowe
Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results.
News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?
Rusty Waters: Elevating Lakehouses Beyond Spark
Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1 Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungen
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
Generative Artificial Intelligence (GenAI) in Business
Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma My talk for the Indian School of Business (ISB) Emerging Leaders Program Cohort 9. In this talk, I discussed key issues around adoption of GenAI in business - benefits, opportunities and limitations. I also discussed how my research on Theory of Cognitive Chasms helps address some of these issues
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Andrew Marnell: Transforming Business Strategy Through Data-Driven Insights
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
Automated testing in Python and beyond
- 1. Automated testing in Python and beyond Brenda Wallace Production Engineer, Weta Digital
- 2. Unit Tests Unit Testing is testing of individual program "units" in relative isolation
- 3. Wah? What they are
- 4. Input -> expected output
- 6. Glorified If/Else statements if (stuff happens as expected): OK! else: Fail.
- 7. Python unit tests class testMyCode(unittest.TestCase): def test_Stuff(self): a = MyDataProcessingThing(5) self.assertEqual(a.blah, 9)
- 8. Python Pass, fail, coverage
- 9. Super Powers Massive refactors, and know they worked
- 10. Wanna try something wickedly clever? Do code change quickly
- 11. instantly see if it works for all 1,000 of your use cases
- 12. Confidence Debugging is fast
- 14. Blame.
- 15. You look GOOD.
- 17. Logging capture
- 18. STDOUT capture
- 21. Where ? Check them into a folder called tests
- 23. The Theme There were shortcomings in the other frame work so instead of helping fixing those, we started a new one.
- 24. Java JUnit What everyone uses JTiger There were shortcomings, so instead of fixing those, we started a new one. TestNG Our new one fixes different short comings Looks like python, but with less words
- 25. But life is too short
- 26. Perl Perl Unit
- 27. +60 more on cpan
- 28. Pod::Coverage
- 29. PHP PhpUnit
- 30. SimpleTest Web
- 31. Erlang EUnit
- 32. Best intro to testing ever.
- 33. Write tests Write tests before you write code
- 35. On cron e.g. every hour
- 36. On commit, poll git for changes
- 37. Email everyone when it breaks
- 38. Email only the person who broke it.
- 39. Thank You