Everybody has legacy code. How do you apply unit testing to existing code? Code that wasn’t meant to testing. This is a hardcore session, where we take an open source application and add tests to it. In the process, we’ll refactor the code, discuss readability, and where to even begin. This is an intensive demonstration …
Tag Archive: legacy code
Permanent link to this article: http://www.typemock.com/blog/2012/01/23/webinar-testing-untestable-code/
Dec
19
Are You A Unit Testing Ninja? Stuck with Legacy Code?
Everybody has legacy code. People write more and more legacy code every day. But what problems does it cause and how can we deal with it? Forget theory and tips. Let’s dive deep into a real world example. How do you apply unit testing to existing code? Code that wasn’t meant to test. This …
Permanent link to this article: http://www.typemock.com/blog/2011/12/19/are-you-a-unit-testing-ninja-stuck-with-legacy-code/
Sep
30
Top 5 Unit Testing Problems in C++ Legacy Code and How to Solve Them
Like unit testing but sometimes it gives you problems? Well, even we admit that sometimes it can be difficult. Gil Zilberfeld recently identified many problems when testing C++ legacy code and how to solve them. Watch his webinar: Legacy code is a real problem with C++ applications. With so many developers working on the …
Permanent link to this article: http://www.typemock.com/blog/2011/09/30/top-5-unit-testing-problems-in-c-legacy-code-and-how-to-solve-them/
Sep
12
Webinar– Top 5 Unit Testing Problems in C++ Legacy Code and How to Solve Them
Legacy code is a real problem with C++ applications. With so many developers working on the same codebase over time – decades even — your code gets complicated and full of dependencies. Unit testing is often the best solution to ensure that your legacy code does what it’s supposed to do. But sometimes unit testing …
Permanent link to this article: http://www.typemock.com/blog/2011/09/12/webinar%e2%80%93-top-5-unit-testing-problems-in-c-legacy-code-and-how-to-solve-them/
Jun
21
Who wants a FREE Typemock T-shirt?
Want to win a Typemock Unit Testing t-shirt? Join our webinar on tips for better unit testing and two recipients will win a Typemock t-shirt. One person will also get a free license of Typemock Isolator! Date: Monday, June 27 Time: 10:00 AM ET / 3:00PM London / 5:00 PM Israel Register Now: https://www2.gotomeeting.com/register/365837051 Attend …
Permanent link to this article: http://www.typemock.com/blog/2011/06/21/who-wants-a-free-typemock-t-shirt-2/
Apr
03
Supercharging Your Unit Testing
If you want to learn how to write better unit tests and test the untestable, watch Typemock’s webinar about Supercharging Your Unit Tests. Supercharging Your Unit Testing from Typemock on Vimeo. Here are the slides from the webinar: Supercharing your Unit Testing View more presentations from Typemock.
Permanent link to this article: http://www.typemock.com/blog/2011/04/03/supercharging-your-unit-testing-2/
Dec
28
How To: Fake an Abstract Class with Isolator++
When you declare an abstract class in C++, it looks like this: class AbstractClass { public: virtual int ReturnFive() = 0; }; in Microsoft’s world you have an additional choice – declare a pure virtual method using the PURE macro (basically equivalent): class AbstractClass { public: virtual int ReturnFive() PURE; }; Here are …
Permanent link to this article: http://www.typemock.com/blog/2010/12/28/how-to-fake-an-abstract-class-with-isolator/
Nov
21
Free Webinar: Be a legacy code unit test ninja with Typemock Isolator
On Tuesday next week, I’ll be hosting a free webinar on using Typemock Isolator to write unit tests for some horribly untestable legacy code. (I originally wanted to call it “Can you Isolation framework do this?”) Roy will walk you through writing unit tests for one of the most untestable code bases he could find …
Permanent link to this article: http://www.typemock.com/blog/2010/11/21/free-webinar-be-a-legacy-code-unit-test-ninja-with-typemock-isolator/
Oct
20
How-To: Setting Behavior for Future Objects with Isolator++
One of the biggest hurdles in writing tests for legacy code are future dependencies. They are called “future” objects, because they are created inside the class under test, rather then injected into it by the test. Let’s look at our Person constructor: Person::Person() { address = new Address(); } That address, right there, is …
Permanent link to this article: http://www.typemock.com/blog/2010/10/20/how-to-setting-behavior-for-future-objects-with-isolator/
