Software Testing

273 readers

3 users here now

Spreading knowledge on software testing and the value it can provide, as well as a location to ask questions about implementations or testing strategies or frameworks

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

Ategon@programming.dev

lackthought@lemmy.sdf.org

Unit testing a non-abstract base class? (khorikov.org)

submitted 3 weeks ago by codeinabox@programming.dev to c/software_testing@programming.dev

1 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] codeinabox@programming.dev 1 points 3 weeks ago

I stumbled upon this article after reviewing a pull request, where someone was unit testing the abstract base class. I'm of the opinion that base classes should not be tested. We don't want to be testing the architecture of an application, we want to be testing the behaviour. The author sums this up nicely with this point:

For tests, though, it shouldn’t matter whether the classes under test share the domain logic or duplicate it. Tests should view all production code as a black box, and approach verifying it with a blank slate. Otherwise, such tests will start couple to the code’s implementation details.