Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 88133
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T22:30:43+00:00 2026-05-10T22:30:43+00:00

Ought I to unit test constructors? Say I have a constructor like this: IMapinfoWrapper

  • 0

Ought I to unit test constructors? Say I have a constructor like this:

IMapinfoWrapper wrapper; public SystemInfo(IMapinfoWrapper mapinfoWrapper) {     this.wrapper = mapinfoWrapper; } 

Do I need to write a unit test for this construtor? I don’t have any getters for the wrapper variable, so I don’t need to test that.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T22:30:43+00:00Added an answer on May 10, 2026 at 10:30 pm

    Unit testing is about testing the public states, behaviors, and interactions of your objects.

    If you simply set a private field in your constructor, what is there to test?

    Don’t bother unit-testing your simple accessors and mutators. That’s just silly, and it doesn’t help anyone.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I feel like this question ought to have been covered, but I can't seem
JavaScript is purported to have first-class functions, so this seems like the following ought
This ought to simple. Say we have a struct from a library that doesn't
This seems like it ought to be simple, but I've tried both try {}
I have some scripts that ought to have stopped running but hang around forever.
I have two simple while loops in my program that I feel ought to
The below MSSQL2005 query is very slow. I feel like their ought to be
This ought to be ridiculously easy. I simply want to print a single element
I'm a little embarrassed to ask this as I ought to know better, but
I have been perpetually intrigued by test-driven development, but I can never follow through

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.