-
Notifications
You must be signed in to change notification settings - Fork 11
Conversation
test/json_unittest.cc
Outdated
)), json::Exception); | ||
} | ||
|
||
TEST(FromStringTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can delete TEST(BigTest, RealisticParsing)
now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, so I can. Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor comments.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStreamTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Complete
-> SingleObject
for similarity with previous tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FromStream
only supports a single object, so that seems a bit redundant. But ok.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStreamTest, ExpectSingle) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
similarly:
ExpectSingle
-> MultipleObjectsThrowsError
Makes it clear we are testing similar inputs across multiple methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Done.
test/json_unittest.cc
Outdated
)), json::Exception); | ||
} | ||
|
||
TEST(FromStringTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto as above:
Complete
-> SingleObject
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStringTest, ExpectSingle) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above:
ExpectSingle
-> MultipleObjectsThrowsError
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(StreamingTest, ParseStreamThrowsOnParseErrorMidStream) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this name (ParseStreamThrowsOnParseErrorMidStream
) hard to understand.
Removing the "On
" would be better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, that would change the meaning I was trying to convey. Renamed — is this better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStreamTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FromStream
only supports a single object, so that seems a bit redundant. But ok.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStreamTest, ExpectSingle) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Done.
test/json_unittest.cc
Outdated
)), json::Exception); | ||
} | ||
|
||
TEST(FromStringTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, so I can. Done.
test/json_unittest.cc
Outdated
)), json::Exception); | ||
} | ||
|
||
TEST(FromStringTest, Complete) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(FromStringTest, ExpectSingle) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
test/json_unittest.cc
Outdated
}); | ||
} | ||
|
||
TEST(StreamingTest, ParseStreamThrowsOnParseErrorMidStream) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, that would change the meaning I was trying to convey. Renamed — is this better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
These will make more sense if read one commit at a time.