Campbell Ritchie wrote:Before you test that code, stop using Calendar or the buillt‑in Date class. Use the newer classes as described in the Java™ Tutorials.
It looks like the whole point of the code is to write a class which represents time-stamps. Yes, I know that's a WTF and it's the exact opposite of best practice. But apparently there are still some teachers who think it's a good way to practice coding.
Asking how to do JUnit testing is a little like asking how to program: it's a complex issue. Can you give us some more context? Have you been told to "add testing" to your program by a teacher or employer? Is this for your own research? Are you using an IDE? Which one? Are you using Maven? Gradle? Is this for a company that runs CI (continuous integration)? In other words, is this part of a larger software development system or just for you?
After we determine your development environment, you would start writing unit tests. This is a new program that will run your tests for the original program. (You actually test methods). I would start with very simple tests and build from there.
A JUnit tutorial would be a good place to start. I would start by googling junit 5 tutorial for beginners. Sorry, I can't recommend any specific one; I'm not familiar with them.
All things are lawful, but not all things are profitable.
posted 1 month ago
I resisted the temptation to say that writing your own date/time classes is a waste of time, but at least it would have ben easier with a well‑designed class underlying that.
Of course, you should be able to extract the information without using an intermediate class at all, so I tried something on JShell:
Ruth Stout was famous for gardening naked. Just like this tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database