From a85604bcc12109542c40ae4d8ea4844d6710ec3c Mon Sep 17 00:00:00 2001 From: jasonqiu212 Date: Fri, 21 Oct 2022 02:52:20 +0800 Subject: [PATCH] Style: fix checkstyle --- .../swift/logic/parser/DeleteContactCommandParserTest.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/test/java/swift/logic/parser/DeleteContactCommandParserTest.java b/src/test/java/swift/logic/parser/DeleteContactCommandParserTest.java index 66d000cc209..21ad749ced7 100644 --- a/src/test/java/swift/logic/parser/DeleteContactCommandParserTest.java +++ b/src/test/java/swift/logic/parser/DeleteContactCommandParserTest.java @@ -11,7 +11,7 @@ /** * As we are only doing white-box testing, our test cases do not cover path variations - * outside of the DeleteCommand code. For example, inputs "1" and "1 abc" take the + * outside the DeleteCommand code. For example, inputs "1" and "1 abc" take the * same path through the DeleteCommand, and therefore we test only one of them. * The path variation for those two cases occur inside the ParserUtil, and * therefore should be covered by the ParserUtilTest. @@ -27,6 +27,7 @@ public void parse_validArgs_returnsDeleteCommand() { @Test public void parse_invalidArgs_throwsParseException() { - assertParseFailure(parser, "a", String.format(MESSAGE_INVALID_COMMAND_FORMAT, DeleteContactCommand.MESSAGE_USAGE)); + assertParseFailure(parser, "a", String.format(MESSAGE_INVALID_COMMAND_FORMAT, + DeleteContactCommand.MESSAGE_USAGE)); } }