Sure! Here are the practice exercises without solutions or explanations.
Divide
@Test | |
public void rollTimeByDaysTest(){ | |
//================================== | |
//TEST CASE 1 | |
//================================== | |
System.out.println("Test case I"); | |
DateTime dateTime = new DateTime(2020,12,14,0,0); | |
DateTime newDate = DateTimeUtils.rollBackByDayOfMonth(dateTime, 7); | |
System.out.println(" newDate " + DateTimeUtils.convertDateToString(newDate)); | |
Assertions.assertEquals(8,newDate.dayOfMonth().get()); |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the