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 6320977
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T16:04:10+00:00 2026-05-24T16:04:10+00:00

I am about to write just another Java-Test which covers a new feature. To

  • 0

I am about to write just another Java-Test which covers a new feature. To document the reason for this new tests I am thinking about commenting the test with an explanation of the feature.

Should I do that?

What is a good way to link the tests with the features?

  • 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. Editorial Team
    Editorial Team
    2026-05-24T16:04:11+00:00Added an answer on May 24, 2026 at 4:04 pm

    You should name your tests in such a way that it’s obvious which feature is under test, and the conditions of that test.

    If, for some reason, that is not possible, then and only then should you add minimal commentary to your test; as should be the case for ANY code you write.

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

Sidebar

Related Questions

I am about to write junit tests for a XML parsing Java class that
I am new to the whole Java Swing/AWT dialogs (which explains how amateurish this
I recently found out about java.util.Properties , which allows me to write and read
I'm just about to write my first application in a duck typed language (Groovy).
I've got an application that just shipped. Since I wrote it, I've learned about
I am about to write an audio file converter for my side job at
I'm about to write a little GUI app that will sit in the system
I'm about to write a small utility to organze and tag my mp3s. What
I am about to write a tender. The solution might be a PHP based
I'm about to write a Scala command-line application that relies on a MySQL database.

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.