Generatingcharacterizationtestsforlegacycode
•Download as PPTX, PDF•
2 likes•302 views
The document discusses generating characterization tests for legacy code without existing tests. It recommends creating characterization tests that capture the actual behavior of code by using sample inputs and asserting expected outputs. This helps protect legacy code from unintended changes by acting as a change detector. An example test is shown that characterizes the behavior of a CalcUtil method by passing sample inputs and asserting the expected output.
Report
Share
Report
Share
Recommended
Unit testing
This is for whom who want to start testing. How to do mocking in testing. Link for the example https://github.com/Vendetta30/GrailsUnitTesting.
Presentation1 computer shaan
The document describes a Java program to calculate parcel shipping charges based on weight. It begins with an initial charge of Rs. 15 for the first 1KG. Any additional weight is charged Rs. 8 for every 500g or fraction thereof. The program takes a weight in KGs as input, calculates the remaining weight after deducting 1KG, determines the charge for full 500g increments and any fractional part, and outputs the total charge.
Fl0ppy - CODEGATE 2016 CTF Preliminary
This document analyzes an exploit for a pwnable challenge called "Fl0ppy" that involves manipulating floppy disk structures. It finds that by overwriting the "data" or "description" fields of the floppy disk structures, a buffer overflow can be achieved to leak memory addresses and eventually execute the "/bin/sh" command by overwriting the return address. The key steps are leaking addresses, identifying the libc version, calculating the address of the "system" function, and using a buffer overflow to redirect execution to "system('/bin/sh')".
Python unittest
The document discusses Python's unittest framework for unit testing. It covers key concepts like test fixtures, test cases, test suites, and test runners. It also provides examples of setting up test fixtures by subclassing TestCase and initializing instance variables in the setUp method. The document recommends organizing tests into groups and using lifecycle methods like setUp, tearDown, setUpClass, and tearDownClass.
Python-nose: A unittest-based testing framework for Python that makes writing...
Nose is a Python testing framework that extends the built-in unittest framework. It makes writing and running tests easier by automating test discovery and running. Nose can be installed via pip and used by running nosetests on test files. Tests are written as unittest classes and methods. Nose supports configuration files, running tests in parallel, and integration with IDEs like Eclipse to automatically run tests on file changes.
Java Inheritance
The document contains 15 multiple choice questions about inheritance in Java. Some key points covered include:
- Overriding vs overloading methods
- Access modifiers for methods in subclasses
- Calling superclass constructors and methods from subclasses
- Runtime polymorphism through inheritance
- Abstract methods and overriding rules
- Accessing subclass fields from superclass references
Inside PyMongo - MongoNYC
This document discusses PyMongo, a Python driver for MongoDB. It provides an overview of common PyMongo operations like connecting to a database, inserting and querying documents, and using GridFS for storing and retrieving files. It also covers newer PyMongo features like commands, stored JavaScript, and awareness of datetime limits. The document encourages involvement in the PyMongo open source project.
Java language fundamentals
The document contains a quiz on Java fundamentals with 29 multiple choice questions covering topics like classes, objects, variables, data types, and methods. It tests understanding of concepts like inheritance, abstraction, polymorphism, and exceptions. The questions have a single correct answer option to select from to test comprehension of Java language rules and behavior.
Recommended
Unit testing
This is for whom who want to start testing. How to do mocking in testing. Link for the example https://github.com/Vendetta30/GrailsUnitTesting.
Presentation1 computer shaan
The document describes a Java program to calculate parcel shipping charges based on weight. It begins with an initial charge of Rs. 15 for the first 1KG. Any additional weight is charged Rs. 8 for every 500g or fraction thereof. The program takes a weight in KGs as input, calculates the remaining weight after deducting 1KG, determines the charge for full 500g increments and any fractional part, and outputs the total charge.
Fl0ppy - CODEGATE 2016 CTF Preliminary
This document analyzes an exploit for a pwnable challenge called "Fl0ppy" that involves manipulating floppy disk structures. It finds that by overwriting the "data" or "description" fields of the floppy disk structures, a buffer overflow can be achieved to leak memory addresses and eventually execute the "/bin/sh" command by overwriting the return address. The key steps are leaking addresses, identifying the libc version, calculating the address of the "system" function, and using a buffer overflow to redirect execution to "system('/bin/sh')".
Python unittest
The document discusses Python's unittest framework for unit testing. It covers key concepts like test fixtures, test cases, test suites, and test runners. It also provides examples of setting up test fixtures by subclassing TestCase and initializing instance variables in the setUp method. The document recommends organizing tests into groups and using lifecycle methods like setUp, tearDown, setUpClass, and tearDownClass.
Python-nose: A unittest-based testing framework for Python that makes writing...
Nose is a Python testing framework that extends the built-in unittest framework. It makes writing and running tests easier by automating test discovery and running. Nose can be installed via pip and used by running nosetests on test files. Tests are written as unittest classes and methods. Nose supports configuration files, running tests in parallel, and integration with IDEs like Eclipse to automatically run tests on file changes.
Java Inheritance
The document contains 15 multiple choice questions about inheritance in Java. Some key points covered include:
- Overriding vs overloading methods
- Access modifiers for methods in subclasses
- Calling superclass constructors and methods from subclasses
- Runtime polymorphism through inheritance
- Abstract methods and overriding rules
- Accessing subclass fields from superclass references
Inside PyMongo - MongoNYC
This document discusses PyMongo, a Python driver for MongoDB. It provides an overview of common PyMongo operations like connecting to a database, inserting and querying documents, and using GridFS for storing and retrieving files. It also covers newer PyMongo features like commands, stored JavaScript, and awareness of datetime limits. The document encourages involvement in the PyMongo open source project.
Java language fundamentals
The document contains a quiz on Java fundamentals with 29 multiple choice questions covering topics like classes, objects, variables, data types, and methods. It tests understanding of concepts like inheritance, abstraction, polymorphism, and exceptions. The questions have a single correct answer option to select from to test comprehension of Java language rules and behavior.
Content marketing slideshow np os-v3
Anne Towne, Bob Duffy Content Marketing Slideshow for Annual Conference of Maryland Nonprofits, November 2014
Genetic adaptation to__organic
The document discusses breeding strategies for poultry in organic environments. It notes that commercial breeding companies focus on high egg production in cages, which can cause problems for organic systems using floor or free-range housing. Studies show cage-bred hens may have higher mortality and lower production outside of cages due to lack of adaptation to stress, disease resistance, and social behaviors important in group housing systems. Research indicates potential for genetic selection and adaptation of breeds to organic conditions through traits like nesting behavior and reduced feather pecking and cannibalism. Tests comparing commercial hybrids to local breeds in various countries found the local breeds often better adapted through traits like disease resistance and productivity on lower-protein diets.
14
El documento proporciona información biográfica sobre José Alberto Pradera, un político vasco que sirvió como Diputado General de Bizkaia de 1987 a 1995. Detalla su infancia y educación, su carrera profesional como ingeniero, y su participación en política como miembro del Partido Nacionalista Vasco. También resume los resultados electorales de 1987 que llevaron a Pradera a ser elegido como el Diputado General más joven de Bizkaia.
Case s 1
This dissertation examined the effectiveness of a hybrid English for Academic Purposes (EAP) course combining in-class and online writing instruction for college-bound ESL students. The study found that students who consistently used the online course website improved the organization and content of their writing, regulated their own learning, and used more learning strategies online than in class. However, lack of student motivation had a negative impact on performance. Overall, the hybrid format provided more effective ways for engaged learners to advance their writing skills and prepare for mainstream college programs compared to traditional in-class instruction alone.
The Outcome Economy
1) The document discusses the opportunity for technology to improve organizational efficiency and transition economies into a "smart and clean world."
2) It argues that aggregate efficiency has stalled at around 22% for 30 years due to limitations of the Second Industrial Revolution, but that digitizing transport, energy, and communication through technologies like blockchain can help manage resources and increase efficiency.
3) Technologies like precision agriculture, cloud computing, robotics, and autonomous vehicles may allow for "dematerialization" and do more with fewer physical resources through effects like reduced waste and need for transportation/logistics infrastructure.
Generating characterization tests for legacy code
This document discusses generating characterization tests for legacy code. It describes characterization tests as tests that characterize the actual behavior of code to act as change detectors and protect legacy code from unintended changes. It provides an example of a characterization test for a calculation method, and discusses how to find "pinch points" in code to focus testing and how to structure tests to replay inputs and outputs from recorded method executions. The document also introduces a framework for writing characterization tests by recording method inputs, outputs, and dependencies.
Aaron Bedra - Effective Software Security Teams
Software is eating the world. The rate at which we produce new software is astounding. Understanding and preventing potential issues is a growing concern.
Building software security teams is much different than building IT security teams. It requires different backgrounds and focus. Software security groups without an emphasis on software fail.
Join Aaron as he talks about the right way to build and run a software security group. You will walk away with a concrete list of actions that you can take back to your job and start working on right away.
Mutation testing for a safer Future
This document discusses mutation testing as a way to test code and test quality. Mutation testing involves intentionally breaking code in small ways (e.g. changing + to *) and ensuring tests catch these "mutant" versions. While code coverage measures how much code is executed, mutation testing checks that tests are thorough by breaking the code in multiple ways. The document provides examples of mutation testing and operators as well as a brief history of the technique. It notes that while time consuming, mutation testing can help identify faults that may cascade and ensure tests are comprehensive.
Software Testing:
A Research Travelogue
(2000–2014)
The document discusses the major developments and contributions in the field of software testing research over the past 14 years from 2000 to 2014. It identifies the most significant research contributions as automated test input generation techniques like symbolic execution, search-based testing, and random testing. It also discusses important testing strategies, empirical studies and infrastructure developments, and practical contributions to software testing. Open challenges and opportunities discussed include testing real-world systems, handling oracles, testing non-functional properties, and leveraging cloud and crowd-based approaches.
Machine Learning Model Bakeoff
Phil Roth presented the results of a malware classification model bakeoff between several machine learning algorithms. The models evaluated were k-nearest neighbors, logistic regression, support vector machines, naive Bayes, random forests, gradient boosted decision trees, and deep learning. Based on the performance, size, and query time metrics, gradient boosted decision trees had the best overall results. However, the presenter noted that deep learning approaches deserve more research due to their potential to learn directly from file content. The conclusions were that gradient boosted decision trees could be deployed to endpoints while larger deep learning models could be used in the cloud after further development.
Spock: Test Well and Prosper
Spock is a testing framework written in Groovy that allows developers to write tests in a business readable domain specific language. It combines the benefits of specification-based testing and mock-based testing. Some key features of Spock include the ability to write feature methods with given, when, and then blocks; use fixtures for setup and cleanup; parameterize tests with data tables in where blocks; make assertions about interactions with mock objects; and write tests in a BDD style with descriptive language. Spock's tests are themselves a good source of documentation on how to write and use Spock tests.
Quality Python Homework Help
I am Wycliffe S. I am a Python Homework Expert at pythonhomeworkhelp.com. I hold a Master's in Computer Science from, the University of Aberdeen, UK. I have been helping students with their homework for the past 13 years. I solve homework related to Python.
Visit pythonhomeworkhelp.com or email support@pythonhomeworkhelp.com. You can also call on +1 678 648 4277 for any assistance with Python Homework.
Agile Developer Immersion Workshop, LASTconf Melbourne, Australia, 19th July ...
Based on the Legacy CodeRetreat - Daniel Prager, Tomasz Janowski and I ran this all day workshop at this year's LASTconf.
Get ready to level up at refactoring at LAST Conference's first Refactoring Developer workshop. Inspired by Code Retreat, we have run a similar session, for the basics of agile development, at LAST Conference for the past few years. We have felt that it's Important to support learning in technical disciplines that are extremely important in agile software development.
Too many Agile and DevOps initiatives are stymied by code bases that are hard to change and understand.
While disciplined teams who rigorously practice pair programming, test-driven design (TDD) and other technical Agile practices avoid producing new legacy code in the first place, cleaning up a pre-existing mess is notoriously difficult and dangerous. Without the safety net of excellent automated test coverage, the risk of breaking something else as you refactor is extremely high. Also, code that wasn't designed and written with testability in mind makes it really difficult to get started. So most don't even try ...
In the Refactoring workshop developers learn how to build an initial safety net before applying multiple refactorings, and have lots of fun along the way!
To read more about how to run a classic CodeRetreat, I recommend this blogpost: https://medium.com/seek-blog/coderetreat-at-seek-clean-code-vs-comfort-zone-cfb1da64909d
Mutation @ Spotify
The document discusses mutating and testing tests. It introduces the concept of mutation analysis, where tests are evaluated by seeding real bugs into the code and checking if the tests detect these bugs. The document provides an example of applying mutation analysis to a factorial function code and test cases. It finds bugs in the test cases like weak oracles and missing test inputs. The document also compares the Pit mutation testing tool with the Descartes tool, finding Descartes generates fewer but coarser-grained mutants, making it more scalable for large projects.
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.
(automatic) Testing: from business to university and back
This talk cares about the fundamentals of testing, a little bit history of how the professional community developed what we currently know as testing, but also about why I should care about testing? why is it important to do a test? What is important to test? What is not important to test? How to do testing?
There some examples in plnker just to see each step, and many surprises.
This talk also compares what people learned in the Computer Sciences and Engineering degrees and what people does in testing. It gives some tips to catch up with current state of art and gives some points to start changing syllabus to make better engineers.
This talk is good for beginners, teachers, bosses, but also for seasoned techies that just want to light up some of the ideas that they might have been hatching.
Spoiler alert: testing will save you development time and make you a good professional.
CBDW2014 - MockBox, get ready to mock your socks off!
Mock what? What Mock?Learn What is Mocking, and how to use Mocking with ColdFusion testing, development, and continuous integration. Look at Mocking and Stubbing with a touch of Theory and a lot of Examples, including what you could test, and what you should test… and what you shouldn't test (but might be fun).
White-box Unit Test Generation with Microsoft IntelliTest
This document discusses white-box unit test generation using Microsoft IntelliTest. It begins with an overview of symbolic execution and how IntelliTest uses dynamic symbolic execution to generate test cases by exploring paths in the code. It then demonstrates IntelliTest's capabilities with examples. The document also discusses challenges with symbolic execution-based test generation and proposes solutions like visualizing the symbolic execution process and automatically isolating environment dependencies through source code transformations.
Test-Driven Design Insights@DevoxxBE 2023.pptx
Testing is fundamental in software development. Quality gates demand high coverage levels, pull requests need sufficient tests, leading to teams spending considerable time writing and maintaining them. But are we using our tests to their full potential?
'If code is hard to test, the design can be improved'. Starting from this mantra, this deep-dive session unveils hints to simplify code, break-down complexity, and effectively use functional programming. We'll delve into topics like fixture creep, partial mocks, onion architecture, and pure functions, providing numerous best practices and practical tips for your testing.
Be warned: This session may significantly disrupt your work routine and will likely change how you see testing. Attend at your own risk.
Grails unit testing
The document discusses unit testing in Grails using the Spock testing framework. It covers the basics of unit testing including goals, advantages, and challenges. It then provides an overview of Spock and examples of writing unit tests in Spock including mocking methods, domains, configurations, and dependencies. The document also discusses how to write unit tests for controllers and integration tests in Grails using Spock.
Java Unit Test and Coverage Introduction
The document provides an introduction to Java unit testing and code coverage. It discusses test-driven development and the JUnit testing framework, including annotations, test results, and Ant integration. It also covers using mock objects with Mockito, performing code coverage analysis, and code coverage tools like Emma and Cobertura.
More Related Content
Viewers also liked
Content marketing slideshow np os-v3
Anne Towne, Bob Duffy Content Marketing Slideshow for Annual Conference of Maryland Nonprofits, November 2014
Genetic adaptation to__organic
The document discusses breeding strategies for poultry in organic environments. It notes that commercial breeding companies focus on high egg production in cages, which can cause problems for organic systems using floor or free-range housing. Studies show cage-bred hens may have higher mortality and lower production outside of cages due to lack of adaptation to stress, disease resistance, and social behaviors important in group housing systems. Research indicates potential for genetic selection and adaptation of breeds to organic conditions through traits like nesting behavior and reduced feather pecking and cannibalism. Tests comparing commercial hybrids to local breeds in various countries found the local breeds often better adapted through traits like disease resistance and productivity on lower-protein diets.
14
El documento proporciona información biográfica sobre José Alberto Pradera, un político vasco que sirvió como Diputado General de Bizkaia de 1987 a 1995. Detalla su infancia y educación, su carrera profesional como ingeniero, y su participación en política como miembro del Partido Nacionalista Vasco. También resume los resultados electorales de 1987 que llevaron a Pradera a ser elegido como el Diputado General más joven de Bizkaia.
Case s 1
This dissertation examined the effectiveness of a hybrid English for Academic Purposes (EAP) course combining in-class and online writing instruction for college-bound ESL students. The study found that students who consistently used the online course website improved the organization and content of their writing, regulated their own learning, and used more learning strategies online than in class. However, lack of student motivation had a negative impact on performance. Overall, the hybrid format provided more effective ways for engaged learners to advance their writing skills and prepare for mainstream college programs compared to traditional in-class instruction alone.
The Outcome Economy
1) The document discusses the opportunity for technology to improve organizational efficiency and transition economies into a "smart and clean world."
2) It argues that aggregate efficiency has stalled at around 22% for 30 years due to limitations of the Second Industrial Revolution, but that digitizing transport, energy, and communication through technologies like blockchain can help manage resources and increase efficiency.
3) Technologies like precision agriculture, cloud computing, robotics, and autonomous vehicles may allow for "dematerialization" and do more with fewer physical resources through effects like reduced waste and need for transportation/logistics infrastructure.
Viewers also liked (6)
Similar to Generatingcharacterizationtestsforlegacycode
Generating characterization tests for legacy code
This document discusses generating characterization tests for legacy code. It describes characterization tests as tests that characterize the actual behavior of code to act as change detectors and protect legacy code from unintended changes. It provides an example of a characterization test for a calculation method, and discusses how to find "pinch points" in code to focus testing and how to structure tests to replay inputs and outputs from recorded method executions. The document also introduces a framework for writing characterization tests by recording method inputs, outputs, and dependencies.
Aaron Bedra - Effective Software Security Teams
Software is eating the world. The rate at which we produce new software is astounding. Understanding and preventing potential issues is a growing concern.
Building software security teams is much different than building IT security teams. It requires different backgrounds and focus. Software security groups without an emphasis on software fail.
Join Aaron as he talks about the right way to build and run a software security group. You will walk away with a concrete list of actions that you can take back to your job and start working on right away.
Mutation testing for a safer Future
This document discusses mutation testing as a way to test code and test quality. Mutation testing involves intentionally breaking code in small ways (e.g. changing + to *) and ensuring tests catch these "mutant" versions. While code coverage measures how much code is executed, mutation testing checks that tests are thorough by breaking the code in multiple ways. The document provides examples of mutation testing and operators as well as a brief history of the technique. It notes that while time consuming, mutation testing can help identify faults that may cascade and ensure tests are comprehensive.
Software Testing:
A Research Travelogue
(2000–2014)
The document discusses the major developments and contributions in the field of software testing research over the past 14 years from 2000 to 2014. It identifies the most significant research contributions as automated test input generation techniques like symbolic execution, search-based testing, and random testing. It also discusses important testing strategies, empirical studies and infrastructure developments, and practical contributions to software testing. Open challenges and opportunities discussed include testing real-world systems, handling oracles, testing non-functional properties, and leveraging cloud and crowd-based approaches.
Machine Learning Model Bakeoff
Phil Roth presented the results of a malware classification model bakeoff between several machine learning algorithms. The models evaluated were k-nearest neighbors, logistic regression, support vector machines, naive Bayes, random forests, gradient boosted decision trees, and deep learning. Based on the performance, size, and query time metrics, gradient boosted decision trees had the best overall results. However, the presenter noted that deep learning approaches deserve more research due to their potential to learn directly from file content. The conclusions were that gradient boosted decision trees could be deployed to endpoints while larger deep learning models could be used in the cloud after further development.
Spock: Test Well and Prosper
Spock is a testing framework written in Groovy that allows developers to write tests in a business readable domain specific language. It combines the benefits of specification-based testing and mock-based testing. Some key features of Spock include the ability to write feature methods with given, when, and then blocks; use fixtures for setup and cleanup; parameterize tests with data tables in where blocks; make assertions about interactions with mock objects; and write tests in a BDD style with descriptive language. Spock's tests are themselves a good source of documentation on how to write and use Spock tests.
Quality Python Homework Help
I am Wycliffe S. I am a Python Homework Expert at pythonhomeworkhelp.com. I hold a Master's in Computer Science from, the University of Aberdeen, UK. I have been helping students with their homework for the past 13 years. I solve homework related to Python.
Visit pythonhomeworkhelp.com or email support@pythonhomeworkhelp.com. You can also call on +1 678 648 4277 for any assistance with Python Homework.
Agile Developer Immersion Workshop, LASTconf Melbourne, Australia, 19th July ...
Based on the Legacy CodeRetreat - Daniel Prager, Tomasz Janowski and I ran this all day workshop at this year's LASTconf.
Get ready to level up at refactoring at LAST Conference's first Refactoring Developer workshop. Inspired by Code Retreat, we have run a similar session, for the basics of agile development, at LAST Conference for the past few years. We have felt that it's Important to support learning in technical disciplines that are extremely important in agile software development.
Too many Agile and DevOps initiatives are stymied by code bases that are hard to change and understand.
While disciplined teams who rigorously practice pair programming, test-driven design (TDD) and other technical Agile practices avoid producing new legacy code in the first place, cleaning up a pre-existing mess is notoriously difficult and dangerous. Without the safety net of excellent automated test coverage, the risk of breaking something else as you refactor is extremely high. Also, code that wasn't designed and written with testability in mind makes it really difficult to get started. So most don't even try ...
In the Refactoring workshop developers learn how to build an initial safety net before applying multiple refactorings, and have lots of fun along the way!
To read more about how to run a classic CodeRetreat, I recommend this blogpost: https://medium.com/seek-blog/coderetreat-at-seek-clean-code-vs-comfort-zone-cfb1da64909d
Mutation @ Spotify
The document discusses mutating and testing tests. It introduces the concept of mutation analysis, where tests are evaluated by seeding real bugs into the code and checking if the tests detect these bugs. The document provides an example of applying mutation analysis to a factorial function code and test cases. It finds bugs in the test cases like weak oracles and missing test inputs. The document also compares the Pit mutation testing tool with the Descartes tool, finding Descartes generates fewer but coarser-grained mutants, making it more scalable for large projects.
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.
(automatic) Testing: from business to university and back
This talk cares about the fundamentals of testing, a little bit history of how the professional community developed what we currently know as testing, but also about why I should care about testing? why is it important to do a test? What is important to test? What is not important to test? How to do testing?
There some examples in plnker just to see each step, and many surprises.
This talk also compares what people learned in the Computer Sciences and Engineering degrees and what people does in testing. It gives some tips to catch up with current state of art and gives some points to start changing syllabus to make better engineers.
This talk is good for beginners, teachers, bosses, but also for seasoned techies that just want to light up some of the ideas that they might have been hatching.
Spoiler alert: testing will save you development time and make you a good professional.
CBDW2014 - MockBox, get ready to mock your socks off!
Mock what? What Mock?Learn What is Mocking, and how to use Mocking with ColdFusion testing, development, and continuous integration. Look at Mocking and Stubbing with a touch of Theory and a lot of Examples, including what you could test, and what you should test… and what you shouldn't test (but might be fun).
White-box Unit Test Generation with Microsoft IntelliTest
This document discusses white-box unit test generation using Microsoft IntelliTest. It begins with an overview of symbolic execution and how IntelliTest uses dynamic symbolic execution to generate test cases by exploring paths in the code. It then demonstrates IntelliTest's capabilities with examples. The document also discusses challenges with symbolic execution-based test generation and proposes solutions like visualizing the symbolic execution process and automatically isolating environment dependencies through source code transformations.
Test-Driven Design Insights@DevoxxBE 2023.pptx
Testing is fundamental in software development. Quality gates demand high coverage levels, pull requests need sufficient tests, leading to teams spending considerable time writing and maintaining them. But are we using our tests to their full potential?
'If code is hard to test, the design can be improved'. Starting from this mantra, this deep-dive session unveils hints to simplify code, break-down complexity, and effectively use functional programming. We'll delve into topics like fixture creep, partial mocks, onion architecture, and pure functions, providing numerous best practices and practical tips for your testing.
Be warned: This session may significantly disrupt your work routine and will likely change how you see testing. Attend at your own risk.
Grails unit testing
The document discusses unit testing in Grails using the Spock testing framework. It covers the basics of unit testing including goals, advantages, and challenges. It then provides an overview of Spock and examples of writing unit tests in Spock including mocking methods, domains, configurations, and dependencies. The document also discusses how to write unit tests for controllers and integration tests in Grails using Spock.
Java Unit Test and Coverage Introduction
The document provides an introduction to Java unit testing and code coverage. It discusses test-driven development and the JUnit testing framework, including annotations, test results, and Ant integration. It also covers using mock objects with Mockito, performing code coverage analysis, and code coverage tools like Emma and Cobertura.
Ruslan Shevchenko - Property based testing
Property-based testing involves generating random inputs and checking that the output of a function satisfies desired properties or laws. It works by specifying properties as assertions that should hold true for all inputs. Testing libraries like ScalaCheck, QuickCheck, and Hypothesis can automatically generate random test values and attempt to falsify the properties. This helps test a wide range of inputs and edge cases. The document provides examples of using property tests to check if a sorting algorithm produces a sorted output and to validate data formats meet constraints. It also discusses generating customized input models and common properties like order relationships.
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
Python mocking intro
Mock objects are simulated objects used in unit testing to isolate and test specific parts of code without dependencies on other objects. The unittest.mock library provides a Mock class that can be used to create mock objects. Mock objects are flexible and create attributes on demand to mimic real objects. They record how they are used to make assertions. Common uses of mock objects include setting return values, configuring side effects like exceptions, and attaching mocks as child objects.
33rd Degree 2013, Bad Tests, Good Tests
1. The document discusses good and bad practices for writing unit tests. It emphasizes that tests should verify the expected behavior, fail clearly when something goes wrong, and use mocks and isolation to focus on the code being tested.
2. Some examples of bad tests shown include tests that don't make assertions or assertions that don't provide useful information on failure. Real objects are also used instead of mocks, obscuring the test.
3. Good practices include using mocks to isolate the code being tested, making sure tests fail clearly when something goes wrong, and focusing tests on expected behavior through clear assertions. Automated testing, fixing broken tests, and mastering testing tools are also emphasized.
Similar to Generatingcharacterizationtestsforlegacycode (20)
Software Testing:
A Research Travelogue
(2000–2014)
Software Testing:
A Research Travelogue
(2000–2014)
Agile Developer Immersion Workshop, LASTconf Melbourne, Australia, 19th July ...
Agile Developer Immersion Workshop, LASTconf Melbourne, Australia, 19th July ...
(automatic) Testing: from business to university and back
(automatic) Testing: from business to university and back
CBDW2014 - MockBox, get ready to mock your socks off!
CBDW2014 - MockBox, get ready to mock your socks off!
White-box Unit Test Generation with Microsoft IntelliTest
White-box Unit Test Generation with Microsoft IntelliTest
Generatingcharacterizationtestsforlegacycode
- 1. Generating Characterization Tests for Legacy Code Slides via Jonas Follesø (@follesoe)
- 2. Huge methods (~3000+ lines)
- 7. FraserSpeirshttp://www.flickr.com/photos/fraserspeirs/3395595360/ Legacy code is code without tests. Code without tests is bad code. -Michael C. Feathers
- 8. A characterization test is test that characterizes the actual behavior of a piece of code. It acts as a change detector, protecting legacy code from unintended changes
- 9. public double Calc(double inv, double rt, int y) { double ret = 0; for (int i = 1; i <= y; i++) { ret = inv * Math.Pow(1.0 + rt / 100.0, i); } return ret; }
- 10. [TestMethod] public void Calc_characterization() { var calc = new CalcUtil(); double result = calc.Calc(10000, 10, 10); Assert.AreEqual(42.0, result); }
- 12. [TestMethod] public void Calc_characterization() { var calc = new CalcUtil(); double result = calc.Calc(10000, 10, 10); Assert.AreEqual(25937.424601, result); }
- 13. Test run completed. Results 1/1 passed.
- 14. public double CalculateCompoundInterest( double investment, double interest, int years) { double projectedValue = 0.0; for (int year = 1; year <= years; year++) { projectedValue = investment * Math.Pow(1.0 + interest / 100.0, year); } return projectedValue; }
- 15. FraserSpeirshttp://www.flickr.com/photos/fraserspeirs/3395599536/ …A pinch point is a natural encapsulation boundary. When you find a pinch point, you’ve found a narrow funnel for all the effects of a large piece of code… -Michael C. Feathers
- 17. The Golden Master Approach Before making any change to production code, do the following: 1) Create X number of random inputs, always using the same random seed, so you can always generate the same set over and over again. You will probably want LOTS of inputs for good coverage. 2) Bombard the class or system under test with these random inputs. 3) Capture the outputs for each individual random input.
- 18. A picture's worth a 1000 tests. Unit testing asserts can be difficult to use. Approval tests simplify this by taking a snapshot of the results, and confirming that they have not changed.