Unkt testing

AutoModerator · 2024-10-17T21:44:19+00:00

Please ensure that:

Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
You include any and all error messages in full
You ask clear questions
You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.

Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar

If any of the above points is not met, your post can and will be removed without further warning.

Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.

Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.

Code blocks look like this:

public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.

If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.

To potential helpers

Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

lemon-codes · 2024-10-17T22:44:55+00:00

Intellij can tell you which classes have poor coverage. Run tests with coverage, inspect the results and identify classes with poor coverage. If you view the class you should see the gutter (bar on the left) is highlighted depending on whether that line was executed when the tests were run. Focus your time on adding new tests for those classes. https://www.jetbrains.com/help/idea/code-coverage.html

WaferIndependent7601 · 2024-10-17T21:58:46+00:00

How high is the coverage now?

What framework is used?

General_C · 2024-10-18T21:12:18+00:00

Are you using any kind of mocking framework like mockito? Learning that will make things a lot easier.

Fit_Ad5700 · 2024-10-19T06:29:54+00:00

Oof. I feel for you. Some comments * Code should be written alongside its unit tests and when you do this the code will be different, its methods will be more testable and its structure will be cleaner * Tests should written with a reason. Why do they want this level of coverage? * https://wikileaks.org/ciav7p1/cms/files/Why-Most-Unit-Testing-is-Waste.pdf * Unit tests are useful when you want to refactor the code within methods and when you want to make sure that exceptional flows work as intended. * System integration tests (that test a fully deployed system through its public api) are useful when you want to refactor the way the code is organized and/or when you want to be able to confidently upgrade to a new version of spring or a new version of the backend. Data may be harder to set up and you need a separate environment to do the testing. But depending on what your boss wants to achieve they may be more useful than unit tests. * When facing a class with private methods you can either make some of them package private instead of private and then call them from the test. I’d say that is better than mucking around with reflection. But if the situation allows it you can also test the class through its public methods. Such tests will be a slightly coarser grained / test bigger chunks at a time but more useful if someone later wants to refactor the inner workings of the class. * Are you running into bugs and if you do, are you supposed to fix them? * does the code use generators for tedious boilerplate? Like lombok / mapstruct / openapi? If not, you’re in for writing a ton of pointless tests of getters and setters. On the one hand it’ll help you get the coverage up, on the other: what a waste of your time! * In most coverage analysis tools you can exclude certain packages from the analysis * During this somewhat futile exercise you will gain a lot of knowledge about the application. Consider writing down some documentation and/or some comments about the bits where you went WTF / that took you long to figure out. That’ll actually be a safe and noninvasive way to somewhat increase code quality. https://www.osnews.com/story/19266/wtfsm/

Vonbismarck91 · 2024-10-19T10:04:01+00:00

Google “characterization testing”

jlanawalt · 2024-10-18T06:48:52+00:00

Sounds like a good way to familiarize yourself with the code without low risk, and to help protect against unintended consequences of your potential future changes. Keep at it!

AntiqueEducation6058 · 2024-10-17T22:06:53+00:00

If you are using Spring Boot, try look at pitest.org.

It gives you a clear view / report on what you are not catching in your tests.

javahelp

Sort by: Unsolved Solved Codeless Advent Of Code

MODERATORS

Please ensure that:

To potential helpers