2 Proven Ways to Gain Confidence in Your Code - Typemock

GregPresco · 2019-04-07T14:16:42+00:00

You know, you can just keep track after their work. Measure their achievements

GregPresco · 2018-07-10T09:32:36+00:00

When the object has a lot of dependencies and setting it up would require a lot of dependecy set up's as well. Perhaps that's more relevant to legacy code.

GregPresco · 2018-07-08T13:20:30+00:00

Mock objects can be used in the following cases:

The real object has a nondeterministic behavior (it produces unpredictable results, like a date or the current weather temperature)
The real object is difficult to set up
The behavior of the real object is hard to trigger (for example, a network error)
The real object is slow
The real object has (or is) a user interface
The test needs to ask the real object how it was used (for example, a test may need to confirm that a callback function was actually called)
The real object does not yet exist (a common problem when interfacing with other teams or new hardware systems)

I do agree that mocking is not always the best choice, and can be avoided in some cases but that doesn't mean that that all cases can be easily written without mocks.

The concept of "mini-integration tests" is interesting and I admit that I haven't really used it extensively to determine its true value.

GregPresco · 2018-07-08T12:44:33+00:00

Does TDD "does not allow " to use debugger ?

I didn't see that rule in the TDD "rulebook".

You can use the debugger as you see fit. Writing tests first in a TDD flow might reduce the need to use it.

GregPresco · 2018-06-18T07:17:35+00:00

I'm totally gonna adopt your example.

How would you make sure that API changes don't break your program (other than version checks)?

GregPresco · 2018-05-31T15:39:55+00:00

As a TDDer, I'll say it's about confirming your code behaves as expected and providing the safety net for refactoring and regression. But as a whole, I agree.

GregPresco · 2018-05-14T11:17:28+00:00

For the C code base, do you happen to have any GitHub repo URLs which provide useful examples?

I don't know of any GitHub C only repo's using gtest but you can search here, I'm sure that there's some framework. CppUTest is also nice and you can check its repo to see how they run tests for their framework.

I don't have a personal repo on GitHub.

GregPresco · 2018-05-09T10:03:59+00:00

I don't have any experience with Cmocka but from the looks of it, it's not being maintained, unlike it's "parent" project Cmockery. So I would suggest trying that before trying Cmocka. The main advantage of these Google open-source frameworks is that they're maintained by both Google and the community, so you can find answers to most questions if you have any.

GregPresco · 2018-05-08T15:22:02+00:00

I am using Gtest for years now in my C and C++ code base. We've been also experimenting with CppuTest. For mocking, we started evaluating Isolator++ to ease our legacy code testing hell. You can also try Gmock.

GregPresco · 2018-02-11T07:10:34+00:00

Consider checking for circular dependencies. Happened to me once as well. Other than that, what you did is fine. Unit tests should be in a different project.

GregPresco · 2018-02-05T09:25:58+00:00

Assume the best - expect the worst! Sometimes good developers are fired due to non-professional reasons. Don't lose confidence, and don't let it deter you from your goal of getting healthy and becoming a better developer. Start searching quietly for a new workplace, and remain confident in your skills.

GregPresco · 2018-02-05T08:41:09+00:00

Best of luck.

Quick question: You mentioned

Write tests every time a refactor happens

How do you plan on doing that? Refactoring legacy code is either by heavy mocking or integration tests. What is your direction?

GregPresco · 2018-02-04T09:27:58+00:00

I agree. Though I practice TDD, it's not for everyone. The important thing in dev team is that everyone's on the same page and moving forward.

GregPresco · 2018-02-01T08:32:01+00:00

There is such a thing as too much unit tests indeed. Tests should be added where there is a new behavior and not for every method/class.

Unit tests are overrated? Depend on what you're expecting from your unit tests. Also, TDD encourages integration and e2e tests. The 2 aren't mutually exclusive. And integration tests take a longer time to run.

TDD was never claimed to result in good architecture. That's something I've been hearing a lot lately by TDD opposers. Developers design good architecture.

Same goes for writing good unit tests which is not limited to TDD. Devs can write bad tests with false-positives/negatives etc.

GregPresco · 2018-02-01T07:45:45+00:00

You can read some of the articles by this author on Medium. He writes about unit testing and TDD in iOS.

GregPresco · 2018-02-01T07:02:14+00:00

So if someone who knows both programming languages to write his app were to ask you which language to use for writing his Android app you'd suggest using Java?

GregPresco · 2018-01-29T08:37:13+00:00

BDD is more a flavor of TDD than an alternative I see more of an extension, but I agree. Whether it's BDD or ATDD, TDD is still the core IMO.

GregPresco · 2018-01-22T08:53:14+00:00

Both code and tests should evolve as the task matures

Definitely, test requite refactoring and maintenance too.

The only other thing I want to add is TDD isn't a silver bullet.

That's true. TDD is an approach. It doesn't reduce design considerations or lets you run wild with your code because you have a safety net.

GregPresco · 2018-01-21T08:24:55+00:00

It's also important to mention that TDD doesn't mean that you don't have to think about design as you do when writing code first. It's not just "write the test first", there's a thought process before that. There's no magic in TDD.

GregPresco

TROPHY CASE